DNS Advice for migration from NT4 domain to 2003 AD ?

Discussion in 'DNS Server' started by RobC, Apr 5, 2005.

  1. RobC

    RobC Guest

    Our Current Setup is as follows:

    We currently have an NT4 domain called CLUB_260 that uses a Win2000 WINS
    server for name resolution so that the DC's can find each other across
    routers. All other PC clients and member servers are Win 2000, and use
    either boadcasting or the WINS server for netbios name resolution.
    Specifically, our branch office clients broadcast on their local LAN to find
    their local DC, while at Corp, since we have several different subnets, all
    clients and servers register with the one WINS server so they can find each
    other if needed. As far as DNS, our main firewall that provides internet
    connectivity for the entire Org (both Corp and branch offices) is also our
    one and only internal DNS server. It is a Sun box running some form of UNIX.
    It has an internal DNS namespace of abc.com (for example) and all Windows
    clients use it's internal IP address as their Primary DNS server. While it
    is used primarily for forwarding name resolution requests on to the internet,
    we do have a handful of internal unix servers whose host names are resolved
    for clients by this DNS server. For example, Outlook Express contacts it's
    POP3 mail server, itmail, by referring just to that name as the server name,
    itmail. Since itmail is a unix box with an FQDN of itmail.abc.com it is
    resolved by our internal DNS server. All our clients have the TCP/IP
    setting: "DNS Suffix for this connection" = abc.com.
    Hence, internal unix host name resolution works.

    We are about to migrate our NT4 domain to 2003 Server AD. The path was to
    take a new box, make it an NT4 BDC, promote it to PDC, install 2003 server,
    and then install AD.


    Should we give the upgraded domain a DNS name of club260.abc.com and on our
    existing Sun DNS server delegate the responsibility of the club260.abc.com
    namespace to the newly upgraded 1st 2003 DC? Is that the correct way to do
    it or not? If so, do we then just tell the 2003 AD Integrated DNS server to
    forward unresolved queries up to the Sun firewall that is responsible for
    abc.com internally? Furthermore, do we really even need to change the client
    settings on the PC's at all, if we don't need them to register their host
    names in DNS. Is it true that it's really only the DC's that need DNS to talk
    to each other. Can't the PC's just keep using broadcasts and WINS for name

    Any advice would be greatly appreciated.
    RobC, Apr 5, 2005
    1. Advertisements

  2. RobC

    Darren D Guest

    This is just my two cents . I think the simplest approach would be to use
    integrated DNS win2003 in this way the SERVE records are automatically
    created for you on the new Win2003 DNS server . Then you can use a number of
    options ,one of the simplest approach would be to utilize a new feature
    within DNS 2003 called conditionally forwarding as a result I would suggest
    you have your clients point to the new integrated DNS 2003 server for all
    internal name resolution . In addition, for DNS name not resolve you can use
    conditional forwarding which you can setup to point to you SUN box..
    Hope this helps..
    Darren D, Apr 5, 2005
    1. Advertisements

  3. RobC

    RobC Guest

    So, should we be setting the DNS name of our new AD domain to be a subdomain
    of abc.com ........ i.e. club260.abc.com or should it be something else
    like corp.local? I mean, it can't be called abc.com, can it since there
    is already the Sun box that is hosting that name internally. Is that correct?
    RobC, Apr 5, 2005
  4. RobC

    RobC Guest

    So we should be making the DNS namespace for the upgraded domain to be
    something like club260.abc.com ? is that correct?
    RobC, Apr 5, 2005
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.