Greetings All,

I'm in need of a bit of trying to resolve this DNS issue.

I have inherited a small AD network with 2 domain controllers. 1 Win2K
Server and 1 Win2K2 Server.

I ran netdiag on the Win2K box and received the following DNS failure
notice.

DNS test . . . . . . . . . . . . . : Failed
[WARNING] Cannot find a primary authoritative DNS server for the name
'odyssey-fs1.Odyssey.'.
[RCODE_SERVER_FAILURE] The name 'odyssey-fs1.Odyssey.' may not be
registered in DNS.
[FATAL] File \config\netlogon.dns contains invalid DNS entries.
[FATAL] File \config\netlogon.dns contains invalid DNS entries.
[FATAL] No DNS servers have the DNS records for this DC registered.

I have run netdiag /fix with no improvement.

I've also run netdiag and dcdiag on the Win2K3 box and received no errors.

I would like to know how I can resolve this issue.

Thanks for any and advice.

Read inline please.

In news:4166074E-F933-4FC9-89D6-6BDB6CFBE058@microsoft.com,
J.Harvey <JHarvey@discussions.microsoft.com> typed:
> Greetings All,
>
> I'm in need of a bit of trying to resolve this DNS issue.
>
> I have inherited a small AD network with 2 domain controllers. 1
> Win2K Server and 1 Win2K2 Server.
>
> I ran netdiag on the Win2K box and received the following DNS failure
> notice.
>
> DNS test . . . . . . . . . . . . . : Failed
> [WARNING] Cannot find a primary authoritative DNS server for
> the name 'odyssey-fs1.Odyssey.'.
> [RCODE_SERVER_FAILURE] The name 'odyssey-fs1.Odyssey.' may
> not be registered in DNS.
> [FATAL] File \config\netlogon.dns contains invalid DNS entries.
> [FATAL] File \config\netlogon.dns contains invalid DNS entries.
> [FATAL] No DNS servers have the DNS records for this DC
> registered.
>
> I have run netdiag /fix with no improvement.
>
> I've also run netdiag and dcdiag on the Win2K3 box and received no
> errors.
>
> I would like to know how I can resolve this issue.
>
> Thanks for any and advice.

It appears that you have a single-label DNS name for your domain, "odyssey"
this is a big problem because single-label DNS names do fit the normal DNS
hierarchy, and usually only contain NS records, such as in a TLD. You will
need to modify the registry of every member (including DCs) of this domain
that is running Win2kSP4 or later.

300684 - Information About Configuring Windows 2000 for Domains with
Single-Label DNS Names
http://support.microsoft.com/default...300684&sd=RMVP



--
Best regards,
Kevin D. Goodknecht Sr. [MVP]
Hope This s

===================================
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.oe.com/OEBackup/Default.aspx
===================================

Greetings Kevin, Thanks for the link. I gave it a read and wanted to give
you a bit more information.

There are 2 other DNS errors I've run across.

On the Win2K DC:
1) Event Type: Warning
Event Source: DNS
Event Category: None
Event ID: 409
Date: 6/20/2007
Time: 11:32:55 AM
User: N/A
Computer: ODYSSEY-FS1
Description:
The DNS server list of restricted interfaces contains IP addresses that are
not configured for use at the server computer.
Use the DNS manager server properties, interfaces dialog, to verify and
reset the IP addresses the DNS server should listen on. For more
information, see "To restrict a DNS server to listen only on selected
addresses" in the online .

On the Win2K3 DC:
2) Event Type: Error
Event Source: DNS
Event Category: None
Event ID: 6702
Date: 6/21/2007
Time: 5:50:51 PM
User: N/A
Computer: ILIAD
Description:
DNS server has updated its own host (A) records. In order to ensure that
its DS-integrated peer DNS servers are able to replicate with this server, an
attempt was made to update them with the new records through dynamic update.
An error was encountered during this update, the record data is the error
code.

If this DNS server does not have any DS-integrated peers, then this error
should be ignored.

If this DNS server's Active Directory replication partners do not have the
correct IP address(es) for this server, they will be unable to replicate with
it.

To ensure proper replication:
1) Find this server's Active Directory replication partners that run the DNS
server.
2) Open DnsManager and connect in turn to each of the replication partners.
3) On each server, check the host (A record) registration for THIS server.
4) Delete any A records that do NOT correspond to IP addresses of this
server.
5) If there are no A records for this server, add at least one A record
corresponding to an address on this server, that the replication partner can
contact. (In other words, if there multiple IP addresses for this DNS
server, add at least one that is on the same network as the Active Directory
DNS server you are updating.)
6) Note, that is not necessary to update EVERY replication partner. It is
only necessary that the records are fixed up on enough replication partners
so that every server that replicates with this server will receive (through
replication) the new data.

