Outdated Zone host records and RDP issues
- From: kettlnaut <kettlnaut@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 30 Jan 2008 06:47:12 -0800
The first time I posted this in the DNS forums I didn't get a response,
however I didn't have a full comprehension of the problem. Somebody pointed
me in the direction of DNS problem, and that led us to discover outdated host
record entries in our forward and reverse lookup zones. For those hosts with
duplicate entries (i.e. multiple IP addresses for 1 host) there was an issue
with RDP going to the wrong machine. You typed PC6, you got PC46. It seemed
that the dup entry is an outdated host record, and it just so happens to have
the same IP as a different host that actually does have the IP that the
outdated dup contains. We had to look at the DHCP lease list to get the
correct host address, then delete the inacurrate record in the forward and
reverse lookup zones. Once the records no longer conflicted, we had no RDP
issues (and I should also mention that we never have RDP issues when using
IP's for the host name, however we use DHCP for all of our XP clients, so we
need to be able to get around the network by machine name, rather than always
having to lookup the IP). So the issue it seems, is that our DNS is not
properly updating the records in it's lookup zones. Now we can correct this
manually, however (a) we feel this is risky procedure as we have little
knowledge of DNS server (b) we have around 40 - 50 hosts and we don't have
time to manually update the DNS. So we need to resolve the issue with our
DNS not recieving updates, and I believe the clues are in the log files.
There are paterns of errors and warnings in our DNS Event Log that repeat
over and over:
4515 - Warning
2 - Information
It alternates this combo of events 5 times (for a total of 10 entries) then
shows this:
4015 - Error
Then it throws 5 of these:
4004 - Error
Then it starts up with another set of 10 of the first two events and repeats
the whole thing again over and over. Any help resolving this would be great,
this seems to cause us more problems as time goes on. See below for the
details of the log event IDs(note - any domain name reference to our company
name has been changed to organization.local, in place of our true
organizationname.local, in order to keep anonymity):
2 - Information
The DNS server has encountered a critical error from the Active Directory.
Check that the Active Directory is functioning properly. The extended error
debug information (which may be empty) is "". The event data contains the
error.
4004 - Error
The DNS server was unable to complete directory service enumeration of zone
... This DNS server is configured to use information obtained from Active
Directory for this zone and is unable to load the zone without it. Check
that the Active Directory is functioning properly and repeat enumeration of
the zone. The extended error debug information (which may be empty) is "".
The event data contains the error.
4015 - Error
The DNS server has encountered a critical error from the Active Directory.
Check that the Active Directory is functioning properly. The extended error
debug information (which may be empty) is "". The event data contains the
error.
4515 - Warning
The zone organization.local was previously loaded from the directory
partition MicrosoftDNS but another copy of the zone has been found in
directory partition DomainDnsZones.ORGANIZATION.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.
--
Thanks for your time.
-Kettle
.
- Follow-Ups:
- Re: Outdated Zone host records and RDP issues
- From: Kevin D. Goodknecht Sr. [MVP]
- Re: Outdated Zone host records and RDP issues
- Prev by Date: Re: DNS names setup
- Next by Date: Re: Website dns without www?
- Previous by thread: Re: RDP Issues after SYSPREP
- Next by thread: Re: Outdated Zone host records and RDP issues
- Index(es):
Relevant Pages
|
