Why do I get inconsistent data in DNS tree?

[Egil Hansen]

Hi all

Sometimes a dns record for a PC and the ip assigned to a PC doesn't
match. E.g. last week PC001 would have IP 10.0.0.2, and I could connect
to it using its DNS name, since the DNS servers record for PC001 was
10.0.0.2. But this week, PC001 have a new IP (assigned by dhcp) -
say 10.0.0.5, but the DNS servers record isn't updated, it still
points to 10.0.0.2. How can I fix this?

We have a Windows 2000 AD (not in native mode I'm afraid), with
Windows 2000 servers running DNS and DHCP. Is my problem due to a lower
lease time on IP's on my DHCP server, and a longer update time on DNS
records?

Thanks, and best regards,
Egil.

 

[Ace Fekay [MVP]]

In

Hi all

Sometimes a dns record for a PC and the ip assigned to a PC doesn't
match. E.g. last week PC001 would have IP 10.0.0.2, and I could
connect to it using its DNS name, since the DNS servers record for
PC001 was
10.0.0.2. But this week, PC001 have a new IP (assigned by dhcp) -
say 10.0.0.5, but the DNS servers record isn't updated, it still
points to 10.0.0.2. How can I fix this?

We have a Windows 2000 AD (not in native mode I'm afraid), with
Windows 2000 servers running DNS and DHCP. Is my problem due to a
lower lease time on IP's on my DHCP server, and a longer update time
on DNS records?

Thanks, and best regards,
Egil.

See my reply in the windows.server.dns group to see if that helped.

It would have been to your advantage to have cross-posted so both groups see
the post, and when a reply is posted, it goes to both simultaneously. It
achieves more efficient collaboration as well.

Ace

(cross posted to windows.server.dns group)

 

[Jorge_de_Almeida_Pinto]

Hi all

Sometimes a dns record for a PC and the ip assigned to a PC
doesn't
match. E.g. last week PC001 would have IP 10.0.0.2, and I
could connect
to it using its DNS name, since the DNS servers record for
PC001 was
10.0.0.2. But this week, PC001 have a new IP (assigned by
dhcp) -
say 10.0.0.5, but the DNS servers record isn't updated, it
still
points to 10.0.0.2. How can I fix this?

We have a Windows 2000 AD (not in native mode I'm afraid),
with
Windows 2000 servers running DNS and DHCP. Is my problem due
to a lower
lease time on IP's on my DHCP server, and a longer update time
on DNS
records?

Thanks, and best regards,
Egil.

How is DDNS setup on the DHCP server and on the client?

Is the client configured to register the IP address in DNS?

Does the DNS zone accept dynamic updates?

Does the DHCP server register on behalf of the client or not

Does the client belong to the domain?