Bind9 not updating zone serial
A server can be the Start of Authority (SOA) for one zone, while providing secondary service for another zone. ( 2 ; Serial 604800 ; Refresh 86400 ; Retry 2419200 ; Expire 604800 ) ; Negative Cache TTL IN A 192.168.1.10 ; @ IN NS ns. ( 2 ; Serial 604800 ; Refresh 86400 ; Retry 2419200 ; Expire 604800 ) ; Negative Cache TTL ; @ IN NS ns. client 192.168.1.10#39448: received notify for zone '1.168.192.in-addr.arpa' zone 1.168.192.in-addr.arpa/IN: Transfer started.
I modified the example file to give box an address of 192.168.1.21).
Please visit this page to clear all LQ-related cookies.
This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant.
Telling a BIND 9 name server to reload a dynamically updated zone has no effect, since the name server doesn’t expect you to update the zone manually.
Note: There are some issues with this Howto, too numerable to fix quickly, and it requires bringing up to standard. in all other places, the document uses the machine name example ns.Welcome to Linux Questions.org, a friendly and active Linux Community. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration.