DNS working but nslookup timeout
Recently migrated from BIND to PowerDNS. Not sure if this is new behaviour, but the DNS seems to be working fine, all domains resolve, and external tools like mxtoolbox and ultratools are able to get domain records.
However, if I from Windows commmand like, run nslookup, then server ns1.mydomain.com, when I query a domain whose zone is on the server I get sometimes get DNS request timed out, and sometimes it works. Usually if I switch to the other name server in the cluster, ie go to ns2.mydomain.com, it works, but not always, failing with the same request timed out error.
What's going on here? Is there something that limits or prevents direct queries to the nameserver by nslookup?
-
Is it the same if you use the IP address of the nameserver? 0 -
Interesting - no - if I use the IP address (either IPv4 or IPv6) of the nameserver the results come back normally as expected. 0 -
what do you get if you run: nslookup ns1.mydomain.com 0 -
If I run nslookup ns1.mydomain.com, the results seem normal - non-authoritative answer, the correct IPv4 and IPv6 addresses. 0 -
It must have been a glitch in the matrix. I've just tried to recreate the problem again, and everything came back fine. So actually everything is working normally. I've changed nothing but a few hours have passed.... maybe something along the way between me and the server was having an issue. 0 -
Could be that, but if you run into further issues with this, I'd suggest opening a ticket so we can look at the configuration while it's occurring. 0
Please sign in to leave a comment.
Comments
6 comments