Thought I'd include a copy of the Win2K box's netlogon.dns

Odyssey. 600 IN A 192.168.1.2
_ldap._tcp.Odyssey. 600 IN SRV 0 100 389 odyssey-fs1.Odyssey.
_ldap._tcp.Default-First-Site-Name._sites.Odyssey. 600 IN SRV 0 100 389
odyssey-fs1.Odyssey.
_ldap._tcp.pdc._msdcs.Odyssey. 600 IN SRV 0 100 389 odyssey-fs1.Odyssey.
_ldap._tcp.gc._msdcs.Odyssey. 600 IN SRV 0 100 3268 odyssey-fs1.Odyssey.
_ldap._tcp.Default-First-Site-Name._sites.gc._msdcs.Odyssey. 600 IN SRV 0
100 3268 odyssey-fs1.Odyssey.
_ldap._tcp.c226fa39-c76c-4d66-b673-478909d622dc.domains._msdcs.Odyssey. 600
IN SRV 0 100 389 odyssey-fs1.Odyssey.
gc._msdcs.Odyssey. 600 IN A 192.168.1.2
798ec3ce-f31e-4c76-8671-a94094f5cc15._msdcs.Odyssey. 600 IN CNAME
odyssey-fs1.Odyssey.
_kerberos._tcp.dc._msdcs.Odyssey. 600 IN SRV 0 100 88 odyssey-fs1.Odyssey.
_kerberos._tcp.Default-First-Site-Name._sites.dc._msdcs.Odyssey. 600 IN SRV
0 100 88 odyssey-fs1.Odyssey.
_ldap._tcp.dc._msdcs.Odyssey. 600 IN SRV 0 100 389 odyssey-fs1.Odyssey.
_ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.Odyssey. 600 IN SRV 0
100 389 odyssey-fs1.Odyssey.
_kerberos._tcp.Odyssey. 600 IN SRV 0 100 88 odyssey-fs1.Odyssey.
_kerberos._tcp.Default-First-Site-Name._sites.Odyssey. 600 IN SRV 0 100 88
odyssey-fs1.Odyssey.
_gc._tcp.Odyssey. 600 IN SRV 0 100 3268 odyssey-fs1.Odyssey.
_gc._tcp.Default-First-Site-Name._sites.Odyssey. 600 IN SRV 0 100 3268
odyssey-fs1.Odyssey.
_kerberos._udp.Odyssey. 600 IN SRV 0 100 88 odyssey-fs1.Odyssey.
_kpasswd._tcp.Odyssey. 600 IN SRV 0 100 464 odyssey-fs1.Odyssey.
_kpasswd._udp.Odyssey. 600 IN SRV 0 100 464 odyssey-fs1.Odyssey.
; _ldap._tcp.Odyssey. 600 IN SRV 0 100 389 ILIAD.Odyssey.
; _ldap._tcp.Default-First-Site-Name._sites.Odyssey. 600 IN SRV 0 100 389
ILIAD.Odyssey.
; _ldap._tcp.pdc._msdcs.Odyssey. 600 IN SRV 0 100 389 ILIAD.Odyssey.
; _ldap._tcp.gc._msdcs.Odyssey. 600 IN SRV 0 100 3268 ILIAD.Odyssey.
; _ldap._tcp.Default-First-Site-Name._sites.gc._msdcs.Odyssey. 600 IN SRV 0
100 3268 ILIAD.Odyssey.
; _ldap._tcp.c226fa39-c76c-4d66-b673-478909d622dc.domains._msdcs.Odyssey.
600 IN SRV 0 100 389 ILIAD.Odyssey.
; ed0474cf-d3bb-48a0-947b-95df7c68916f._msdcs.Odyssey. 600 IN CNAME
ILIAD.Odyssey.
; _kerberos._tcp.dc._msdcs.Odyssey. 600 IN SRV 0 100 88 ILIAD.Odyssey.

>>>>> Info Ends Here <<<<<<<<<<<<<

Does the additional info I've included call for any other type fix than the
registry edit to deal with the single-label DNS issue you've identified?

Thanks again for you interest and .
_____________________________________________

"Kevin D. Goodknecht Sr. [MVP]" wrote:

