Re: DNS Question - In Place Upgrade NT>2003

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Joe Wu [MSFT] (joewu_at_online.microsoft.com)
Date: 03/15/04 

Date: Mon, 15 Mar 2004 08:31:21 GMT

Hello,

Thank you for your post, and also thanks to Herb for his suggestions.

It is good to use different internal and external domain names. This
creates a barrier between your internal resources and the Internet, and you
will gain the following advantages:

- The internal namespace is not registered with Internic. Internal
resources are not exposed.

- Proxy clients need to exclude only the external namespace, which allows
any external DNS queries to the Internet to proceed through the Proxy
Server.

Reference:

285983 Considerations for Designing Namespaces in Windows 2000-Based Domain
http://support.microsoft.com/?id=285983

By the way, we can keep the current NetBIOS name of the domain. During the
upgrade, please choose an appropriate DNS domain name. If you point the DC
to use a DNS server that support dynamic update (you can also build DNS on
the DC), a new DNS zone will be created for the domain.

If you have any questions or concerns, please do not hesitate to let me
know. I am standing by to help you. Thank you for your time and cooperation!

Regards,
Joe Wu
Product Support Services
Microsoft Corporation

Get Secure! - www.microsoft.com/security

====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------
|From: "Herb Martin" <news@LearnQuick.com>
|References: <7tk650t7rfknbpjidubhrcqifof2h5aa74@4ax.com>
|Subject: Re: DNS Question - In Place Upgrade NT>2003
|Date: Mon, 15 Mar 2004 00:23:56 -0600
|Lines: 57
|X-Priority: 3
|X-MSMail-Priority: Normal
|X-Newsreader: Microsoft Outlook Express 6.00.3790.0
|X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
|Message-ID: <uLPiZYlCEHA.1588@tk2msftngp13.phx.gbl>
|Newsgroups: microsoft.public.windows.server.migration
|NNTP-Posting-Host: cs6625203-102.austin.rr.com 66.25.203.102
|Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!tk2msftngp13.phx.gbl
|Xref: cpmsftngxa06.phx.gbl microsoft.public.windows.server.migration:8754
|X-Tomcat-NG: microsoft.public.windows.server.migration
|
|> Questions:
|> 1. Will changing my internal DNS zone from CITY.ORG to CITY.INT
|> adversely affect my clients? So far, I'm figuring on changing DHCP for
|> the clients and manual changes for my servers, but maybe I'm missing
|> something else.
|
|I would rename the domain (while under NT) or continue to use the
|NetBIOS name as the BASIS of the new DNS zone/domain name.
|
|> 2. To stay compatible for some legacy services, I'm supposing I'll
|> need to keep my NetBIOS name of MN. What will be my FQDN's be for
|> users/machines.... (e.g. joed.mn.city.int / host1.mn.city.int) ? Will
|> it really matter?
|
|It will be the "machine name" prefixed to whatever you give the
|DNS domain name -- the NetBIOS name is technically irrelevant
|here.
|
|BUT, I strongly suggest that you use the NetBIOS name as the
|first (left most) tag or label of the DNS name. If you don't like the
|current name, rename the domain while under NT -- it's hard to do
|later.
|
|> 3. Will I need to add a new internal zone on my DNS servers (e.g.
|> MN.CITY.INT)
|
|Not unless your Win2003 domain has this name. That would NOT
|be the domain "City.int" but a child of this name.
|
|What you propose will work, but it is ugly, confusing, and will haunt
|you for years.
|
|--
|Herb Martin
|"CB" <question@tech.net> wrote in message
|news:7tk650t7rfknbpjidubhrcqifof2h5aa74@4ax.com...
|> Greetings,
|> Thank you in advance for any assistance.
|>
|> Current Setup
|> NT4 Domain - 225 clients (9X, 2K, XP, mac)
|> Servers: 1 PDC - 3 BDC - 16 Standalone (NT4/2K)
|> NetBIOS Domain Name - MN
|> Internal DNS Zone - CITY.ORG (so FQDN's for hosts is HOST.CITY.ORG)
|> External DNS (managed by ISP) - CITY.ORG
|>
|> Proposed Setup
|> PDC In Place Upgrade to 2003 AD
|> Keep current NetBIOS name - MN
|> Keep current Internal DNS zone CITY.ORG (if necessary) or rename to
|> CITY.INT (if possible)
|>
|>
|> Thanks again for any help,
|> CB
|
|
|

Relevant Pages

  • Re: What is FQDN ?
    ... Active Directory setup Wizard didn't add my computer name which is "DC1DNSAD". ... Connection-specific DNS Suffix. ... I think at one Point AD Setup Wizard ask you Question What should be NETBIOS ... How to Configure OEx for Internet News ...
    (microsoft.public.windows.server.dns)
  • Re: computer name length issue
    ... This length is reflective of the old NETBIOS computer name which was 8 characters, 15 on then newer Windows OSes. ... However, what Microsoft did a long time ago when they finally added Internet support over its NETBIOS based LAN support, was WINS which ties the IP address of the machine with the netbios computer name. ... That is only TRUE when the network administrator has made it that way via DNS and WINS. ...
    (microsoft.public.vc.language)
  • Re: Urgent! New router and big disaster
    ... Both NICs should point to his internal IP for DNS. ... forward ports to it reliably in the router. ... I should have been more clear about internet connection.. ...
    (microsoft.public.windows.server.sbs)
  • Re: Unable to join my new XP pro wkstation to the Win 2K pro server domain.
    ... You must have an internal DNS zone for each AD domain that is ... maintained separately from the Internet versions of these zone (if ... You need an INTERNAL DNS server for the zones. ... Herb Martin> tia ...
    (microsoft.public.windows.server.networking)
  • Re: Urgent! New router and big disaster
    ... Both NICs should point to his internal IP for DNS. ... You should give your SBS a fixed external address so you can forward ports to it reliably in the router. ... I should have been more clear about internet connection.. ...
    (microsoft.public.windows.server.sbs)