DNS Setup

[Guest]

I have a client that has an AD primay NT domain\zone called corp.contoso.com.
This is the primary zone for all his Internal computers. He needs to have
records created such as www.contoso.com and mail.contoso.com. Since there is
no zone by this name and the corp.contoso.com zone is the only domain in the
forest, there is no dns zone just called contoso.com. Can he create a new
different zone called contoso.com? This also then automatically creates the
subdomain of corp.contoso.com in this new zone. Will deleting this zone
cause any internal dns resolution issues? If the subdomain was left intact,
there would be no entries for all the computers in the real domin
corp.contoso.com.

Suggestions?

 

[Herb Martin]

I have a client that has an AD primay NT domain\zone called
corp.contoso.com.

What is an "AD Primary NT domain?" Or zone for that matter?

NT doesn't do AD, except as an (additional) BDC in a Win2000+
AD Domain.

This is the primary zone for all his Internal computers. He needs to have
records created such as www.contoso.com and mail.contoso.com.

These are unrelated to your current zone so do what you must....

Since there is
no zone by this name and the corp.contoso.com zone is the only domain in
the
forest, there is no dns zone just called contoso.com. Can he create a new
different zone called contoso.com?

Sure, but chance are (from the names but you have obfuscated so
we cannot be sure) that the parent domain/zone (contoso.com) is
PUBLIC on the Internet and so should just be kept (or placed) at
the REGISTRAR in 99.99% of the cases.

This also then automatically creates the
subdomain of corp.contoso.com in this new zone.

No, nothing like that is automatic -- and if the parent is
a public zone (on THE Internet) it might be totally irrelevant or
even undesirable.)

But it is generally trivial to delegate the child zone (e.g.,
corp.contoso.com)
-- for instance in the MS DNS GUI you just right click and delegate.

Will deleting this zone
cause any internal dns resolution issues?

Deleting what zone? You must not delete the zone for the AD
Domain, other zones are IRRELEVANT to the domain (itself),
although you may (or may not) need them for other reasons.

If the subdomain was left intact,
there would be no entries for all the computers in the real domin
corp.contoso.com.

If the two domains are contoso.com and corp.contoso.com then
the SUBDOMAIN is "corp.contoso.com" or more usually it is
called the CHILD domain while the other (contoso.com) is the
PARENT domain/zone.

 

[Kevin D. Goodknecht Sr. [MVP]]

I have a client that has an AD primacy NT domain\zone called
corp.contoso.com. This is the primary zone for all his Internal
computers. He needs to have records created such as www.contoso.com
and mail.contoso.com. Since there is no zone by this name and the
corp.contoso.com zone is the only domain in the forest, there is no
dns zone just called contoso.com. Can he create a new different zone
called contoso.com? This also then automatically creates the
subdomain of corp.contoso.com in this new zone. Will deleting this
zone cause any internal dns resolution issues? If the subdomain was
left intact, there would be no entries for all the computers in the
real domin corp.contoso.com.

Suggestions?

Can I assume that you need these records because the sites are hosted on a
local server?
That would be the only reason because your DNS shouldn't be authoritative
over contoso.com since its domain is corp.contoso.com.

If the sites are hosted locally create zones for these names
(www.contoso.com and mail.contoso.com) then, create host records in these
zones, leaving the name field blank, and give them the local IP of the
server hosting them.