Dynamic DNS issue

  • Thread starter Thread starter AAO
  • Start date Start date
A

AAO

Does anyone else have a problem with domain clients dynamically registering
themselves in the DNS as the following:

(Same as Parent Folder) Host <Ip Address goes here>

This has not been occuring on a consitent basis. Thus far, I have not been
able to figure out what causes this. In a months time, one or two clients
will register records such as this; however, there are some months that we
will not get any records like this registered to the DNS at all. From what
I could tell this problem is not specific to a particular machine and if I
delete the records, a whole other set of clients will do this same thing,
given time. When the client registers itself as this record the client is
added to the list of machines that can resolve to the AD domain suffix.
From what I can tell this should only be domain controllers. Anyone else
see this behavior?

Thanks in advance.

AO
 
Hello,

Besides checking for viruses or for some kind of LDAP application that is adding these records you may want to configure the AD zone in DNS for secure
dynamic updates only.
Here is something else to consider, in case you of multihomed Domain controllers:

295328 "Private Network Interfaces on a Domain Controller Are Registered in DNS"
http://support.microsoft.com/default.aspx?scid=kb;en-us;295328
--------------------
From: "AAO" <[email protected]>
Subject: Dynamic DNS issue
Date: Fri, 30 Apr 2004 15:08:23 -0500

Does anyone else have a problem with domain clients dynamically registering
themselves in the DNS as the following:

(Same as Parent Folder) Host <Ip Address goes here>

This has not been occuring on a consitent basis. Thus far, I have not been
able to figure out what causes this. In a months time, one or two clients
will register records such as this; however, there are some months that we
will not get any records like this registered to the DNS at all. From what
I could tell this problem is not specific to a particular machine and if I
delete the records, a whole other set of clients will do this same thing,
given time. When the client registers itself as this record the client is
added to the list of machines that can resolve to the AD domain suffix.
From what I can tell this should only be domain controllers. Anyone else
see this behavior?

Thanks in advance.

AO
Click to expand...

--
Sergio Moreno
Microsoft Windows Networking

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.
 
Sergio,

Thanks for your reply.

The DC's have all been scanned for virus' using the latest virus definition
file. There are no LDAP applications interacting with the DC's directly. I
am currently considering setting up DNS for secure updates to see if this
resolves this problem; however I suspect it may not because the clients
registering these records are legitimate clients of the domain. I also
found the article that you mentioned (295328) on the Microsoft Online
Knowledge Base but dismissed it because the DC's are not multihomed plus the
symptoms were not the same.

Regards,
AO
-------------------------------
Click to expand...
Sergio Moreno(MSFT) said:
Hello,

Besides checking for viruses or for some kind of LDAP application that is
Click to expand...
adding these records you may want to configure the AD zone in DNS for secure
dynamic updates only.
Here is something else to consider, in case you of multihomed Domain controllers:

295328 "Private Network Interfaces on a Domain Controller Are Registered in DNS"
http://support.microsoft.com/default.aspx?scid=kb;en-us;295328
--------------------

--
Sergio Moreno
Microsoft Windows Networking

This posting is provided "AS IS" with no warranties, and confers no
Click to expand...
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
Click to expand...
message are best directed to the newsgroup/thread from which they
originated.
 
Hi there,

it is difficult to determine the root cause of this issue without more indepth troubleshooting.
You may want to consider other support options to address this issue, please take a look at the following URL:

http://www.microsoft.com/resources/documentation/WindowsServ/2003/all/ads/en-us/Default.asp?
url=/resources/documentation/WindowsServ/2003/all/ADS/en-us/ads_support_information.asp

--------------------
From: "AAO" <[email protected]>
References: <[email protected]> <[email protected]>
Subject: Re: Dynamic DNS issue
Date: Wed, 5 May 2004 08:55:20 -0500
Click to expand...
Sergio,

Thanks for your reply.

The DC's have all been scanned for virus' using the latest virus definition
file. There are no LDAP applications interacting with the DC's directly. I
am currently considering setting up DNS for secure updates to see if this
resolves this problem; however I suspect it may not because the clients
registering these records are legitimate clients of the domain. I also
found the article that you mentioned (295328) on the Microsoft Online
Knowledge Base but dismissed it because the DC's are not multihomed plus the
symptoms were not the same.

Regards,
AO

adding these records you may want to configure the AD zone in DNS for secure
rights. Use of included script samples are subject to the terms specified at
message are best directed to the newsgroup/thread from which they
originated.
Click to expand...

--
Sergio Moreno
Microsoft Windows Networking

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.
 
Back
Top