Benefits of domain being it's own DNS server...

We are setting up a DNS server for our 50+ domains on Windows Server 2003.

We have the option of setting up one domain as the DNS server or each domain as it's own DNS server.

i.e. dns1.domain1.com, dns1.domain2.com, dns1.domain3.com
versus each domain being under dns.domain1.com  

Does anyone know of any reasons for setting up each domain as it's own DNS server?  Does AOL give preference to mail from domains that have their own DNS server, for example?

Otherwise it seems easier to have just one DNS server for each domain.
hzukerAsked:
Who is Participating?
 
JammyPakConnect With a Mentor Commented:
I don't think anyone would say it's easier to have 50 DNS servers than to have 1....seems to me that I would prefer creating one DNS server, and adding 50 authoritative zones - I can tell you for sure that no ISP is going to have separate servers for each domain, and neither AOL nor anybody else is going to know/care.

this way, you have one server to setup, one NAT rule on the firewall, all DNS users can access the same cache, etc.
0
 
karel_jespersCommented:
in case domains need to access resources in ohter company domains,
the dns must also be forwarded in case the dns resolution fails to one or more dns servers who contain that information for all those domains
0
 
karel_jespersCommented:
reasons for setting up each domain as it's own DNS server:
eg
no traffic between domains needed to resolve dns resolution for resources within the own domain
karel
0
Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

 
karel_jespersCommented:
depends on the network structure
you can make on dns server responsible for all the domains
but then you must also take care that all those domains can also contact a local dns server on each site (domain)
so for each domain configure then also a dns caching only server
so each dns resolution will be cached (until the first reboot)
0
 
karel_jespersCommented:
50 domains
questions to be considered
(what dns resolution is needed on each domain, eg for local resources)
(what are the communication links between them)
(at what location do you place the dns  server)
at least one dns caching only server per domain (site)



0
 
JammyPakCommented:
Hzuker, these are just Internet domains, right? It sounds like you're not talking about Active Directory domains.

Karel, I think you are thinking about Windows AD Domains, otherwise I don't really understand what you mean in your posts. My impression is that this is just for 50 web-domains, not 50 offices running Active Directory. Also, DNS lookups aren't cached until the next reboot, they're cached for the length of the TTL setting for the domain that you're resolving - usually it's 24hrs.

Hzuker, if we haven't answered your question already, then please provide more information about what the scenario is and what you are trying to do.
0
 
karel_jespersCommented:
JammyPak:
yes i was talking about active directory domains
until reboot: i agree i configure my caching only servers with a ttl that is increased, so that i can assume that dns resolutions will be kept until the caching only server reboots

karel
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.