Solved How long does it take for clients to resolve new IP from DNS on LAN?
-
We have changed an local DNS entry to another ip address. Or actually the customers internal IT has done this.
How long does it take for users to start using the new ip address?
- DNS points to a webserver
- Clients are running Win10 and some Win7
- Clients are using Chrome .
- Customer is a Windows shop (mostly) so I think DNS comes from AD?
-
@Pete-S said in How long does it take for clients to resolve new IP from DNS on LAN?:
@Obsolesce said in How long does it take for clients to resolve new IP from DNS on LAN?:
i thought they default to one day. Just check the DNS server quick to see.
Can I do that from a client? How?
try
ipconfig /displayDNS
-
Assuming they aren't cached, should be just a matter of minutes. This is all internal, correct?
-
@DustinB3403 said in How long does it take for clients to resolve new IP from DNS on LAN?:
Assuming they aren't cached, should be just a matter of minutes. This is all internal, correct?
Yes, just internal.
I read somewhere that TTL on DNS in AD is 7 days or something by default. I have no clue though. Only have a very cursory understanding of how it works.
-
@Pete-S said in How long does it take for clients to resolve new IP from DNS on LAN?:
@DustinB3403 said in How long does it take for clients to resolve new IP from DNS on LAN?:
Assuming they aren't cached, should be just a matter of minutes. This is all internal, correct?
Yes, just internal.
I read somewhere that TTL on DNS in AD is 7 days or something by default. I have no clue though. Only have a very cursory understanding of how it works.
On the client machines, you can force it by running ipconfig /flushdns -- that should force them to get the most recent DNS changes from AD.
-
@Pete-S said in How long does it take for clients to resolve new IP from DNS on LAN?:
I read somewhere that TTL on DNS in AD is 7 days or something by default.
I do not know either, but this would not surprise me. Windows always does shit stupid.
/glare default DHCP lease times -
@dafyre said in How long does it take for clients to resolve new IP from DNS on LAN?:
@Pete-S said in How long does it take for clients to resolve new IP from DNS on LAN?:
@DustinB3403 said in How long does it take for clients to resolve new IP from DNS on LAN?:
Assuming they aren't cached, should be just a matter of minutes. This is all internal, correct?
Yes, just internal.
I read somewhere that TTL on DNS in AD is 7 days or something by default. I have no clue though. Only have a very cursory understanding of how it works.
On the client machines, you can force it by running ipconfig /flushdns -- that should force them to get the most recent DNS changes from AD.
Thanks, good to know for future reference. Unfortunately in this case there are about 100 to 150 clients and they are out of our reach.
-
@Pete-S said in How long does it take for clients to resolve new IP from DNS on LAN?:
@dafyre said in How long does it take for clients to resolve new IP from DNS on LAN?:
@Pete-S said in How long does it take for clients to resolve new IP from DNS on LAN?:
@DustinB3403 said in How long does it take for clients to resolve new IP from DNS on LAN?:
Assuming they aren't cached, should be just a matter of minutes. This is all internal, correct?
Yes, just internal.
I read somewhere that TTL on DNS in AD is 7 days or something by default. I have no clue though. Only have a very cursory understanding of how it works.
On the client machines, you can force it by running ipconfig /flushdns -- that should force them to get the most recent DNS changes from AD.
Thanks, good to know for future reference. Unfortunately in this case there are about 100 to 150 clients and they are out of our reach.
Yikes...
-
@Pete-S said in How long does it take for clients to resolve new IP from DNS on LAN?:
@dafyre said in How long does it take for clients to resolve new IP from DNS on LAN?:
@Pete-S said in How long does it take for clients to resolve new IP from DNS on LAN?:
@DustinB3403 said in How long does it take for clients to resolve new IP from DNS on LAN?:
Assuming they aren't cached, should be just a matter of minutes. This is all internal, correct?
Yes, just internal.
I read somewhere that TTL on DNS in AD is 7 days or something by default. I have no clue though. Only have a very cursory understanding of how it works.
On the client machines, you can force it by running ipconfig /flushdns -- that should force them to get the most recent DNS changes from AD.
Thanks, good to know for future reference. Unfortunately in this case there are about 100 to 150 clients and they are out of our reach.
Have your client send an email to everyone - to get the new settings - reboot. problem solved.
-
@Pete-S said in How long does it take for clients to resolve new IP from DNS on LAN?:
We have changed an local DNS entry to another ip address. Or actually the customers internal IT has done this.
How long does it take for users to start using the new ip address?
- DNS points to a webserver
- Clients are running Win10 and some Win7
- Clients are using Chrome
- Customer is a Windows shop (mostly) so I think DNS comes from AD?
I thought they default to one
dayhour. Just check the DNS server quick to see.Edit: one hour, not one day.
-
@Obsolesce said in How long does it take for clients to resolve new IP from DNS on LAN?:
i thought they default to one day. Just check the DNS server quick to see.
Can I do that from a client? How?
-
@Pete-S said in How long does it take for clients to resolve new IP from DNS on LAN?:
@Obsolesce said in How long does it take for clients to resolve new IP from DNS on LAN?:
i thought they default to one day. Just check the DNS server quick to see.
Can I do that from a client? How?
try
ipconfig /displayDNS
-
You can use powershell to flush the DNS of remote systems.
Invoke-Command -script {Clear-DnsClientCache} -ComputerName Server01
If you have access to the DNS servers, you can try clearing the cache of each server.
-
@Dashrender I just checked a couple of clients and Time To Live where set to 3600 at most and counting down.
@Obsolesce If it's default then one hour it is.