Creating a DC in Windows 2003 Server with another server running DNS

[RogerPictage]

I want to create a DC in Windows server 2003 but we have a linux server that handles the DNS. Will I run into issues when doing this?

 

[58sniper]

You'd be best to move your DNS to Active Directory. I'm assuming, of course, that you're referring to internal DNS (that used within your office to do name resolution for resources within your office).

Pat Richard, MCSE MCSA:Messaging CNA
Microsoft Exchange MVP
Want to know how email works? Read for yourself -

http://www.ietf.org/rfc/rfc2821.txt

 

[reynolwi]

Active directory needs DNS so it will be installed when you create your first AD server since they go hand in hand.

Wm. Reynolds
RRWDS | TxPSS

http://www.rrwds.com

http://www.txpubsafety.com

- - - - - - - - - - - - -
Network Error:
Hit any user to continue

 

[nedrudrelyt]

It is likely that you will need BIND version 8.2 or later running on your Linux boxes in order for AD to have all of the features that it needs in order to be happy. Below are some in of the things that AD needs. If you are looking for an enlightening article on the subject that is also below.

Some of the new DNS requirements of AD are:
Support of SRV records (RFC 2782).
Recommended support of dynamic updates (RFC 2136).
Recommended support of incremental zone transfer (IXFR) (RFC 1995).
BIND 8.2.2 or higher will support DNS extensions used by AD.

Useful article:

http://redmondmag.com/features/article.asp?EditorialsID=64

 

[markdmac]

This can be done but is a really bad idea because of the dependance that AD has on DNS.

No matter what you need to setup DNS on your AD, but you can have your L word DNS be authritative. Do not set your DNS to be AD integrated and you will be fine.

I hope you find this post helpful.

Regards,

Mark

Check out my scripting solutions at

http://www.thespidersparlor.com/vbscript

 

[58sniper]

reynolwi - it's only installed if you allow it. AD does not need Window based DNS. It will run with Bind, MetaIP, or anything else.

BUT - it's far more intuitive, efficient, and easy to manage if you're using AD integrated DNS.

Pat Richard, MCSE MCSA:Messaging CNA
Microsoft Exchange MVP
Want to know how email works? Read for yourself -

http://www.ietf.org/rfc/rfc2821.txt

 

[LWComputingMVP]

I disagree with Markdmac's comment

No matter what you need to setup DNS on your AD

AD requries DNS... but it DOES NOT require Windows to run DNS. But I do agree with evveryone else - you SHOULD run DNS on Windows for your AD Domain. Why? Companies have a nasty habit of blaming the other company when there's a problem. Run DNS on a non-Windows server and don't be surprised if Microsoft tries to blame the non-windows DNS server for problems if you call up asking for support and it's DNS related.

You would be wise to keep your existing DNS domain for public use and setup a NEW DNS domain for your Active Directory. In fact, that's what best practices says - your Active Directory domain should be using something like mycompany.local. So setup a Windows DNS server (better make it 2 for redundancy) for your new AD domain.