Dear all,
Currently I have 2 dns using bind on Debian v8 to run as dns server. One dns runs as master, and another one runs as slave. Slave dns gets record update from Master dns by doing the zone transfer, and those records are binary.
Now Master dns got issue, and I need to promote Slave dns to be master. Can you guide me how to do it?
Thanks,
Ly
Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230
How to promote slave dns to master dns
- GarryRicketson
- Posts: 5644
- Joined: 2015-01-20 22:16
- Location: Durango, Mexico
Re: How to promote slave dns to master dns
No, I can't , how ever there are some good guides available, you can read them, and after that if there is something you don't understand, maybe somebody here would be willing and have time to try to explain.
On Debian servers , How to promote slave dns to master dns
This one is pretty good, it includes for Debian:
https://www.garron.me/en/go2linux/how-s ... -bind.html
You also might want to read this , from a mailing list:
https://lists.isc.org/pipermail/bind-us ... 93899.html
"named.conf" file, and is more Debian specific,...
https://wiki.debian.org/Bind9
On Debian servers , How to promote slave dns to master dns
This one is pretty good, it includes for Debian:
https://www.garron.me/en/go2linux/how-s ... -bind.html
You also might want to read this , from a mailing list:
https://lists.isc.org/pipermail/bind-us ... 93899.html
This might be use full to you as well, it helps explain how to edit yourBut why have just a single master? If you're worried about the primary going down, just have a warm standby ready to go. To keep zone data in sync, you could use shared storage, a replicated database (BIND does support a database backend), or perhaps some sort of also-notify
configuration. To do the failover itself, you could use something like
Pacemaker/Corosync, ucarp, or similar. Just pass a VIP back/forth between
the two -- your NS records would only use the VIP.
***The big issue I see with converting a slave to a master is that you'd have to change all of your zone definitions, change your named.conf and do so under time pressure. Then, when the master came back online, you'd have to change your zone definitions again. With config management software, not that hard to do, but servers are cheap these days -- easier just to create a failover pair (or group) for your master, then stand up as many slaves (doing update forwarding) as you need. If you purchase a DNS appliance (Infoblox, SolidServer, Bluecat, etc.), this is how they handle things.
"named.conf" file, and is more Debian specific,...
https://wiki.debian.org/Bind9
"What we expect you have already Done"
==========
Old Website
======================
For the Birds
==================
What Does a Parrot Know About PTSD?
==========
Old Website
======================
For the Birds
==================
What Does a Parrot Know About PTSD?