On Tue, 2018-01-23 at 09:53 -0700, Grant Taylor via bind-users wrote: > > Could you try disabling DDNS updates for a little while?
That's effectively what I have done. I set up a second server configuration running new zone on a different IP address and pointed the DHCP server at it so that the DHCP server is no longer sending DDNS updates to the server that is having these intermittent outages. I've set up CNAME pointers from the main server to the new server for the names (of DHCP clients) that need to be resolvable as well as for a reverse zone on the new server. > Maybe you'll > get lucky (for a given value of luck) and find that the problem > continues happening even with DDNS updates disabled. Thus you will > have > a reasonable idea that the issue is not related to DDNS updates. Exactly my goal. I'm fairly sure that the problem is going to stop happening now that the server is no longer processing DDNS updates. Unfortunately it's impractical to run like this for the long term as any DHCP client that comes into the network ought to be able to be resolvable by it's name in the main zone, but that would require CNAMEs for any and every possible name that could show up in a DHCP client. Cheers, b.
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
