asked on

DNS Problems after upgrading a NT4 DC to Windows 2000

I am experiencing problems with DNS after upgrading a NT4 domain controller to Windows 2000 server. The server had no prior installation of DNS. Several re-installations of DNS have been performed. DNS fails testing when running NETDIAG. I have also executed NETDIAG /FIX the relative portions of the log file follow:

DNS test . . . . . . . . . . . . . : Failed
[WARNING] Cannot find a primary authoritative DNS server for the name
'hv-cba.rowbci.'. [RCODE_SERVER_FAILURE]
The name 'hv-cba.rowbci.' may not be registered in DNS.
[FATAL] Failed to fix: DC DNS entry rowbci. re-registeration on DNS server '206.55.59.1' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
[FATAL] Failed to fix: DC DNS entry _ldap._tcp.rowbci. re-registeration on DNS server '206.55.59.1' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
[FATAL] Failed to fix: DC DNS entry _ldap._tcp.Default-First-Site-Name._sites.rowbci. re-registeration on DNS server '206.55.59.1' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
[FATAL] Failed to fix: DC DNS entry _ldap._tcp.pdc._msdcs.rowbci. re-registeration on DNS server '206.55.59.1' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
[FATAL] Failed to fix: DC DNS entry _ldap._tcp.gc._msdcs.rowbci. re-registeration on DNS server '206.55.59.1' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
[FATAL] Failed to fix: DC DNS entry _ldap._tcp.Default-First-Site-Name._sites.gc._msdcs.rowbci. re-registeration on DNS server '206.55.59.1' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
[FATAL] Failed to fix: DC DNS entry _ldap._tcp.97d35c4f-a7a6-4969-b329-279b8b52580e.domains._msdcs.rowbci. re-registeration on DNS server '206.55.59.1' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
[FATAL] Failed to fix: DC DNS entry gc._msdcs.rowbci. re-registeration on DNS server '206.55.59.1' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
[FATAL] Failed to fix: DC DNS entry 703a02ec-6182-4d85-86c2-7c4b3520d1aa._msdcs.rowbci. re-registeration on DNS server '206.55.59.1' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
[FATAL] Failed to fix: DC DNS entry _kerberos._tcp.dc._msdcs.rowbci. re-registeration on DNS server '206.55.59.1' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
[FATAL] Failed to fix: DC DNS entry _kerberos._tcp.Default-First-Site-Name._sites.dc._msdcs.rowbci. re-registeration on DNS server '206.55.59.1' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
[FATAL] Failed to fix: DC DNS entry _ldap._tcp.dc._msdcs.rowbci. re-registeration on DNS server '206.55.59.1' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
[FATAL] Failed to fix: DC DNS entry _ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.rowbci. re-registeration on DNS server '206.55.59.1' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
[FATAL] Failed to fix: DC DNS entry _kerberos._tcp.rowbci. re-registeration on DNS server '206.55.59.1' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
[FATAL] Failed to fix: DC DNS entry _kerberos._tcp.Default-First-Site-Name._sites.rowbci. re-registeration on DNS server '206.55.59.1' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
[FATAL] Failed to fix: DC DNS entry _gc._tcp.rowbci. re-registeration on DNS server '206.55.59.1' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
[FATAL] Failed to fix: DC DNS entry _gc._tcp.Default-First-Site-Name._sites.rowbci. re-registeration on DNS server '206.55.59.1' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
[FATAL] Failed to fix: DC DNS entry _kerberos._udp.rowbci. re-registeration on DNS server '206.55.59.1' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
[FATAL] Failed to fix: DC DNS entry _kpasswd._tcp.rowbci. re-registeration on DNS server '206.55.59.1' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
[FATAL] Failed to fix: DC DNS entry _kpasswd._udp.rowbci. re-registeration on DNS server '206.55.59.1' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
[FATAL] Fix Failed: netdiag failed to re-register missing DNS entries for this DC on DNS server '206.55.59.1'.
[FATAL] No DNS servers have the DNS records for this DC registered.

Thanks!

Debsyl99

Hi

Have you put the ip address of your server as the preferred dns server in tcp/ip settings on the servers nic? If you have your isp's server address, swap it for your server ip,

Deb :))

Debsyl99

Setting Up the Domain Name System for Active Directory
http://support.microsoft.com/?kbid=237675
Frequently Asked Questions About Windows 2000 DNS and Windows Server 2003 DNS
http://support.microsoft.com/?kbid=291382

bng2004

ASKER

Yes the ip address of the server is set for DNS

ASKER CERTIFIED SOLUTION

Debsyl99

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Chris Dent

This address:

'206.55.59.1'

Is the IP Address it's trying to dynamically register records in and query records from.

Is that one definately your Internal (private) DNS Server address? Just curious because that's not a reserved private network range.

bng2004

ASKER

The upgrade was performed to accomodate the installation of a new application architecture. I have a new server specified for order, but I was looking to stabilize the network prior to the integration of the new box. I installed WINS last week and things have stabilized a bit, but I wanted to get DNS working as well.

bng2004

ASKER

206.55.59.1 is an internal private address on the LAN

Thanks

Debsyl99

Did you apply the registry fixes contained in the link I posted - just to confirm - your server is called hv-cba.rowbci and your domain is rowbci?
Ordinarily Domains should be configured with the names in the form mydomain.com or mydomain.local etc. If this is the case you'll need to apply the fix to get registration of records working,

Chris Dent

Ahh good :)

Can you confirm that the zone files are Active Directory Integrated and set to Allow Dynamic Updates (Allow Secure Updates Only)?

The single label zone (as Deb suggested) might well be the problem and there's a registry change that can be made to bypass it (again detailed in the articles posted by Deb).

But instead of adding a new DC to the existing domain you might consider using ADMT to move everything off the old domain and onto a new one with a full domain name. Of course, that option depends very much on the impact it will have on your current infrastructure.

bng2004

ASKER

Thanks for all of your help guys, I have not had a chance to move forward with the regedit. I will keep you posted. Yeah all of my other networks I service have the .local added to the FQDN, I don't remeber having an option to specify the .local during the upgrade process from NT to 2000 on the server in question, I prefer not to do OS upgrades but rather clean installs, but in this case I had no choice. Thanks again.