Re: Help needed with setting up a secondary DNS server


"BreadSlicer" <BreadSlicer@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:43803D9D-2C34-40C8-BC11-D94576C5CE8B@xxxxxxxxxxxxxxxx
Hello All,

I have been tasked to develop a disaster recovery plan on our network that
now has a second Win2k DC that I was also going to configure as a
secondary
DNS server (which would be handy in the event of a disaster) but let's
just
say things did not go well.

Better would be two AD integrated DNS servers on the two DCs.

At first everything appeared to be OK but overall network speed started to
degrade more and more until it was crippling internet access for everyone.
I
had to uninstall the DNS from the secondary server and delete all
references
to it from the primary DNS server which got us back to where we were.

Then you had failed to setup the zone correctly (or this had nothing to
do with the problems.)

I followed the instructions I found here:
http://www.eng.uwaterloo.ca/~hon/windows2000/DNS-HOWTO.html step by step
but
clearly something was wrong with that and admittedly I don't really
understand how the forward/reverse lookup zones work.

Are you using AD Integrated on the FIRST DC?

In that case, you should merely have to add the DNS
server to the second DC and it will (usually) populate the
DNS zone automatically.

I'm currently trying to find the best resource/advice on developing this
DRP
which involves DNS (which is where I'm at right now) and any and all
advice
would be much appreciated by all.

Make sure that your internal DNS clients (including DCs) point
STRICTLY at this DNS server SET. Never point them to the
ISP or any DNS which cannot resolve your internal resources.

I would be happy to provide any additional info anyone may need.

Thanks in advance!


--
Herb Martin, MCSE MVP
www.LearnQuick.Com


.

Relevant Pages

  • Re: DNS domain name same as AD domain
    ... Or should I change the DNS domain first to something else? ... For any host name that you wish to have access from both your internal network and from the external Internet you need scenario 1, although it is the most DNS-intensive over time. ... Each DNS zone is authoritative for the zone of that name so therefore the external DNS zone and internal AD/DNS zone will NOT replicate with each other thereby prevent internal company records to be visible to the outside Internet. ...
    (microsoft.public.windows.server.dns)
  • Re: .com versus.local
    ... DNS and public names on the internet etc but I have never had someone ... All DNS entries are help at the ISP. ... external Internet you need scenario 1, although it is the most DNS-intensive ... Each DNS zone is authoritative for the zone of that name so ...
    (microsoft.public.windows.server.dns)
  • Re: AD DNS naming
    ... my e-mail and Site Internet." ... infrastructure (mostly with respect to DNS and VPN). ... If you do not select this option and go with scenario 2 ... Each DNS zone is authoritative for the zone of that ...
    (microsoft.public.windows.server.dns)
  • Re: How many Global Catalog Servers are needed?
    ... make for an AD DNS FQDN domain name, ... external Internet you need scenario 1, although it is the most DNS-intensive ... Each DNS zone is authoritative for the zone of that name so ...
    (microsoft.public.windows.server.active_directory)
  • Re: Domain naming strategies
    ... a delegation to an unreachable internal dns server. ... my e-mail and Site Internet." ... network and from the external Internet you need scenario 1, ... Each DNS zone is authoritative for the zone of that name so ...
    (microsoft.public.windows.server.active_directory)
Loading