Incorrect DNS information controlled by Group Policy

By cfrait ·
I was troubleshooting an issue with DNS and set the clients DNS to an external DNS server using group policy (which overrides any local settings). The secondary DNS is an internal DNS sever (the DC), but the clients are not connecting to the domain.

Now, I can't use gpupdate /force to update the clients and remove this policy because they can't find the DC.

Obviously, this was a really stupid mistake, but how can I fix it? How can I either manually send an updated group policy to my clients or force the dns client to use the secondary DNS so that it can find the domain?

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Answers

Collapse -

Figured out a Fix

by cfrait In reply to Incorrect DNS information ...

In the registry, HKLM\Software\Policies\Microsoft\Windows NT \DNSClient

Changed the value of "NameServer" to my internal server and now DNS is using the internal server to connect to the domain.

Collapse -

Redirect ip address on the router?

by TobiF In reply to Incorrect DNS information ...

Is it possible to temporarily redirect the external dns to be forwarded to your DC?
Or at least block outgoing UDP traffic to port 53 on the main server, to force failover to secondary DNS...

Related Discussions

Related Forums