> Read inline please.
>
> In news:4166074E-F933-4FC9-89D6-6BDB6CFBE058@microsoft.com,
> J.Harvey <JHarvey@discussions.microsoft.com> typed:
> > Greetings All,
> >
> > I'm in need of a bit of trying to resolve this DNS issue.
> >
> > I have inherited a small AD network with 2 domain controllers. 1
> > Win2K Server and 1 Win2K2 Server.
> >
> > I ran netdiag on the Win2K box and received the following DNS failure
> > notice.
> >
> > DNS test . . . . . . . . . . . . . : Failed
> > [WARNING] Cannot find a primary authoritative DNS server for
> > the name 'odyssey-fs1.Odyssey.'.
> > [RCODE_SERVER_FAILURE] The name 'odyssey-fs1.Odyssey.' may
> > not be registered in DNS.
> > [FATAL] File \config\netlogon.dns contains invalid DNS entries.
> > [FATAL] File \config\netlogon.dns contains invalid DNS entries.
> > [FATAL] No DNS servers have the DNS records for this DC
> > registered.
> >
> > I have run netdiag /fix with no improvement.
> >
> > I've also run netdiag and dcdiag on the Win2K3 box and received no
> > errors.
>
>
> It appears that you have a single-label DNS name for your domain, "odyssey"
> this is a big problem because single-label DNS names do fit the normal DNS
> hierarchy, and usually only contain NS records, such as in a TLD. You will
> need to modify the registry of every member (including DCs) of this domain
> that is running Win2kSP4 or later.
>
> 300684 - Information About Configuring Windows 2000 for Domains with
> Single-Label DNS Names
> http://support.microsoft.com/default...300684&sd=RMVP
>
>
>
> --
> Best regards,
> Kevin D. Goodknecht Sr. [MVP]
> Hope This s

Read inline please.

In news:140AA1DD-C00C-48D4-AFF5-77593FEA2C38@microsoft.com,
J.Harvey <JHarvey@discussions.microsoft.com> typed:
> Greetings Kevin, Thanks for the link. I gave it a read and wanted to
> give you a bit more information.
>
> There are 2 other DNS errors I've run across.
>
> On the Win2K DC:
> 1) Event Type: Warning
> Event Source: DNS
> Event Category: None
> Event ID: 409
> Date: 6/20/2007
> Time: 11:32:55 AM
> User: N/A
> Computer: ODYSSEY-FS1
> Description:
> The DNS server list of restricted interfaces contains IP addresses
> that are not configured for use at the server computer.
> Use the DNS manager server properties, interfaces dialog, to verify
> and reset the IP addresses the DNS server should listen on. For more
> information, see "To restrict a DNS server to listen only on selected
> addresses" in the online .
>

This warning is pretty much self explanatory, check the interfaces tab of
the DNS server properties in the DNS Management Console, remove any IP
addresses that are not physically on the NIC.


The rest of these errors are related to the single-label DNS name, you'll
have to make the registry fixes noted in the article.



