Tech Support > Operating Systems > Windows 2003 > non-RFC-compliant domain naming
non-RFC-compliant domain naming
Posted by J e r e m y on February 2nd, 2004


I use domain.local in every internal namespace I setup. I don't know if that
is RFC compliant but it seems to be a widely used standard. I also host
internet services (email, web) on the same machine in some cases, and host a
standard primary DNS zone for the external namespace on that same server.

HTH,
J e r e m y

"John H" <anonymous@discussions.microsoft.com> wrote in message
news:51A8A04E-70F2-4DB8-9522-2D0820E59B6F@microsoft.com...
services are hosted offsite?



Posted by John H on February 2nd, 2004


Thanks Jeremy. I was looking a for reason not to use the internal company.pri naming, but I'm glad it's common practice. I even ran all the unlikely scenerios through my head: i.e.: adding an exchange server to the domain, or even bringing the websites local, but I assumed that I could create aliases and forwarders for those. Thanks again

John


Similar Posts