Refresh Clients to new DNS?

[jmair]

We updated our DNS and now some clients are connecting to it and resolving to AD, however many are not. I can manually remove the client from the domain and re-join and all works fine, however I'm hoping there is a better way of doing this to the clients that will be coming back on campus next week.

I have tried ipconfig /flushdns ipconfig /registerdns

 

When I ping or do a nslookup by server it will fail to resolve. Pinging by ip works fine. So the device acts like it no longer has privileges.

 

Aside from manually touching each device, any suggestions how to solve this problem?

[jslate1980]

We updated our DNS and now some clients are connecting to it and resolving to AD, however many are not. I can manually remove the client from the domain and re-join and all works fine, however I'm hoping there is a better way of doing this to the clients that will be coming back on campus next week.

I have tried ipconfig /flushdns ipconfig /registerdns

 

When I ping or do a nslookup by server it will fail to resolve. Pinging by ip works fine. So the device acts like it no longer has privileges.

 

Aside from manually touching each device, any suggestions how to solve this problem?

Has your new dns server been added to the scope options of your dhcp server scopes?

[jmair]

In the DHCP Scope Options, the DNS Domain Name and DNS server (static internal ip) is the same. I did resolve it to the domain name in case that would make any difference. It currently look like.

 

DNS Servers

10.1.1.2 (the local dns)

8.8.8.8

8.8.4.4

[Davit2005]

Is this on prem AD?

 

Don't specify google dns to clients, only specify the DNS related to the Active Directory would be my first thing. Then specify external DNS as forwarders on the DNS servers.

 

Then you could run dcdiag on the domain controller to make sure all is OK that side.

Edited August 11, 2021 by Davit2005

[jmair]

Is this on prem AD?

 

Don't specify google dns to clients, only specify the DNS related to the Active Directory would be my first thing. Then specify external DNS as forwarders on the DNS servers.

 

Then you could run dcdiag on the domain controller to make sure all is OK that side.

All good now ( I hope ). Will know more when folks trickle in. Thank you for the support btw, few places to get it.

[mikemcsharry]

If you end up with a rogue PC (or three) here's a few things I found out over the years

1. Check the time on the devices and compare with your Active Directory

2. Run elevated command prompt netsh winsock reset (then reboot), that normally fixes things

if after reboot you have issue, try elevated command netsh int ip reset

 

Those last 2 commands clear out a big stack of garbage