How can I refresh my local cached DNS records?

I have just changed the DNS A-Record with my ISP to point to the IP address of our new web hosting server (which takes up to "24 - 48hrs" to propagate around the world).

In my experience, it "usually" takes about 3 - 4 hours for us to check and see the site on the Internet via a local web browser however, if we check within our LAN, this time frame can be distorted by a greater length of time as cached record is returned from our local DNS server returning the old site.

How can I force our local DNS server to re-check the master DNS record with our ISP? Or get it to re-check at a more frequent time frame e.g. an hour (once the new site is seen, I can then revert it back to lessen the network traffic).

Apologies for the lack of official terminology!
IvanHowarthAsked:
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

x
 
bradleys40Commented:
from the link i sent go to the "Managing DNS and DHCP class IDs by using ipconfig" section for more information
0
 
KCTSConnect With a Mentor Commented:
ipconfig /flushdns will flush the local name cache, you also need to flush the cache on your own DNS server. Open the DNS console, right click on the DNS server and select "Clear Cache"
0
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

 
Chris DentConnect With a Mentor PowerShell DeveloperCommented:

Bear in mind that if you use a Forwarder to retrieve public records you'll just get the cached response back again.

Chris
0
 
IvanHowarthAuthor Commented:
OK, "ipconfig /flushdns" on both client machine and DNS Server.
 
But going by Chris-Dent's comment, how do I know if I use a Forwarder to retrieve public records? Looking at our dnsmgmt consol, I basically have the following:

-Forward Lookup Zones
    -MyDomain.local
        -[Other folders]
-Reverse Lookup Zones
    -10.0.0.x subnet
0
 
KCTSCommented:
also don't forget Open the DNS console, right click on the DNS server and select "Clear Cache" - this is the DNS server cache - different from the local name cache.
0
 
Chris DentPowerShell DeveloperCommented:

Forwarders is set under the Properties for the Server (as a Tab). It's more likely that you're not using them if you're not sure.

Chris
0
 
KCTSCommented:
Forwaders are set on the Forwarders Tab, Right click on the DNS server itself in the DNS console and look under forwarders.

I think the point that Chris-Dent was trying to make is that external DNS servers that you rely on for forwarding may also have thier own cache - and there is nothing you can to to clear these - they are not your machines, and any IPs retrived from these may still be incorrect until their caches expire.
0
 
Chris DentPowerShell DeveloperCommented:

Yep, KCTS is right, just thought it worth mentioning in case you bumped into a problem that wouldn't go away.

Chris
0
 
IvanHowarthAuthor Commented:
There are two Forwarders set, using WHOIS, they both point to our ISP anyway. Confirming with our ISP, the A-Record has been changed and now propagating.

I'll periodically "ipconfig /flushdns" and wait.

Thanks all.
0
 
IvanHowarthAuthor Commented:
Just done the above, all worked, and now have access to our new site - excellent!

Thks again!
0
All Courses

From novice to tech pro — start learning today.