> Thought I'd include a copy of the Win2K box's netlogon.dns
>
> Odyssey. 600 IN A 192.168.1.2
> _ldap._tcp.Odyssey. 600 IN SRV 0 100 389 odyssey-fs1.Odyssey.
> _ldap._tcp.Default-First-Site-Name._sites.Odyssey. 600 IN SRV 0 100
> 389 odyssey-fs1.Odyssey.
> _ldap._tcp.pdc._msdcs.Odyssey. 600 IN SRV 0 100 389
> odyssey-fs1.Odyssey. _ldap._tcp.gc._msdcs.Odyssey. 600 IN SRV 0 100
> 3268 odyssey-fs1.Odyssey.
> _ldap._tcp.Default-First-Site-Name._sites.gc._msdcs.Odyssey. 600 IN
> SRV 0 100 3268 odyssey-fs1.Odyssey.
> _ldap._tcp.c226fa39-c76c-4d66-b673-478909d622dc.domains._msdcs.Odyssey.
> 600 IN SRV 0 100 389 odyssey-fs1.Odyssey.
> gc._msdcs.Odyssey. 600 IN A 192.168.1.2
> 798ec3ce-f31e-4c76-8671-a94094f5cc15._msdcs.Odyssey. 600 IN CNAME
> odyssey-fs1.Odyssey.
> _kerberos._tcp.dc._msdcs.Odyssey. 600 IN SRV 0 100 88
> odyssey-fs1.Odyssey.
> _kerberos._tcp.Default-First-Site-Name._sites.dc._msdcs.Odyssey. 600
> IN SRV 0 100 88 odyssey-fs1.Odyssey. _ldap._tcp.dc._msdcs.Odyssey.
> 600 IN SRV 0 100 389 odyssey-fs1.Odyssey.
> _ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.Odyssey. 600 IN
> SRV 0 100 389 odyssey-fs1.Odyssey. _kerberos._tcp.Odyssey. 600 IN SRV
> 0 100 88 odyssey-fs1.Odyssey.
> _kerberos._tcp.Default-First-Site-Name._sites.Odyssey. 600 IN SRV 0
> 100 88 odyssey-fs1.Odyssey. _gc._tcp.Odyssey. 600 IN SRV 0 100 3268
> odyssey-fs1.Odyssey. _gc._tcp.Default-First-Site-Name._sites.Odyssey.
> 600 IN SRV 0 100 3268 odyssey-fs1.Odyssey.
> _kerberos._udp.Odyssey. 600 IN SRV 0 100 88 odyssey-fs1.Odyssey.
> _kpasswd._tcp.Odyssey. 600 IN SRV 0 100 464 odyssey-fs1.Odyssey.
> _kpasswd._udp.Odyssey. 600 IN SRV 0 100 464 odyssey-fs1.Odyssey.
> ; _ldap._tcp.Odyssey. 600 IN SRV 0 100 389 ILIAD.Odyssey.
> ; _ldap._tcp.Default-First-Site-Name._sites.Odyssey. 600 IN SRV 0 100
> 389 ILIAD.Odyssey.
> ; _ldap._tcp.pdc._msdcs.Odyssey. 600 IN SRV 0 100 389 ILIAD.Odyssey.
> ; _ldap._tcp.gc._msdcs.Odyssey. 600 IN SRV 0 100 3268 ILIAD.Odyssey.
> ; _ldap._tcp.Default-First-Site-Name._sites.gc._msdcs.Odyssey. 600 IN
> SRV 0 100 3268 ILIAD.Odyssey.
> ;
> _ldap._tcp.c226fa39-c76c-4d66-b673-478909d622dc.domains._msdcs.Odyssey.
> 600 IN SRV 0 100 389 ILIAD.Odyssey. ;
> ed0474cf-d3bb-48a0-947b-95df7c68916f._msdcs.Odyssey. 600 IN CNAME
> ILIAD.Odyssey. ; _kerberos._tcp.dc._msdcs.Odyssey. 600 IN SRV 0 100
> 88 ILIAD.Odyssey.
>
>>>>>> Info Ends Here <<<<<<<<<<<<<
>
> Does the additional info I've included call for any other type fix
> than the registry edit to deal with the single-label DNS issue you've
> identified?
>
> Thanks again for you interest and .
> _____________________________________________
>
> "Kevin D. Goodknecht Sr. [MVP]" wrote:
>
>> Read inline please.
>>
>> In news:4166074E-F933-4FC9-89D6-6BDB6CFBE058@microsoft.com,
>> J.Harvey <JHarvey@discussions.microsoft.com> typed:
>>> Greetings All,
>>>
>>> I'm in need of a bit of trying to resolve this DNS issue.
>>>
>>> I have inherited a small AD network with 2 domain controllers. 1
>>> Win2K Server and 1 Win2K2 Server.
>>>
>>> I ran netdiag on the Win2K box and received the following DNS
>>> failure notice.
>>>
>>> DNS test . . . . . . . . . . . . . : Failed
>>> [WARNING] Cannot find a primary authoritative DNS server for
>>> the name 'odyssey-fs1.Odyssey.'.
>>> [RCODE_SERVER_FAILURE] The name 'odyssey-fs1.Odyssey.' may
>>> not be registered in DNS.
>>> [FATAL] File \config\netlogon.dns contains invalid DNS
>>> entries. [FATAL] File \config\netlogon.dns contains invalid
>>> DNS entries. [FATAL] No DNS servers have the DNS records for
>>> this DC
>>> registered.
>>>
>>> I have run netdiag /fix with no improvement.
>>>
>>> I've also run netdiag and dcdiag on the Win2K3 box and received no
>>> errors.
>>
>>
>> It appears that you have a single-label DNS name for your domain,
>> "odyssey" this is a big problem because single-label DNS names do
>> fit the normal DNS hierarchy, and usually only contain NS records,
>> such as in a TLD. You will need to modify the registry of every
>> member (including DCs) of this domain that is running Win2kSP4 or
>> later.
>>
>> 300684 - Information About Configuring Windows 2000 for Domains with
>> Single-Label DNS Names
>> http://support.microsoft.com/default...300684&sd=RMVP
>>
>>
>>
>> --
>> Best regards,
>> Kevin D. Goodknecht Sr. [MVP]
>> Hope This s



--
Best regards,
Kevin D. Goodknecht Sr. [MVP]
Hope This s

===================================
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.oe.com/OEBackup/Default.aspx
===================================