Hi All,
I've encountered a strange problem that has me stumped.
I have a vista x64 workstation (hosting a share) that had been getting
assigned an ip address by DHCP, but which I changed to a static
address a few weeks ago. When I switched it to static, it had an
erroneous forward lookup record in our dns servers' zone files (the
record was a duplicate, another machine actually owned that particular
ip address). I then deleted the duplicate record and switched the
workstation to static ip and manually entered the new forward lookup
(along with the reverse pointer).
Ever since then, every day at a specific time, the old record I
deleted is somehow recreated. This leads over time, once other
machines refresh their cached local host records, to machines not
being able to access the share. I then go in and re-delete the record
and the story goes on and on.
Now, I have had some issues in the past with stale DNS records
(populated by DHCP) not getting purged, and it is probable that there
is some configuration issue to blame. I am not sure if that is in any
way related to the recurring lookup record referred to in the previous
paragraph though.
So far my only idea has been to double check the workstation and make
sure the static values are still set and to verify that there isn't a
second network adapter that I am forgetting about. These don't appear
to be issues. I also did a registry search on the workstation for the
erroneous ip address (although my search was for decimal quads, maybe
a hex or binary number search is more applicable?) in hopes of
determining, if the workstation had something lurking in the registry,
that the workstation is the issue and not a DHCP/DNS server. I found
nothing though. Lastly, I checked my two DNS and DHCP server settings
for anything I thought might cause this (e.g. a reserved ip address in
a DHCP scope, a rogue DNS server with which replication is occurring,
etc.), but nothing popped out at me
Any thoughts on this would really be appreciated.
Thanks
Tim
P.S. My net config is 2 W2K3 servers each running DHCP (different
scopes) set to update DNS and each running DNS. Only one subnet.
|