Bind9 dns zone not updating
If it's a regularly-configured Ubuntu BIND server, it should be sufficient to install the bind9 package on the new machines, copy the contents of /etc/bind to the new machines, then adjust the settings on each machine to talk to the new one, change the delegations (or IP addresses, if appropriate) and get on with life.For a seamless (zero-downtime) migration, do one machine at a time. Failing that, give Now, the funny thing is, I am 99.999% sure that the permissions were already set correctly (owner/group named, with 660 permissions). Also, I added has to guess what zone the update applies to when you omit that ("based on the rest of the input" according to the manpage), and I see lots of room for that assumption to be wrong given how many quads deep this zone is. Since I'm right in the middle of migrating our servers to new hardware, I'll toss into the ring for this one.First, if at all possible, do not expose your master server (the one where all the changes should occur) to the internet.
Make sure that the RR files are in /etc/bind as well (Fed/Cent/RH they are in /var/some/where/) for the fastest switch over.nsupdate then spits me back to the shell, and there are no errors (or messages of any kind) in the logs. I've tried the reverse zone update with and without trailing periods. ( 5 ; serial 604800 ; refresh (1 week) 86400 ; retry (1 day) 2419200 ; expire (4 weeks) 604800 ; minimum (1 week) ) NS ns1. I have the feeling I'm missing something basic, but I can't figure out what it is. Here are my config files, and other info: $ORIGIN .
I feel like the differences are trivial enough to not make a difference in functionality, but of course, I'm far from an expert.
try to end up with the new servers having the same IP addresses as the old).