DNS issues after upgrading from NT4.0 to Windows 2003. Please help.
From: Shohab (mshohab_at_yahoo.com)
Date: 08/24/04
- Next message: Steve Bruce, mct: "Re: dns questions"
- Previous message: Jack Ryan: "dns questions"
- Next in thread: Roger Abell: "Re: DNS issues after upgrading from NT4.0 to Windows 2003. Please help."
- Reply: Roger Abell: "Re: DNS issues after upgrading from NT4.0 to Windows 2003. Please help."
- Messages sorted by: [ date ] [ thread ]
Date: 24 Aug 2004 08:54:16 -0700
Hi.
We used to have two domains abc and 123 . Both domains had two way
trust between them. Now we upgraded from NT 4,0 to 2003. The design
structure we opted for is like this. we have a top level empty root
domain top.local and upgraded abc and 123 domains as abc.top.local and
123.top.local. As we were on Nt 4.0 so we were just using ISP DNS to
resolove. We have one DC in top domain which is the schema master and
naming operatons master and is a glocal catalog server too. We have
two DC's in each child domain and all 5 DC's are running DNS and are
global catalog server. Now after we upgraded we are having two major
DNS replication issues, one in each child domain. we are in 2000 mixed
mode right now for forest and domain functionality level (because of
5.5 exchange server which will be upgraded soon to 2003).On top root
domain, DNS has zones for _msdcs.top.local, top.local. 123.top.local
and abc.top.local and all zones are primary AD integrated and set to
replicate in forest.
First let me describe problem in abc.top.local domain. It has two
DC's. The first domain controller DNS has just one zone (AD
integrated) appearing in DNS which is for its own zone
(abc.top.local). It does'nt show zones for top.local or 123.top.local
or not even _msdcs.top.local. The zone for abc.top.local is set to
replicate all DC's in forest. I reduced time for AD replication to 15
minutes but still its not populating those missing zones. On other
hand, The second DC on this child domain has all zones
_msdcs.top.local, top.local. 123.top.local and abc.top.local) and all
are AD integrated and set to replicate forest wide. Now whenever I try
to restart netlogon service it gives error event ID 5781 twice.
ERROR1:
Dynamic registration or deletion of one or more DNS records associated
with DNS domain 'ForestDnsZones.top.local.' failed. These records are
used by other computers to locate this server as a domain controller
(if the specified domain is an Active Directory domain) or as an LDAP
server (if the specified domain is an application partition).
Possible causes of failure include:
- TCP/IP properties of the network connections of this computer
contain wrong IP address(es) of the preferred and alternate DNS
servers
- Specified preferred and alternate DNS servers are not running
- DNS server(s) primary for the records to be registered is not
running
- Preferred or alternate DNS servers are configured with wrong root
hints
- Parent DNS zone contains incorrect delegation to the child zone
authoritative for the DNS records that failed registration
USER ACTION
Fix possible misconfiguration(s) specified above and initiate
registration or deletion of the DNS records by running 'nltest.exe
/dsregdns' from the command prompt or by restarting Net Logon service.
Nltest.exe is available in the Microsoft Windows Server Resource Kit
CD.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
ERROR2:
Dynamic registration or deletion of one or more DNS records associated
with DNS domain 'top.local.' failed. These records are used by other
computers to locate this server as a domain controller (if the
specified domain is an Active Directory domain) or as an LDAP server
(if the specified domain is an application partition).
Possible causes of failure include:
- TCP/IP properties of the network connections of this computer
contain wrong IP address(es) of the preferred and alternate DNS
servers
- Specified preferred and alternate DNS servers are not running
- DNS server(s) primary for the records to be registered is not
running
- Preferred or alternate DNS servers are configured with wrong root
hints
- Parent DNS zone contains incorrect delegation to the child zone
authoritative for the DNS records that failed registration
USER ACTION
Fix possible misconfiguration(s) specified above and initiate
registration or deletion of the DNS records by running 'nltest.exe
/dsregdns' from the command prompt or by restarting Net Logon service.
Nltest.exe is available in the Microsoft Windows Server Resource Kit
CD.
For more information, see Help and Support Center at
Second problem is for 123.top.local child domain. This domain has two
DC as well. On both DC, all zones _msdcs.top.local, top.local.
123.top.local and abc.top.local appear. All zones are AD integrated.
All zones except 123.top.local are set to replicate in forest. When I
try to set 123.top.local replication in forst it gives me error saying
"The name limit for the local computer network adapter card was
exceeded." I tried this on both DC and same error occured. Now
whenever I restart DNS service, it gives error event ID 4515 in logs
twice. First error is like this:
ERROR1:
The zone 123.top.local was previously loaded from the directory
partition MicrosoftDNS but another copy of the zone has been found in
directory partition DomainDnsZones.123.top..local. The DNS Server will
ignore this new copy of the zone. Please resolve this conflict as soon
as possible.
If an administrator has moved this zone from one directory partition
to another this may be a harmless transient condition. In this case,
no action is necessary. The deletion of the original copy of the zone
should soon replicate to this server.
If there are two copies of this zone in two different directory
partitions but this is not a transient caused by a zone move operation
then one of these copies should be deleted as soon as possible to
resolve this conflict.
To change the replication scope of an application directory partition
containing DNS zones and for more details on storing DNS zones in the
application directory partitions, please see Help and Support.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
ERROR2:
The zone 123.top.local was previously loaded from the directory
partition MicrosoftDNS but another copy of the zone has been found in
directory partition ForestDnsZones.top.local. The DNS Server will
ignore this new copy of the zone. Please resolve this conflict as soon
as possible.
If an administrator has moved this zone from one directory partition
to another this may be a harmless transient condition. In this case,
no action is necessary. The deletion of the original copy of the zone
should soon replicate to this server.
If there are two copies of this zone in two different directory
partitions but this is not a transient caused by a zone move operation
then one of these copies should be deleted as soon as possible to
resolve this conflict.
To change the replication scope of an application directory partition
containing DNS zones and for more details on storing DNS zones in the
application directory partitions, please see Help and Support.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Please tell me how to deal with errors. I am very greatful in adavance
for helping me out.
Thanks
Shohab
- Next message: Steve Bruce, mct: "Re: dns questions"
- Previous message: Jack Ryan: "dns questions"
- Next in thread: Roger Abell: "Re: DNS issues after upgrading from NT4.0 to Windows 2003. Please help."
- Reply: Roger Abell: "Re: DNS issues after upgrading from NT4.0 to Windows 2003. Please help."
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
