Visit Jeremy's Blog.
Go Back > Forums > Linux Forums > Linux - Server
User Name
Linux - Server This forum is for the discussion of Linux Software used in a server related context.


  Search this Thread
Old 01-21-2013, 06:00 PM   #1
LQ 5k Club
Registered: Jan 2011
Location: Nowhere near you, thank God.
Distribution: OSX Sierra
Posts: 8,576
Blog Entries: 15

Rep: Reputation: Disabled
BIND9 Configuration Scenarios


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 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 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 and updated A and NS records
(ns[34] manually.
nslookup 64.xx.xx.xx spits out the expected IP.

Once the 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:

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

Plugging away slowly...

Thanks for your time.


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.

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.


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.

Last edited by Habitual; 01-31-2013 at 11:39 AM. Reason: //Edit out comment before move


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
Bind9 configuration MX record IvanMP Linux - Networking 1 09-10-2012 11:57 AM
Bind9 Configuration Confusion debianfan Linux - Server 13 04-03-2010 09:14 PM
BIND9 configuration help... nali27 Linux - Server 3 09-28-2009 12:34 PM
Configuration problem bind9 poiuytrez Linux - Networking 9 06-13-2009 01:22 AM
Can't get bind9 configuration ok on Ubuntu 8.04 havan Linux - Networking 2 11-30-2008 03:08 PM > Forums > Linux Forums > Linux - Server

All times are GMT -5. The time now is 09:31 PM.

Main Menu
Write for LQ is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration