Subsequent queries from clients matching "cdn-redir" get the correct record immediately after nsupdate without fiddling with "rndc freeze/thaw", but querying from addresses that fall outside the view of "cdn-redir" now have the delay/rndc silliness.
My ultimate question If it were as simple as 42, I'd take it with open arms...
authoritative; # Use this to send dhcp log messages to a different log file (you also # have to hack to complete the redirection). I don’t think that they are that bad and personally I don’t have any problem editing them after that bind has rewritten them.
The format of a zone file is defined in RFC 1035 (section 5) and RFC 1034 (section 3.6.1).
This format was originally used by the Berkeley Internet Name Domain (BIND) software package, but has been widely adopted by other DNS server software – though some of them (e.g.
3.1 Edit /etc/bind/local: # # Make sure to change the ddns update style to interim: ddns-update-style interim; ignore client-updates; # Overwrite client configured FQHNs ddns-domainname ""; ddns-rev-domainname ""; # option definitions common to all supported networks... subnet .0 netmask 255.255.255.0 The dns database files are now being rewritten by the bind service.
option domain-name "home.lan"; option domain-name-servers lan; default-lease-time 600; max-lease-time 7200; # If this DHCP server is the official DHCP server for the local # network, the authoritative directive should be uncommented. Some people have mentioned that they think that bind messes up these files so that they are impossible to maintain.
I'd like to avoid having to "rndc freeze && rndc thaw" for fear of missing a dynamic update from the DHCP server.