colinedwardharvey at yahoo.com
Sun Dec 4 18:08:09 UTC 2011
We're running BIND 9.6.1-P3 on several machines setup to be forwarders. Some domains are not resolvable via the forwarder, so named.ca has those domains listed with the appropriate nameservers to reach to resolve the requests.
For some reason, one host is either not using its named.ca or has some other glitch. dig, host, and nslookup just hang when trying to debug the situation.
To resolve the issue on this one host, I added the troublesome domain to named.conf as another forwarder zone. This resolved the situation.
I'd like to understand the underlying cause here tho. Under the original configuration (that wasn't working) I was able to resolve the requests if I told nslookup where to go, i.e. 'nslookup host.otherzone.com 192.168.1.42'. So, for me, this proved that networking was not the issue. But after that troubleshooting step, I'm not sure where to look.
Also, is the original configuration a generally accepted method to do what we're doing? Or is my fix the recommended method?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the bind-users