"sunshine757" <> wrote in message news:406DAED5-9222-4EF2-B187-...
> We have a 2000 Server integrated AD Domain, with 2 DCs.
> serverJ is FSMO Master DC, primary DNS Server. single IP address.
> serverT is DC and DNS server. It has 1 x NIC with 2 x IP addresses.
> 192.168.0.4 is the email server, and .10 is everything else.
>
> We have several DNS errors (below) that I am very keen to clear.
>
> Here are all the Errors Only, from dcdiag and netdiag (no paramters), on
> both DCs.
>
> dcdiag serverT (clean)
>
> netdiag serverT
> netdiag DNS test . . . . . . . . . . . . . : Failed (see attached)
> [FATAL]: The DNS registration for 'serverT.domainname.local'
> is incorrect on all DNS servers.
> PASS - All the DNS entries for DC are registered on DNS server 'serverJ'
> ' and other DCs also have some of the names registered.
> PASS - All the DNS entries for DC are registered on DNS server 'serverT'
> ' and other DCs also have some of the names registered.
> DNS test . . . . . . . . . . . . . : Failed
>
> dcdiag serverJ
> Starting test: frssysvol
> There are errors after the SYSVOL has been shared.
> The SYSVOL can prevent the AD from starting.
> ......................... serverJ passed test frssysvol
>
> netdiag serverJ
> [WARNING] The DNS entries for this DC are not registered correctly on DNS se
> rver '123.456.78.90'.(ISPs DNS Server) Please wait for 30 minutes for DNS
> server replication.
>
> 1. How can we clear these ?
>
> 2. Are the 2 x IP addresses an issue here? Ive recently seen warnings about
> multi-homing, especially
> http://www.microsoft.com/communities...r=US&sloc=&p=1
>
> 3. Is our ISPs DNS address set correctly? (We have some user issues with
> network shared folder permissions, but web access is OK).
>
> Thank you so much.
>
Hello Sunshine,
You must remove that ISP's DNS server (123.456.78.90) from any internal machine that is part of AD (DCs, desktops, laptops, addresses given to VPN users, member servers, etc).
Configure a Forwarder on all your DNS servers to use 123.456.78.90. If not sure how, read the following article, please, that applies to your operating system version.
300202 - HOW TO: Configure DNS for Internet Access in Windows 2000
http://support.microsoft.com/?id=300202&FR=1
323380 - HOW TO: Configure DNS for Internet Access in Windows Server 2003 (How to configure a forwarder):
http://support.microsoft.com/d/id?=323380
Also, yes, multihoming is a very bad idea with DCs, as Meinolf indicated as well.
I don't know why you have multiple NICs on the DC, but if you need that for any reason in your infrastructure, use a member server (non-DC). As my post indicates in the link you've provided, it explains the DNS registration implications and why you are getting the errors. If the machine is being used for internet access, such as a NAT server, disable the external NIC and get an inexpensive NAT/DSL/Cable router to take care of this function.
If you want to keep the multiple NICs, I would highly suggest to follow the steps I've outlined in that link you've provided, on how to setup a multihomed DC, by making the necessary operating system and registry changes. But I would rather put it on a non-DC or get a router to take care of this function instead of making all these changes to my DC.
I hope that helps.
--
Ace
This posting is provided "AS-IS" with no warranties or guarantees and confers no rights.
Please reply back to the newsgroup/forum to benefit from collaboration among responding engineers, as well as to help others benefit from your resolution.
Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSA Messaging, MCT
Microsoft Certified Trainer
http://twitter.com/acefekay
For urgent issues, you may want to contact Microsoft PSS directly. Please check
http://support.microsoft.com for regional support phone numbers.
Similar Threads
Linear Mode
