http://www.thelinuxwiki.com/index.php?action=history&feed=atom&title=Named_slave_zone_refresh_failingNamed slave zone refresh failing - Revision history2026-04-29T07:26:32ZRevision history for this page on the wikiMediaWiki 1.21.5http://www.thelinuxwiki.com/index.php?title=Named_slave_zone_refresh_failing&diff=191&oldid=prevNighthawk: Pushed from Themanclub.2013-04-12T15:58:03Z<p>Pushed from Themanclub.</p>
<p><b>New page</b></p><div><br />
== problem description ==<br />
<br />
Trying to refresh a slave zone by updating master, deleting slave db file in /etc/bind/pri, then restarting named. The file doesn't "refresh" and an error is received as follows.<br />
<br />
'''error:''' in /var/log/messages for named<br />
zone example.com/IN: refresh: unexpected rcode (SERVFAIL) from master 191.168.1.254#53 (source 0.0.0.0#0)<br />
<br />
the SERVFAIL was caused because the master named didn't load the zone on startup due to errors. Upon further investigation I found the following in /var/log/messages on the master dns server:<br />
Feb 1 17:26:51 heinkel named[5666]: zone example.com/IN: not loaded due to errors.<br />
Feb 1 17:26:51 heinkel named[5666]: zone example.com/IN: not loaded due to errors.<br />
<br />
<br />
== solution ==<br />
<br />
fixed master zone file error. In this case I was trying to use a # incorrectly as a comment char instead of a ; <br />
<br />
[[category:bind]]</div>Nighthawk