LinuxQuestions.org - [SOLVED] BIND9 Configuration Scenarios

Gurus:

How would you plan an expected move of a Primary Master bind9 host to a new network?

199.xx.xx.xx Ubuntu 8.04.4 LTS is the current host and domain.com resolves to it.
Server bind (Version: 9.4.2) is managed by Webmin.

64.xx.xx.xx is Ubuntu 12.04.1 LTS is the target host and domain.com will point there.
Server bind (Version: 9.8.1) is managed by Webmin.

On the new host I setup a root zone, and a master for domain.com and updated A and NS records
(ns[34].domain.com) manually.
nslookup domain.com 64.xx.xx.xx spits out the expected IP.

Once the domain.com contents and backends have been replicated, then we can just edit the DNS at the Registrar to point to the new host (either update A record to new host or change NSs...6 of one...1\2 dozen of the other...)

I just need to understand the "flow" better.

Warning: I do NOT want to affect anything on the current working host's bind9 configuration.

...a registered domain name or an imaginary one (but only if used on a restricted network).", so I'm off investigating that route.
How about alive but inactive?

What I DON'T WANT TO DO is spend days replicating this only to find out I'll have to cp the zone files over manually and update them manually in the end with "sed -ip.bak ..."

I continue to read:
https://help.ubuntu.com/community/BIND9ServerHowto
http://doxfer.webmin.com/Webmin/BINDDNSServer

God, I hope someone with some kung.fu can
actually read this and offer some guidance.

Plugging away slowly...

Thanks for your time.

Thanks!

Tue Jan 22, 2013 - 6:22:40 PM EST
I just wound up grinding it out manually.
a list of domains in a text file and dig can do wonders. :)

Code:

for i in `cat file`; do dig  +short $i @199.xx.xx.xx) ; done 

for i in `cat file`; do dig  +short $i ns @199.xx.xx.xx) ; done 

for i in `cat file`; do dig  +short $i mx @199.xx.xx.xx) ; done



for i in `cat file`; do dig  +short $i @64.xx.xx.xx) ; done 

for i in `cat file`; do dig  +short $i ns @64.xx.xx.xx) ; done 

for i in `cat file`; do dig  +short $i mx @64.xx.xx.xx) ; done

told me all I needed to know for the 22 domains.

Thanks!

Thu Jan 31, 2013 - 11:35:42 AM EST'
In the 'end', I just scp'd the zone files themselves from the old (199) server to the new (64) server and bounced named.