Cloud DNS providers for secondary DNS

John W. Blue at
Wed Dec 30 00:52:27 UTC 2015

Hello Mike!

So you are tracking correctly what needs to be done: update your registrar and your master zone files.  Not knowing how the UI to the cloud and at the risk of stating the obvious, the only other agenda item that you would need to address is making sure that the cloud knows it is a slave.

If your secondary servers were normal BIND, you would need to tag your zones in the named.conf file as slaves.

Hope that is helpful.


-----Original Message-----
From: bind-users-bounces at [mailto:bind-users-bounces at] On Behalf Of Diggins Mike
Sent: Tuesday, December 29, 2015 6:40 PM
To: bind-users at
Subject: Cloud DNS providers for secondary DNS


I'm looking into providing secondary name service for my organization using a cloud DNS provider (D-Zone). We would transfer our zones to them using a standard zone transfer and they would publish them to their AnyCast DNS servers. I was going to simply add their DNS servers to my Domain Registrars list of authoritative name servers. Is it enough to do that or do I also need to add these (2) name server addresses to each of my zone files as well (I have about 50 zones).

;                                Name Servers
                        IN  NS
                        IN  NS
                        IN  NS	<== Addition
                        IN  NS	<== Addition

What happens if I do one without the other? I guess I don't fully understand the relationship between the name servers listed in the zone versus the ones found in my domain record. I'm running BIND locally, if that matters.

Please visit to unsubscribe from this list

bind-users mailing list
bind-users at

More information about the bind-users mailing list