NT4 upgrade and namespace question

  • Thread starter Thread starter Dave
  • Start date Start date
D

Dave

I'm going to be upgrading an NT4 domain to W2K real soon. Only the
namespace question bothers me about this process.

We've been using the same domain (abcdef.com) internal as external. We
only have two names (www.abcdef.com and mail.abcedf.com) available
externally, neither external IP I want available internally, so I'll
create an alias for both with the internal IP. So far so good?


If I have a computer called fred (which would be fred.abcdef.com), can
the internal W2K DNS box be authoritative for internal computers (like
fred.abcdef.com), but NOT be authoritative for external boxes (like
mail.abcedf.com and www.abcedf.com)?


I know the "normal" way would be to create a subdomain for fred to
live in (fred.corp.abcedf.com), but I'm trying to not change 500+
laptops with references to the old naming convention used
(fred.abcedf.com).

We'll be going to AD after we get the last of the NT4 boxes taken care
of, but this will be a two-month process for us.

Thanks.
 
In
Dave said:
I'm going to be upgrading an NT4 domain to W2K real soon. Only the
namespace question bothers me about this process.

We've been using the same domain (abcdef.com) internal as external. We
only have two names (www.abcdef.com and mail.abcedf.com) available
externally, neither external IP I want available internally, so I'll
create an alias for both with the internal IP. So far so good?
Click to expand...

Don't really need an alias, just an A record will suffice, just giving it
the actual external IP address.

If I have a computer called fred (which would be fred.abcdef.com), can
the internal W2K DNS box be authoritative for internal computers (like
fred.abcdef.com), but NOT be authoritative for external boxes (like
mail.abcedf.com and www.abcedf.com)?
Click to expand...

In simplest terms, authorative just means that the DNS server has a Primary
or AD Integrated zone on the machine so therefore it's authorative for the
zone. Mere fact of it just being hosted on that DNS server. If internal name
is the same as external, called Split-Horizon, then the internal will NOT
forward out what it's authorative for. That's why you need to make the A
records metioned above in the previous paragraph.

This is of course assuming you will be forwarding out and not using your
ISP's DNS server addresses in any internal machine other than a forwarder
(or all kinds or errors will occur).
I know the "normal" way would be to create a subdomain for fred to
live in (fred.corp.abcedf.com), but I'm trying to not change 500+
laptops with references to the old naming convention used
(fred.abcedf.com).
Click to expand...

That's fine. There is no set "normalcy" when it comes to domain naming. As
long as it's in the proper hierarchal form and not a single label name,
(domain.com instead of just "domain"), then your're ok. However, the
split-horizon just requires additional administrative tasks, such as manual
A record creation, as al;ready mentioned, and a couple others if you want to
get http://abcdef.com to work too.
We'll be going to AD after we get the last of the NT4 boxes taken care
of, but this will be a two-month process for us.

Thanks.
Click to expand...

No problem and good luck!


--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
Back
Top