BIND Problem ...
Hey all ... I've recently converted my employers to switch their primary DNS server from an old NT4 box to Linux, which is good for me, because now I feel a little bit more in place. See, EVERYTHING here is Win2k/NT4, which I don't have a large amount of experience administrating.
Anways, my problem is with BIND. We have a class C from our upstream provider, and the way they've decided to delegate reverse DNS to us is to do zone transfers from our nameserver to theirs. The ICANN record lists their nameserver (zeus.ihermes.com) as the nameserver that provides reverse resolution. So, I have our nameserver setup as the master for 125.181.208.in-addr.arpa, and the sysadmin there has set their server up to be a slave. If I change the serial number in the zone file, and do a restart of named, it sends to notify to zeus, but I don't ever receive (or at least see) a message acknowledging recipt. If I change the serial on one of the other zones and reload, the transfer of the zone goes as planned (albeit a different nameserver).
So, my question is, is there any way I can tell if the sysadmin has actually setup their nameserver, or if I can make bind be very verbose about rejections and such? For reference, our primary nameserver is ns1.n-magic.net (188.8.131.52), our secondary is ns2.n-magic.net (184.108.40.206) and our ISPs primary DNS server is zeus.ihermes.com (220.127.116.11). Listed below is a sample log entry, zone file, and the relevant entry in /etc/named.conf:
( Collapse )