#Unexpected rcode notimp resolving verification

This happens when the master is not responding to a zone transfer request from one of the slave DNS servers.

#Unexpected rcode notimp resolving verification

There are other potential issues that could come up beyond the journal file being out of sync. That means your forwarder (158.152.1.58 ) cannot resolve those DNS requests. I have searched for, and read most of the related threads from back in 2017 about verification failures due to DNS problem: SERVFAIL looking up CAA for XXX - the domain’s nameservers may be malfunctioning, resulted by the server answering NOTIMP (Not Imlemented, aka. If you are running a bind server, you may have come across this error message: named 2465: zone /IN: refresh: unexpected rcode (SERVFAIL) from master 10.1.2.353. Here’s what that would look like in the logs on the master server: dns named: client 10.1.2.11#59633/key rndc-key (): transfer of '/IN': AXFR-styleĭns named: client 10.1.2.11#59633/key rndc-key (): transfer of '/IN': AXFR-style Once the service comes up, it should immediately load the zone file and send a notify to the configured slave servers prompting them to initiate a zone transfer. Then restart the bind service: sudo service bind9 restart On the master dns server, go to the path where zone file is located and delete the corresponding “jnl” file. On an Ubuntu server running bind9, the fix for this is to simply delete the journal file for the zone. This happens when the master is not responding to a zone transfer request from one of the slave DNS servers.Ī quick check of the logs on the master DNS server will show a corresponding message: dns named: zone /IN: journal rollforward failed: journal out of sync with zoneĭns named: zone /IN: not loaded due to errors. If you are running a bind server, you may have come across this error message: named: zone /IN: refresh: unexpected rcode (SERVFAIL) from master 10.1.2.3#53