I get the following message when running netdiag:

DNS test . . . . . . . . . . . . . : Passed

PASS - All the DNS entries for DC are registered on DNS server
'xxx.xxx.xx.xxx’

51' and other DCs also have some of the names registered.

[WARNING] The DNS entries for this DC are not registered correctly on
DNS server 'zzz.zzz.zz.zzz'. Please wait for 30 minutes for DNS server
replication



where xxx.xxx.xx.xxx is OUR internal DNS server, and ZZZ.ZZZ.ZZ.ZZZ is the
IP address of our ISP’s DNS sever.



Does this mean the problem is on our end or something the ISP has to do?

"Gary M" <garym_jacksonfurniture(removespam)@hotmail.com> wrote in message
news:eTz$D$(E-Mail Removed)...
>I get the following message when running netdiag:
>
> DNS test . . . . . . . . . . . . . : Passed
>
> PASS - All the DNS entries for DC are registered on DNS server
> 'xxx.xxx.xx.xxx'
>
> 51' and other DCs also have some of the names registered.
>
> [WARNING] The DNS entries for this DC are not registered correctly on
> DNS server 'zzz.zzz.zz.zzz'. Please wait for 30 minutes for DNS server
> replication

For some reason your DNS servers are not fully replicated. Either you have
isolated (non-replicating) secondary DNS servers, "lost DNS servers" no
longer
online, OR you have AD DNS which isn't replicating.

What sort of DNS are you using?

> where xxx.xxx.xx.xxx is OUR internal DNS server, and ZZZ.ZZZ.ZZ.ZZZ is the
> IP address of our ISP's DNS sever.
>
>
>
> Does this mean the problem is on our end or something the ISP has to do?

You end.

--
Herb Martin, MCSE, MVP
http://www.LearnQuick.Com
(phone on web site)

"Herb Martin" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
>
> "Gary M" <garym_jacksonfurniture(removespam)@hotmail.com> wrote in message
> news:eTz$D$(E-Mail Removed)...
>>I get the following message when running netdiag:
>>
>> DNS test . . . . . . . . . . . . . : Passed
>>
>> PASS - All the DNS entries for DC are registered on DNS server
>> 'xxx.xxx.xx.xxx'
>>
>> 51' and other DCs also have some of the names registered.
>>
>> [WARNING] The DNS entries for this DC are not registered correctly on
>> DNS server 'zzz.zzz.zz.zzz'. Please wait for 30 minutes for DNS server
>> replication
>
> For some reason your DNS servers are not fully replicated. Either you
> have
> isolated (non-replicating) secondary DNS servers, "lost DNS servers" no
> longer
> online, OR you have AD DNS which isn't replicating.
>
> What sort of DNS are you using?
>
>> where xxx.xxx.xx.xxx is OUR internal DNS server, and ZZZ.ZZZ.ZZ.ZZZ is
>> the IP address of our ISP's DNS sever.
>>
>>
>>
>> Does this mean the problem is on our end or something the ISP has to do?
>
> You end.
>
> --
> Herb Martin, MCSE, MVP
> http://www.LearnQuick.Com
> (phone on web site)
>

shoot, I was afraid you were going to say that.

I have two windows 2000 servers that do DNS (one each at two different
plants, two different subnets), sounds like they are not replicating, then?

gary

"Gary M" <garym_jacksonfurniture(removespam)@hotmail.com> wrote in message
news:(E-Mail Removed)...
>
> I have two windows 2000 servers that do DNS (one each at two different
> plants, two different subnets), sounds like they are not replicating,
> then?

Yes, are they both AD Integrated (instread of Primary-Secondary)?

AD alrways requires DNS to work to replicate, AND IF AD is in DNS
then DNS requires AD which cause a bigger problem IF it goes bad.

General way to fix this is as follows:

Pick one DNS server (whichever or one with "most correct" stuff.)

Set BOTH DNS Servers NIC->IP Properties->DNS server to
ONLY this "best" DNS server

Do the "NetDiag /Fix" or restart the "netlogon" service to
re-register
EACH DC

Fix any other problems such as firewall filtering that prevent DNS
from replicating.

Wait for full replication

Set the DNS servers back to
1) Self first as PREFERRED
2) Partner(s) as alternate(s)

Concept: Get them both using AND registered in ONE DNS server. Get them
replicated. Then set it normally.

--
Herb Martin, MCSE, MVP
http://www.LearnQuick.Com
(phone on web site)

