WINDOWS 2003 DNS NAMESPACE QUESTION

  • Thread starter Thread starter sam1967
  • Start date Start date
S

sam1967

Hi

Im setting up a small Windows 2003 network and am wondering what DNS
name i should use.

The charity use charityname.org.uk at present for their external DNS
name and I am thinking of using charityname.internal for the internal
DNS name.

any comments on the wisdom of this approach ?
 
In
Hi

Im setting up a small Windows 2003 network and am
wondering what DNS name i should use.

The charity use charityname.org.uk at present for their
external DNS name and I am thinking of using
charityname.internal for the internal DNS name.

any comments on the wisdom of this approach ?
Click to expand...

There are benefits and drawbacks, the benefit is that the name will not
conflict with your pubic domain name.
The drawback is if you have VPN clients you will need to use hosts files on
the VPN clients to help resolve internal servers.
I recommend using a subdomain level of the public domain for the internal
domain, e.g. internal.charityname.org.uk. This way you can delegate the
internal name in the public domain to the internal IP of the internal DNS
server. This method makes the internal domain name seamless _with_ the VPN
connected and useless _without_ the VPN connected.
Integrating Your Active Directory Namespace Into an Existing DNS
Infrastructure Without Name Overlap:
http://www.microsoft.com/windows200...scenarios/dns_int_adns_to_dns_inf_wo_olap.asp
 
Kevin,
Great link. I agree with your approach on building out the name space for
DNS. Easiest to delegate a zone/subdomain to your AD configuration and you
are good to go. Nice thing is that you always know who is authoritative for
your domain! Plus, you avoid problems with things like certificate services
and SPF.

Regards,
Ed Horley
Microsoft MVP Server-Networking
 
Back
Top