Re: NT4 to Windows 2003 : which dns ?
From: Dana Brash (dbrash_at_gmail.com)
Date: 11/07/04
- Next message: JD: "Re: Stupid Americans! -- Stupid... Stupid... STUPID!!! _____________---_ bugbeqy"
- Previous message: Tony Scarola: "Re: DNS Domain Name Extension Suggestions?"
- In reply to: Tony Scarola: "Re: NT4 to Windows 2003 : which dns ?"
- Next in thread: Tony Scarola: "Re: NT4 to Windows 2003 : which dns ?"
- Reply: Tony Scarola: "Re: NT4 to Windows 2003 : which dns ?"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 8 Nov 2004 01:06:47 +0800
Hi Tony,
That would depend on how you have your zones and replication set up.
If you have a local DNS Server at the branch office that is storing a copy
of the zone (generally a good idea) then the branch site points to the local
dns server. You could add root as a secondary DNS server for clients as
well, but you'd be better off using a secondary DNS server if at the branch
if you're concerned about redundancy. Remember, if the clients in the
branch office need to find servers in the home office, the branch office dns
should be pointing them to the right place.
Chances are you've got your branch and home office on different subnets as
well, so make sure to set up your reverse lookup zones properly also.
-- HTH, =d= Dana Brash MCSE, MCDBA, MCSA dbrash@NOSPAM.gmail.com "Tony Scarola" <tony[rEm0vEmE]@scarolas.com> wrote in message news:O%23oNavNxEHA.3808@TK2MSFTNGP15.phx.gbl... > Dana, > > You mention that the clients should point to the root DC for DNS > resolution. Would this also be the case for clients at a branch site (over > a WAN link) if they have their own DC w/ AD-DNS? Or would they point to > their local DC first, and have root as secondary? I've always been a bit > confused by this. > > Thank you in advance, > Tony > > "Dana Brash" <dbrash@gmail.com> wrote in message > news:ePm%23npMxEHA.4004@tk2msftngp13.phx.gbl... >> Hi Vincent, >> >> You can configure DNS as part of the installation of AD on your new >> server, but I always prefer to get DNS working properly before hand. It >> seems to save time cleaning up event log error messages after installing >> AD.... >> >> Make sure you plan you namespace properly: >> Active Directory, ADSI and Directory Services Technical Articles >> >> Microsoft Windows 2000 Namespace Design ~~ A more thorough Discussion >> >> http://msdn.microsoft.com/archive/default.asp?url=/archive/en-us/dnaractdir/html/Namespace_Design.asp >> >> >> >> Clients should point to the new server for DNS resolution as you >> mentioned. Their primary DNS should be the Root DC, and their secondary >> DNS should be the secondary DC. Both DC's should be running DNS and have >> AD integrated forward and reverse lookup zones. >> >> >> >> The Root server should point to itself for DNS resolution ONLY. Do not >> configure a secondary DNS lookup for the root DC. The Secondary DC(s) >> should point to the root DC for DNS as well. >> >> >> >> The DNS server will have two options for resolving lookups. The first >> option, which is how it works by default, is by using the Root Hint >> records that configure as part of the DNS Service installation. The >> preferred method of configuration is to use your ISP as a DNS forwarder >> on your DNS Server. In DNS management console (dnsmgmt.msc) right click >> and select properties for the root DC's server name. On the Forwarders >> tab click 'Enable Forwarders' and set the IP address that you got from >> your ISP, or your favorite public DNS server. >> -- >> HTH, >> =d= >> >> >> >> Dana Brash >> MCSE, MCDBA, MCSA >> >> dbrash@NOSPAM.gmail.com >> >> "Vincent Schmid" <nospam@nospam.com> wrote in message >> news:2v6j51F2h13emU1@uni-berlin.de... >>> Hello, >>> >>> We are planning to migrate our NT4 server to Windows 2003. We will >>> configure a simple domain which will have one server and about 50 XP >>> clients. The server will have dns installed at the same time than active >>> directory. >>> >>> I'm not quite sure how the dns should be configured in the network >>> TCP/IP settings of the machines : >>> >>> - Clients : Now they point to an IP which was given by our internet >>> provider. I suppose that we will have to redirect them to the IP of the >>> new server ? >>> >>> - What about the server ? Should the TCP/IP settings of the connexion >>> point to the internet provider dns or to the server itself ? >>> >>> - Where does the Windows 2003 dns get his information from ? do we have >>> to indicate some known dns server in its configuration ? >>> >>> >>> Thanks in advance for any help, >>> Sincerely, >>> Vincent Schmid >> >> > >
- Next message: JD: "Re: Stupid Americans! -- Stupid... Stupid... STUPID!!! _____________---_ bugbeqy"
- Previous message: Tony Scarola: "Re: DNS Domain Name Extension Suggestions?"
- In reply to: Tony Scarola: "Re: NT4 to Windows 2003 : which dns ?"
- Next in thread: Tony Scarola: "Re: NT4 to Windows 2003 : which dns ?"
- Reply: Tony Scarola: "Re: NT4 to Windows 2003 : which dns ?"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