Gary M wrote:
> I get the following message when running netdiag:
>
> DNS test . . . . . . . . . . . . . : Passed
>
> PASS - All the DNS entries for DC are registered on DNS server
> 'xxx.xxx.xx.xxx
>
> 51' and other DCs also have some of the names registered.
>
> [WARNING] The DNS entries for this DC are not registered
> correctly on DNS server 'zzz.zzz.zz.zzz'. Please wait for 30 minutes
> for DNS server replication
>
>
>
> where xxx.xxx.xx.xxx is OUR internal DNS server, and ZZZ.ZZZ.ZZ.ZZZ
> is the IP address of our ISPs DNS sever.
>
>
>
> Does this mean the problem is on our end or something the ISP has to
> do?

Remove the ISP DNS from TCP/IP properties, your ISP's DNS cannot possibly
resolve your internal network and should ONLY be used as a forwarder.

--
Best regards,
Kevin D. Goodknecht Sr. [MVP]
Hope This Helps
Send IM: http://www.icq.com/people/webmsg.php?to=296095728
===================================
When responding to posts, please "Reply to Group"
via your newsreader so that others may learn and
benefit from your issue, to respond directly to
me remove the nospam. from my email address.
===================================
http://www.lonestaramerica.com/
http://support.wftx.us/
http://message.wftx.us/
===================================
Use Outlook Express?... Get OE_Quotefix:
It will strip signature out and more
http://home.in.tum.de/~jain/software/oe-quotefix/
===================================
Keep a back up of your OE settings and folders
with OEBackup:
http://www.oehelp.com/OEBackup/Default.aspx
===================================

"Kevin D. Goodknecht Sr. [MVP]" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Gary M wrote:
>> I get the following message when running netdiag:
>>
>> DNS test . . . . . . . . . . . . . : Passed
>>
>> PASS - All the DNS entries for DC are registered on DNS server
>> 'xxx.xxx.xx.xxx
>>
>> 51' and other DCs also have some of the names registered.
>>
>> [WARNING] The DNS entries for this DC are not registered
>> correctly on DNS server 'zzz.zzz.zz.zzz'. Please wait for 30 minutes
>> for DNS server replication
>>
>>
>>
>> where xxx.xxx.xx.xxx is OUR internal DNS server, and ZZZ.ZZZ.ZZ.ZZZ
>> is the IP address of our ISPs DNS sever.
>>
>>
>>
>> Does this mean the problem is on our end or something the ISP has to
>> do?
>
> Remove the ISP DNS from TCP/IP properties, your ISP's DNS cannot possibly
> resolve your internal network and should ONLY be used as a forwarder.
>
> --
> Best regards,
> Kevin D. Goodknecht Sr. [MVP]
> Hope This Helps
> Send IM: http://www.icq.com/people/webmsg.php?to=296095728
> ===================================
> When responding to posts, please "Reply to Group"
> via your newsreader so that others may learn and
> benefit from your issue, to respond directly to
> me remove the nospam. from my email address.
> ===================================
> http://www.lonestaramerica.com/
> http://support.wftx.us/
> http://message.wftx.us/
> ===================================
> Use Outlook Express?... Get OE_Quotefix:
> It will strip signature out and more
> http://home.in.tum.de/~jain/software/oe-quotefix/
> ===================================
> Keep a back up of your OE settings and folders
> with OEBackup:
> http://www.oehelp.com/OEBackup/Default.aspx
> ===================================
>
>

oh, okay. I gotcha.

so I have the ISP DNS listed on our firewall anyways, so I dont need it on
this windows server.
this is also our exchange server (was our first server), so I will just
remove the ISP DNS and put in the other windows 2000 server DNS, and let our
firewall\vpn appliance take care of the forwarding.

gary

"Gary M" <garym_jacksonfurniture(removespam)@hotmail.com> wrote in message
news:(E-Mail Removed)...
>
> "Kevin D. Goodknecht Sr. [MVP]" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...

>> Remove the ISP DNS from TCP/IP properties, your ISP's DNS cannot possibly
>> resolve your internal network and should ONLY be used as a forwarder.

> oh, okay. I gotcha.
>
> so I have the ISP DNS listed on our firewall anyways, so I dont need it on
> this windows server.

Not only do you not "need" it on the server, you MUST NOT put it there on
any internal machine.

Internal DNS clients must use strictly the internal DNS server set which can
resolve all internan (and external) names needed by the client.

> this is also our exchange server (was our first server), so I will just
> remove the ISP DNS and put in the other windows 2000 server DNS, and let
> our firewall\vpn appliance take care of the forwarding.

Right. Let the internal DNS servers forward to the ISP or your own
Gateway/Firewal
DNS server for resolving Internet names.

--
Herb Martin, MCSE, MVP
http://www.LearnQuick.Com
(phone on web site)