Domain name ! New installation Windows 2003

[vectorw16]

Hi everyone,

I'm planning a new installation of windows 2003 ! Right now I'm running NT4! But I wan't a clean install !

But my question is about the domain name !

Right now it's something like "ABCDE_City" but in 2003 many peoples suggest to call the domain like the web site "Company.com" or "city.company.com" !

On my side our website name looks like "companyCity.com" and our website is hosted outside! Should I call the domain "companyCity.com" anyway ?

If the company grow ?

Any suggestions ?
Thanks

 

[wdoellefeld]

Personally I have an affinity for keeping the internal and external name the same. I'd keep it the same.

FRCP

http://www.frcp.net

 

[NickFerrar]

I'd agree, our AD name is the same as our external DNS name - although some advise you make it different (such as if company.com is the external DNS then call the AD forest company.local).

 

[dkediger]

This Microsoft White Paper - although targeted to SBS, explains the pros and cons of your options:

http://support.microsoft.com/default.aspx?scid=kb;en-us;296250

 

[Jpoandl]

Just my opinion:

I would never name the internal and external domain name the same. This may cause problems with DNS resolution (because Windows 200x is DNS based). Also, it is not a good idea to name them the same for security reasons.

If my external domain name was "companyCity.com", I would name my internal domain name company-city.local, or ccity.local, or ccity.net, etc. (Also, I wouldn't use an "_" underscore....use a "-" dash instead.)

Underscores are not <really> supported by MS DNS. "-" dashes are fully supported. Using the underscore may have been the cause of your problems.

Also, when you setup your DC, make sure that your are not pointing to your ISP DNS servers. Because Windows 200x domains need DNS, the DCPROMO wizard will automatically install DNS locally on the server. So, your local TCP/IP properties on the server should point to itself and only itself for DNS.

-later





Joseph L. Poandl
MCSE 2003

If your company is in need of experts to examine technical problems/solutions, please contact

http://www.NJCOMPUTERNETWORKS.com

(Sales@njcomputernetworks.com)

 

[vectorw16]

Thanks for all your answer !
Joseph : my server is not set up yet! I was not planning to put an underscore in my 2003 domain name ! My NT4 domain has an underscore !

But what do you think of split-brain dns ?

http://www.microsoft.com/serviceproviders/whitepapers/split_dns.asp

 

[Jpoandl]

Vectorw16,

Are you an ISP? Are you a DNS expert? No, then I wouldn't attempt

http://www.microsoft.com/serviceproviders/whitepapers/split_dns.asp

Joseph L. Poandl
MCSE 2003

If your company is in need of experts to examine technical problems/solutions, please contact

http://www.NJCOMPUTERNETWORKS.com

(Sales@njcomputernetworks.com)

 

[vectorw16]

Why not?
It doesn't look that complicated !

I've ask one of my friend (MCSE, MCT, Consultant) he told me it's his favorite way of implementing DNS !

Thanks for your opinion !

 

[Jpoandl]

Its really not that complicated...but when someone comes into a string with this question:

But my question is about the domain name !

Right now it's something like "ABCDE_City" but in 2003 many peoples suggest to call the domain like the web site "Company.com" or "city.company.com" !

On my side our website name looks like "companyCity.com" and our website is hosted outside! Should I call the domain "companyCity.com" anyway ?


And then goes to this:

http://www.microsoft.com/serviceproviders/whitepapers/split_dns.asp

...I would have my doubts...

---anyway, good luck, let us know if you have any problems...



Joseph L. Poandl
MCSE 2003

If your company is in need of experts to examine technical problems/solutions, please contact

http://www.NJCOMPUTERNETWORKS.com

(Sales@njcomputernetworks.com)

 

[dkediger]

I would concur with JPOANDL - don't complicate it unless you know you need it.

I favor the .local AD name. DNS is pretty simple this way. All clients, servers, and DC's point to the internal DNS and you enter external DNS forwarders in the DNS MMC.

All cut and dried, internal queries stay internal, external stay external, nothing to muck around with.

 

[vectorw16]

lol thanks for your concern, you are right my question sound like a newbie. I'm really more famillar with NT 4 !

But I'm MCSA 2003 and I like challenges ! Next time I'll ask more challenging question !

Thanks

 

[vectorw16]

dkediger,

How do you know you need it ? It's more a choice than a need !

But you are right it's more "cut and dried" the other way !

 

[Jpoandl]

The MS Article says why you might need it... if you are an ISP.

This document describes how to set up a split-brain DNS configuration, which Internet service providers (ISPs) can use to provide secure DNS service to allow both internal and external name resolution requests. You can use a split-brain configuration to separate and secure dynamic DNS servers running on an internal or customer network from publicly available, external DNS servers.


You can find a good deal of information on DNS configuration for enterprise installations, but ISPs who want to provide more consistent domain namespaces for customers can implement split-brain DNS.


Joseph L. Poandl
MCSE 2003

If your company is in need of experts to examine technical problems/solutions, please contact

http://www.NJCOMPUTERNETWORKS.com

(Sales@njcomputernetworks.com)

 

[dkediger]

I'm simply applying the KISS principle. Unless I've got an internal host/service that absolutley *needs* the external domain name - I'm drastically reducing my exposure to DNS issues.