DNS Record keeps changing

[steveh]

Hi
I have one windows 2003 server that keeps having it's dns
record changed on both of my DNS servers. I check the
server itself, and it's IP address hasn't changed and
there are no secondary IP address configured either. I
can manually reset the record on the DNS server but a few
hours later it changes itself back. The result is no-one
can access the server because the name and IP address do
not match. Any ideas on where it could be pulling this
erroneous IP address from?

Steve

 

[Guest]

Is it the SOA or the NS record that keeps changing? When
it changes does it change the ip to an external ip address?

 

[Larry Stotler]

Hello,

What OS are you running on your DNS servers? If they are 2003 servers you
can enable debug logging in the DNS console at the server level. You can
set it to log updates. This way you can see where the updates are coming
from.

If it is not 2003 then we will just need to do some investigative work.
What is the name of the client that is having the name changed? Are your
DNS server ONLY pointing internally at themselves for DNS? Is your
internal domain name the same as your external? Are you getting any weird
DNS related Events in your event log?

Larry Stotler, MCSE
Microsoft Product Support

NOTE: Please reply to the newsgroup and not directly to me. This allows
others to add to and benefit from these threads and also helps to ensure a
more timely response. Thank you!

This posting is provided "AS IS" without warranty either expressed or
implied, including, but not limited to, the implied warranties of
merchantability or fitness for a particular purpose

 

[steveh]

Thank you for your reply. The two DNS servers are Windows
2000 SP4 machines. They point to each other for DNS
resolution and then have a forwarder configured for
offsite name resolution. The name of the client server
is 'bobcat' and it is changing the IP address in the dns
record not the name of the client - I don't think I made
that clear in the original post. It changes from x.x.x.17
to x.x.x.97
Thanks

Steve

 

[Larry Stotler]

Hello,

Then we need to do some work to find out who x.x.x.97 is. This is most
likely the culprit. I would first check to make sure that Bobcat does not
have this IP address bound to it also. If not then I would try to find who
has the IP. If it is not immediately clear who has this IP then try to
connect to this IP. Try to remote desktop in or just connect to a share
and try to figure out who it is. Once you find this client check its name
and see if it is Bobcat. If it is not you can search the registry for the
name. It may be some bad reg key that has been modified.

Larry Stotler, MCSE
Microsoft Product Support

NOTE: Please reply to the newsgroup and not directly to me. This allows
others to add to and benefit from these threads and also helps to ensure a
more timely response. Thank you!

This posting is provided "AS IS" without warranty either expressed or
implied, including, but not limited to, the implied warranties of
merchantability or fitness for a particular purpose