Strage IP address in DNS

  • Thread starter Thread starter DaG
  • Start date Start date
D

DaG

I have a Dell PE server that has 2 NIC's in it. It is the
only DNS server of a small domain. It is also the only AD
server. I am currently only using 1 of the 2 NIC's (#2 is
disabled by the OS). The AD zone is AD integrated.

I noticed that there was an A record with the default
192.168.234.x address registered for the server, as well
as the hard coded 10.1.1.x address. There was also an
entry for (same as previous folder) with the IP same
address. I kept deleting the (same as..) entry and it
keeps coming back. The host record seemed to keep coming
back whenever I went into the network setting on the
server. I have since enabled the other card and configured
it for teaming. I have not gone into the network settings,
however I think if I did, I'd see the mysterious A record
again. But the (same as..) thing bugs me...

Any ideas?? This is not impacting anyhting, but I imaging
if a user tries to find the server and gets the bogus
address, it could cause problems. I have better things to
do that to babysit DNS and delete bogus entries.

Anyone have any ideas???

-DaG
 
Is it in your Nameservers tab?

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
The netlogon service on a DC will register itself as same as parent within the zone for the AD. This is why this record keeps
coming back. It's required for AD operation. Do not delete it. If it's referencing the incorrect IP address, then you can disable
dynamic updates on the server and manually create all the records. This is usually a bad idea though. It's also not a good idea
to have a DC that is multihomed (two IP's or two NICs).

Thank you,
Mike Johnston
Microsoft Network Support
--

This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the
terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread from
which they originated.
 
The IP that is registering is actually a PPP adapter. Only
I cannot find one installed on the system. Any ideas??


-DaG

-----Original Message-----
The netlogon service on a DC will register itself as same
as parent within the zone for the AD. This is why this
record keeps
coming back. It's required for AD operation. Do not
delete it. If it's referencing the incorrect IP address,
then you can disable
dynamic updates on the server and manually create all the
records. This is usually a bad idea though. It's also
not a good idea
to have a DC that is multihomed (two IP's or two NICs).

Thank you,
Mike Johnston
Microsoft Network Support
confers no rights. Use of included script samples are
subject to the
terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all
responses to this message are best directed to the
newsgroup/thread from
 
It's from RAS. Here, read this:
292822 - Name Resolution and Connectivity Issues on Windows 2000 Domain
Controller with Routing and Remote Access and DNS Insta {DNS and RRAS and
unwanted IPs registering]:
http://support.microsoft.com/?id=292822

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
Back
Top