secondary DNS, load required

Im looking at setting up a secondary DNS server incase the primary goes
down, but from my understanding a backup dns server is not only used as a
backup, It actualy does load balancing between it and the primary. Is it
possible to setup a dns server so it is only used in the event the primary
is down, if not what sort of data rates are you looking at for an average
secondary dns server.

Many Thanks

"Adrian Brown" <(E-Mail Removed)> wrote in message news:(E-Mail Removed)...
> Im looking at setting up a secondary DNS server incase the primary goes
> down, but from my understanding a backup dns server is not only used as a
> backup, It actualy does load balancing between it and the primary. Is it
> possible to setup a dns server so it is only used in the event the primary
> is down, if not what sort of data rates are you looking at for an average
> secondary dns server.
>
> Many Thanks
>


An additional DNS does not work that way. The client side resolver, and keep in mind, every machine has a client side resolver that is used to send a request to a DNS server, including a DNS server itself, is what does the work. You can setup the additional DNS server, and I assume you mean promote an additional DC in the domain and make it a DNS server. THen you would specify the IP of this new DC/DNS as the second entry in all machines' IP properties. If the first one does not answer, and only when the first one does not answer, (if it answers with an NXDOMAIN, meaning it doesn't know, then that is an answer), then it would go to the second entry after a timeout period, then removing the first entry in the list for 15 minutes, before it resets the list.

Now assuming you mean to have the additional DNS for a domain, it would need to be a DC with DNS installed, and in this cased, it would be called a replica DC, and DNS on it would not be called a Secondary in the sense of the term meaning it only has a read only copy of the zone, in essence a standard zone. When you install DNS on a DC, and the zone is AD integrated (not a standard zone), then the data is stored in the AD database and automatically replicates when you install it. So when you do install DNS after you promote the server, wait about 15 - 30 minutes and the zone auto appears. Then you can add it as the second entry in IP properties of all machines.

I hope that makes sense.

--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSA Messaging, MCT
Microsoft Certified Trainer
(E-Mail Removed)

For urgent issues, you may want to contact Microsoft PSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

"Efficiency is doing things right; effectiveness is doing the right things." - Peter F. Drucker
http://twitter.com/acefekay