From: Ciesinski, Nick (CiesinskNA26@uww.edu)
Date: Tue Jan 20 2004 - 11:40:06 CST
I moved servers during our winter break and in the process moved to Bind version 9.2.3. I had a slight problem that I can't figure out and was hoping someone could give some insight.
When I moved from the previous version of Bind (9.x) I just copied the configuration files. So the config was the exact same from one version of Bind to the other.
When a user/me would try and do a lookup on say google.com I would get a NXDOMAIN error. Every other name except .com's would come back correctly. I traced it down to the following lines in the db.root file.
windowsupdate.com. NS example.com.
windowsupdate.microsoft.com. NS example.com.
example.com. IN A 127.0.0.1
When these lines are present all .com's fail with NXDOMAIN. When I remove the lines it works. I also tried to put in something like google.com IN A 127.0.0.1 and it still fails to resolve any .com except the one in the db.root file.
I don't understand why this is happening. I tried just putting .net's into the db.root and I don't see the issue with .net's as I did with .com's.
Anyone have any thoughts? It just seems to weird to me.
Here is some of my named.conf.
options {
directory "/var/named";
pid-file "named.pid";
recursion no;
};
zone "." in {
type master;
file "/etc/db.root";
};
server 140.146.200.75 {
bogus yes;
};
Thanks,
Nick
**********************************************************************
To unsubscribe from this list, send an e-mail message to
majordomo@southwestern.edu containing a single line with the words:
unsubscribe netreg
Send requests for assistance to: owner-netreg@southwestern.edu
**********************************************************************
This archive was generated by hypermail 2.1.4 : Thu Aug 12 2004 - 12:01:43 CDT