netdiag error

[Guest]

trying to get prepped for exchange 2003. Ran netdiag on my 2000 DC and received the following error.

DNS test . . . . . . . . . . . . . : Faile
[WARNING] Cannot find a primary authoritative DNS server for the nam
'S0.shrs.'. [RCODE_SERVER_FAILURE
The name 'S0.shrs.' may not be registered in DNS
[WARNING] The DNS entries for this DC are not registered correctly on DNS server '192.168.7.14'. Please wait for 30 minutes for DNS server replication
[FATAL] No DNS servers have the DNS records for this DC registered

This server (S0 on domain shrs) is my domain controller and my DNS server. I have gone into the DNS and removed the A record and added it back again manually. I also did the same with the pointer in the reverse lookup zone. Why am I getting this error? Is it because I only have a single name domain

I wnat to make sure that this is cleaned up before I continue with my exchange upgrade

Kevi

 

[Kevin D. Goodknecht [MVP]]

In

trying to get prepped for exchange 2003. Ran netdiag on my 2000 DC
and received the following error.

DNS test . . . . . . . . . . . . . : Failed
[WARNING] Cannot find a primary authoritative DNS server
for the name
'S0.shrs.'. [RCODE_SERVER_FAILURE]
The name 'S0.shrs.' may not be registered in DNS.
[WARNING] The DNS entries for this DC are not registered
correctly on DNS server '192.168.7.14'. Please wait for 30 minutes
for DNS server replication.
[FATAL] No DNS servers have the DNS records for this DC
registered.

This server (S0 on domain shrs) is my domain controller and my DNS
server. I have gone into the DNS and removed the A record and added
it back again manually. I also did the same with the pointer in the
reverse lookup zone. Why am I getting this error? Is it because I
only have a single name domain?

I wnat to make sure that this is cleaned up before I continue with my
exchange upgrade.

Kevin

It appears you have a single-label domain name, which is bad. Win2kSP4 WinXP
and Win2k3 cannot register by default in a single-label domain name, you'll
have to make registry entries to make that possible. Even with the registry
entries the single-label domain will not resolve in DNS, which is required
for Group policies to be applied. If you aren't too far along you'd be best
to start over with a new domain using a DNS compatible name like shrs.local
which will make everything happy.
300684 - Information About Configuring Windows 2000 for Domains with
Single-Label DNS Names
http://support.microsoft.com/default.aspx?scid=kb;en-us;300684

 

[Larry Stotler]

Hello,

After applying the registry keys listed in article 300684 you should be
able to both register and do DNS queries against this zone. The 2 required
values are AllowSingleLabelDnsDomain & UpdateTopLevelDomainZones. The
mistake that is usually made is that these are put in the wrong location.

Create "AllowSingleLabelDnsDomain"(REG_DWORD) registry value and set to
0x1, under the following registry key on each domain member:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Netlogon\Parameters

This allows the Clients to use DNS to do lookups in a single label domain.

Create "UpdateTopLevelDomainZones" (REG_DWORD value) registry value and set
to 0x1 under the following registry key on clients that attempt to
dynamically update the single-label DNS zone:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\DnsCache\Parameters

This allows clients and servers to register in a single label domain.

Please notice that these are under DIFFERENT keys. This should allow you
to function with your current name. However, as Kevin reccomended if you
are early along in the process changing to a name with a dot in it would
save you some work.


Larry Stotler, MCSE
Microsoft Product Support

NOTE: Please reply to the newsgroup and not directly to me. This allows
others to add to and benefit from these threads and also helps to ensure a
more timely response. Thank you!

This posting is provided "AS IS" without warranty either expressed or
implied, including, but not limited to, the implied warranties of
merchantability or fitness for a particular purpose

 

[Guest]

I have a single domain with 2 DC's I have about 200 users and 160 pcs on it. I also have exchange 5.5 attached. How difficult would it be to change my domain name at this point How would I move the active directory, dns etc. Will the registry setting allow me to install exchange 2003. This is where my problems started.

 

[Larry Stotler]

Hello,

There is not a mechanism to change the Active Directory domain name in a
Windows 2000 domain. In order to change domain names it you must dcpromo
down both DC's and then create a new domain. So it is basically starting
over from scratch. If you already have 200 users you may not want to start
over.

Windows Server 2003 does offer the option to rename the domain. In this
case all DC's must be 2003 and it is not supported in an environment with
Exchange 2000. This process is talked about at the following link.

http://www.microsoft.com/windowsserver2003/downloads/domainrename.mspx


Larry Stotler, MCSE
Microsoft Product Support

NOTE: Please reply to the newsgroup and not directly to me. This allows
others to add to and benefit from these threads and also helps to ensure a
more timely response. Thank you!

This posting is provided "AS IS" without warranty either expressed or
implied, including, but not limited to, the implied warranties of
merchantability or fitness for a particular purpose

 

[Kevin D. Goodknecht [MVP]]

In

I have a single domain with 2 DC's I have about 200 users and 160
pcs on it. I also have exchange 5.5 attached. How difficult would it
be to change my domain name at this point How would I move the active
directory, dns etc.

You can demote one of your DCs and promote it with a DNS compatible name.
Then use ADMT to Migrate all user accounts and computer accounts, every
thing will migrate including the User SIDs, profiles and so on. I will take
a while, leave all machines turned on with no logged on users. After the
migration the clients will need to be rebooted, but when the users come to
work and log on they'll never know the difference.

Will the registry setting allow me to install
exchange 2003. This is where my problems started.

Yes it should.

 

[Kevin D. Goodknecht [MVP]]

In

Hello,

There is not a mechanism to change the Active Directory domain name
in a Windows 2000 domain. In order to change domain names it you
must dcpromo down both DC's and then create a new domain. So it is
basically starting over from scratch.

He can use ADMT and demote/promote one DC.

 

[Kevin]

-----Original Message-----
In

He can use ADMT and demote/promote one DC.







.

After looking through this I would like to keep the name
as is and use the registry settings. I changed the
registry on both 2000 DCs and the errors went away. I did
this on the 2003 server and the error was not as large but
still exists as follows:

[Warning] Cannot find a priamry authoritative server
for the name 'email.shrs.' [Error_Timeout]
The name 'email.shrs.' may not be registered in dns.

I checked my registry settings on the 2003 server. I know
that the location for the UpdateTopLevelDomainZones is not
in the same place as it is on the 2000. I also found an
article on this that says you can use group policies.
(article 826743).

I also ran a simple and recursive query on my DC. The
simple query was fine but the reverse failed.

All of this is due to my doamin prep failing for exchange
2003 and if I run it on the DC it still fails the same
way.

 

[Larry Stotler]

Hello,

This article has worked for me each time I have used it on a Windows server
2003 system. Please confirm again that they are in the correct location
and Spelled correctly, including capitalization. Also make sure you reboot
to ensure the changes are taking affect.

AllowSingleLabelDnsDomain

(REG_DWORD)
registry value to 0x1 under the following registry key on each domain
member:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Netlogon\Parameters

UpdateTopLevelDomainZones

(REG_DWORD)
registry value to 0x1 under the following registry key on each domain
member:

HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\DNSClient



Larry Stotler, MCSE
Microsoft Product Support

NOTE: Please reply to the newsgroup and not directly to me. This allows
others to add to and benefit from these threads and also helps to ensure a
more timely response. Thank you!

This posting is provided "AS IS" without warranty either expressed or
implied, including, but not limited to, the implied warranties of
merchantability or fitness for a particular purpose