named 9.3.2 zone transfer problem.

[rmueller58]

I am trying to troubleshoot a problem as to why when updates are made to our primary dns zones are not being updated with the changes.

I have two identical boxes, both running FC6 with named9.3.2 ..

We update the zone file in question on the primary, update the serial and restart the process. Do a dig on the secondary and the lookup fails. My best guess is someone screwed up the zone file, tested against a zone that is working modified a record, and the transfer and lookup was successful. Does it sound like a zone file problem?

To many danged hands in the cookie jar, our MSCE drives me nuts with his hunt and peck PICO crap and he likely jacked something up. this zone file is huge. I seem to recall there was a checkzone utility of some sort?

[Wilfred Chau_1 · Accepted solution]

do you see the zone transfer message in the log file?

is your secondary listed as NS for the domain?

[Ivan Ferreira]

This could be because:

1- The slave server does not have the apropiate permissions to write to the zone directory/files. Ensure that the named user has all access to the zone directory/files.

2- You are using DDNS. If you use DDNS, you must stop the DNS service, remove the .jnl zone file, update the zone and serial number, start the service.

[rmueller58]

Thanks all, find a typo courtesy of our microslop guy. Serial# mismatched.

Corrected the SN and restarted seconday is updating.

[rmueller58]

thanks