Newbie DNS question

  • Thread starter Thread starter Roger
  • Start date Start date
R

Roger

I've would like to know the correct implementation for installing DNS in my
envirnment. I have 12 branch locations, all of which need to be fully
functioning in the event our frame relay goes down. Each branch will have a
DC service dhcp address, but the DNS part I'm not so sure about. I have a
w2k dns server running at the main office which is now being used by all
branches. But I would think it would be better to put DNS at each branch as
well in the event they lose cotact with the main office, and lower the
amoutn of lookups going to the main office. Any sugggestions as to the best
way to accomplish this? Thansk in advance.

Roger
 
In
Roger said:
I've would like to know the correct implementation for installing DNS
in my envirnment. I have 12 branch locations, all of which need to
be fully functioning in the event our frame relay goes down. Each
branch will have a DC service dhcp address, but the DNS part I'm not
so sure about. I have a w2k dns server running at the main office
which is now being used by all branches. But I would think it would
be better to put DNS at each branch as well in the event they lose
cotact with the main office, and lower the amoutn of lookups going to
the main office. Any sugggestions as to the best way to accomplish
this? Thansk in advance.

Roger
Click to expand...

Does each of the 12 branch locations have a domain controller?

Are they all in one domain?

If all offices have a domain controller and are in the same domain, it is
just a simple matter of using an Active Directory integrated zone and
installing DNS on all the DCs. This will replicate the zone to all DNS
servers on the DCs.

While it is important that all branches have a DNS server, it is for more
critical to have a DC at each location. If you have a DC at each location
then installing DNS on those DCs only makes sense. Think about it this way,
the DC is found by its members through the records it has in DNS, so by you
only having DNS at the main office that makes DNS the weak link. DNS
requires very little system resources, probably no more than 5 or 6 MB of
memory, that puts DNS way down the list, so the hardware will hardly even
notice DNS running.
 
Thanks Kevin,
Can I assume then that DNS updates get replicated via the Global Catalog on
each DC (yes, there will be a DC at each location). I just wanted to
decrease unnecessary traffic if at all possible. In this case, I guess I
would then use each branches DNS server as a fowarder for internet requests
to the ISP DNS, or would it make more sense to just have my "main" DNS
server at my main location be the only forwarder, and have all branches
forward through that one?

Thanks again.
Roger
 
In
Roger said:
Thanks Kevin,
Can I assume then that DNS updates get replicated via the Global
Catalog on each DC (yes, there will be a DC at each location). I
just wanted to decrease unnecessary traffic if at all possible. In
Click to expand...

Having a DNS server at each location not only reduces DNS traffic but
increases DC availability because if the link did go down having a local DC
does little good if it cannot be located in DNS.

Incidentally I would suggest you have a Global Catalog at each site.
this case, I guess I would then use each branches DNS server as a
fowarder for internet requests to the ISP DNS, or would it make more
sense to just have my "main" DNS server at my main location be the
only forwarder, and have all branches forward through that one?
Click to expand...

Let each DNS server have its own forwarder to your ISP, definitely do not
forward these DNS servers to each other, that will set you up for a DNS
loop.
 
Back
Top