Re: 169.254.x.x auto registrering as a (same as parent folder)!
- From: "Herb Martin" <news@xxxxxxxxxxxxxx>
- Date: Tue, 17 Apr 2007 09:38:10 -0500
"Claude Lachapelle" <ClaudeLachapelle@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:DF1A4171-1785-4397-9B60-F038FCB52A04@xxxxxxxxxxxxxxxx
Hi!
We have a strange issue, we have a workstation or a server that it is
registrering into the dns as a Host (A) record (same as parent folder),
which
are supposed to be used to identify domain controller for that domain.
Since this an invalid ip address, every application doing ldap requests on
that domain are getting this address, and before falling back to another
good
one, this is taking a lot of time (sometime they timing out!).
This is really annoying, since everytime we delete it, it is coming back
15
min. later. We tried to activated all disabled NIC on all domain
controllers,
but that did not fixed the problem. We disabled a RRAS which was not used
anymore on one of the DCs, but the address is still coming back!
So as a quick fix, we created a dummy Host (A) record with the same ip
address -- this fix temporarely the problem, since it seem the workstation
is
not able to overwrite this record!
BUT, we want to know where this record is coming from? How we can acheive
that? Using Network Monitor? Any suggestions?
Usually it if from an additional but UNUSED network interface.
A NIC or even an RAS/VPN interface which has no manual address and no
way to acquire one from DHCP.
Since it has no address, it defaults to making up one using APIPA range of
169.254.x.y -- thus this range is the tip off to the likely problem and
worth
memorizing.
Disable all unused/unassigned Network Interfaces or set them to avoid
registration.
--
Herb Martin, MCSE, MVP
http://www.LearnQuick.Com
(phone on web site)
.
- Prev by Date: Forward Lookup Zones - Expired
- Next by Date: Re: Reverse Lookup setup
- Previous by thread: Forward Lookup Zones - Expired
- Next by thread: AD 2003 DNS issue: multiple hosts, same IP
- Index(es):
Relevant Pages
|