Forward Lookup and Reverce Lookup zones entries are different

[rusavolk]

Hello,

I encountered a problem with my DNS (in Windows 2003 server).

The entries in forward Lookup zone are different form the entries in Reverse Lookup zone.

For example if do a "ping -a 10.10.10.20" it is pinging a machine with name "p00011", but if i would do "ping -a p00011" it is pinging a different address -- 10.10.10.55.

It is happening only for the machine on DHCP.
The machines/servers with static addresses are fine.

How can i fix it?
Thanks

 

[DylanThompson]

I'm not sure what you are trying to do here, but a ping -a is used to resolve a hostname from the specified IP address. Using a -a when pinging a hostname kind of defeats the purpose and may give some enexpected results. You should use ping -a "IP Address" and ping "hostname". Then they should both be the same addresses.

 

[rusavolk]

Yes, i see the point... using "ping -a notname" is stupid...

but still when i do "ping - a IPaddress" it resolves to a hostname, and when i do "ping hostname" it ping to a different ip address.

 

[DylanThompson]

Have you tried flushing the DNS cache on the client and server? Also, re-register the DNS on the target PC. So on the client do a ipconfig /flushdns, on the target do a ipconfig /registerdns and if you can, flush the DNS on the DNS server.

Are the two machine running the same OS? Could this be a WINS issues as opposed to a DNS issue? If one of the machine is pre-Win2K, the WINS DB may be having some sort of effect....

 

[rusavolk]

Client machines are all XPs. Wins is not in used on a Domain (lucky me), i use DNS for all names resolution.

On some of the client machines flushed and reregistered the dns. Now they look fine.

...but i am still thinking why this happened...
It probably will appear again...

 

[DylanThompson]

Will if you are using DHCP on the network and the machine p00011 is a client machine, it could be possible that another client machine will cache an IP address for it. Then is p00011 reboots/renews it's address and gets assigned a different IP, the cache of other client machine will be incorrect.

You could try lowering the TTL of the DNS records to force the client machines to regsiter their DNS more often and also to stop other clients machines from caching the records for so long.

 

[rusavolk]

Thank you