This is not really a group policy issue - meaning you could have been
more judicious in your choice of cross-posted newsgroups.
Perhaps a post only to microsoft.public.windows.server.dns ???

Anyway, when you said
> If we flush DNS on the client or restart the client it will connect again
> fine.
indicates that the client has been given an invalid IP since flushing the
client will not change its current in-use DNS server (for that use
net stop dnscache / net start dnscache). Hence, your question is how
did the client cache get poisoned?


"Tim" wrote in message
news:124if2ljgb7geb1@corp.supernews.com...
> We have an issue with our inhouse DNS. We have one server that is not a
> DC,
> it is a domain member however. We have clients that will have no issue
> connecting to this server and then all of sudden they can not connect.
> Instead the client will be redirected to our main DC that host the GC. If
> we flush DNS on the client or restart the client it will connect again
> fine.
> It is very sporadic, and will happen on one machine one day and a
> different
> machine another day. I checked all DNS settings on our server and they
> look correct. I even took them out and put them in Manually once, another
> time I deleted them and ran ipconfig /registerdns on the server that we
> can
> not connect to and it seemed to register correctly. Can anyone shead some
> light on what the heck this may be?
>