Hello,
Im update my ddns server (bind-9.5.2), but have problems.
Mikrotik 3.15
Routerboard 333
command to update:
/tool dns-update address=100.100.100.100 dns-server=200.200.200.200
name=“hosddin” ttl=60 zone=“ddns.mydomain.com” key-name=“ddns.mydomain.com.” k
ey=“asdqw1O6gqwFqcz7O/Hq12==”
But receive this message in terminal of mikrotik:
bad key
or
bad reply format
In my BIND server:
client 10.1.14.2#55452: request has invalid signature: TSIG ddns.mydomain.com: tsig verify failure (BADSIG)
Clocks are syncronized.
OBS: problem only in RB-333, in RB-133 i have no problems
Sorry for my english.
Thanks
JJCinAZ
2
OBS: problem only in RB-333, in RB-133 i have no problems
Sounds like an endian bug to me. Maybe you should capture packets from the working RB-133 and then the non-working RB-333 and send those to support.
Hello,
I have same problem.
RouterOS 3.27 (recently 3.25 - same behavior)
Routerboard RB433AH
My update command is:
dns-update dns-server=x.x.x.x name="ocean" address=y.y.y.y key-name="rndc-key" key="PNLMjMn8J44aND89pKicCrPGT5hOJnwnLr3XW2P5t6Q=" zone="domain.tld"
And the response from Bind server is:
request has invalid signature: TSIG rndc-key: tsig verify failure (BADSIG)
Bind server is configured correctly. When I use nsupdate command at another box, than it works OK.
It looks like some ugly bug in RouterOSs dns-update command. Does anybody have a solution ?
I have captured some packets in Wireshark. They are in attached files.
- capture from PC and nsupdate (this works)
- capture from Routerboard (this is bad)
routerboard.log (404 Bytes)
pc.log (368 Bytes)