dns problems -help

[Guest]

Hi
I hope some one has seen this before

When i ping via host name to one of my domain clients, it resolves the name to an ip that then doesnt respond to the ping
i then look in dhcp for the clients hostname i see it and it is assosiated witha differnt ip then was resolved. when i ping (-a) the ip it resolves the correct host name (the same as what i ping orignally) and the ping works.if i get the user to log out of the domain and then relogin, when i ping the host name it resolves fine. i have a 200 seat center and this is happening inconsistanly
also i have been geting event id: 5781 on my dns server i have look through the technet site and found a few things but this is a production server and i would like to know witch one will fix my problem before i start experimenting. i know that the two are probley the same problem but i need some help

anyhelp whould be greatly appersiated

Regards
Brad

 

[Simon Whale]

brad,

have a look at the following as it sounds like their is a problem with dns.

http://www.eventid.net/display.asp?eventid=5781&eventno=167&source=NETLOGON&phase=1

hope this helps
Simon

Hi
I hope some one has seen this before:

When i ping via host name to one of my domain clients, it resolves the

name to an ip that then doesnt respond to the ping.

i then look in dhcp for the clients hostname i see it and it is assosiated

witha differnt ip then was resolved. when i ping (-a) the ip it resolves the
correct host name (the same as what i ping orignally) and the ping works.if
i get the user to log out of the domain and then relogin, when i ping the
host name it resolves fine. i have a 200 seat center and this is happening
inconsistanly.

also i have been geting event id: 5781 on my dns server i have look

through the technet site and found a few things but this is a production
server and i would like to know witch one will fix my problem before i start
experimenting. i know that the two are probley the same problem but i need
some help.

 

[Guest]

Thanks Simon

but i found that my problem was addressed in kb826743

Regards
Bradford Berry