find problem on example #800
Replies: 2 comments
-
likely means that the name server you tried to do the transfer from was not authoritative for the domain
means that the nameserver gave a TSIG BADKEY error, which means that the nameserver either didn't know the key name or didn't recognize the algorithm. I'm not sure what's going on here based on your configuration. You probably should not use your rndc key as a TSIG key but should generate a separate one. You should not use HMAC-MD5 as MD5 is not secure; HMAC-SHA256 would be a good choice. I don't know if not having a trailing "." on the key name matters for BIND key statements as it has been too long since I used them, but you might try adding one. |
Beta Was this translation helpful? Give feedback.
-
Hi @rthalley Thanks for your reply and sorry for my late response. My Test env is blow this The error we can see
And the bind log is nothing on this step, more strangly,I can use the same key by rndc command and it worked such as
However my laptop django project is still not ok,which confused me for a long time recently I found the difference between the laptop and the rndc command server I used dig command like this
rndc command server is ok and shows the results but the laptop shows error After serval tests, I find the issue problem is on the different firewall zone , maybe the zone policy is matter BR |
Beta Was this translation helpful? Give feedback.
-
Hi team,
I am facing the problem on changing another env
eample1:
I have used it on my first bind9 env is ok however it not work when I changed to another
It shows error message
Example2 :
it shows
My config is blew
rndc.conf
name.conf
named.rfc1912.zones
Could you please give me some advice on it , maybe I have mistake some config on my conf file
dnspython == 2.2.0
BR
Robin
Beta Was this translation helpful? Give feedback.
All reactions