Ehh… yesterday my name server NS1 looked fine… today it looks bad. NS2 looked bad all along.
They are both rejecting all requests.
It must be the setup on the machine because it’s writing this to the log files:
Mar 17 08:54:40 ns1 named[2108]: client xx.xx.xxx.xxx#31579: query (cache) ‘host.domain.net/A/IN’ denied
for EVERY request.
The setup is the same as I’ve seen it on working boxes as far as I can see. I don’t think it’s a firewall problem since it’s being written to the log as a rejection and because these machines are on two different networks entirely.
It could be a few things… you’ll probably need to post your BIND config file for us to assist.
If BIND is denying requests, it’s because of something setup in the BIND options.
Also, if you could post an example of a domain being hosted on your site, that’d be helpful, I’d like to run it through the “intodns.com” site to see what their reports say.
That is, your ns1 nameserver is showing up as the IP 98.190.138.12.
You may want to verify in your zone file, on ns1 (/var/named/wildwestcloud.com.hosts), and your slave zone file on ns2 (/var/named/wildwestcloud.com.hosts), that the numbers are correct.
If so, there might just be something weird cached somewhere, and it should clear up within a day or two.
For some reason, one of the sites can’t slave to the master server. I created the secondary as a master zone instead… but when I do that, the dns servers at Qwest start reporting the wrong address for our name servers.
but, after I hand added ns records for the non-slaving domain on the box, all of a sudden ns1’s address is reported as 65.100.96.186 by nslookup.
This is the same problem that happened yesterday. It fixed itself when I removed the errant entry you pointed out… today the problem got “fixed” when I removed all of my dns records from the problem domain on the secondary name server - the ones I had added.
Today I created a domain “inks2cash.com” on ns1 using 98.190.138.12 as the ip address for everything. It slaved on ns2 (65.100.96.186) okay and the records are setup the same on both servers… but nslookup reports the ip of inks2cash.com as 65.100.96.186… the ip address of the secondary name server and NOT the ip of the box it’s on!
It happened about the same time yesterday that quest starting reportin 65.100.96.165 as the addy for NS1 and NS2, even though NS1’s address is 98.190.138.12
When this name server ip screwup happens, all the sites start going to the default website on ns2… the one at /var/www/html…
