?
Solved

How to check out our DNS replication and clear the cache and stale records if they exist?

Posted on 2009-04-08
9
Medium Priority
?
1,653 Views
Last Modified: 2012-05-06
We were told to look into our DNS replication and remove any stale records.
We are a small-medium sized business with 3 branch locations.
Please ask whatever questions you have and I will get back to you promptly.
There is 1 domain controller in 2 of the branches and 2 more domain controllers in the main branch (where I work).
Thanks in advance.
0
Comment
Question by:homerslmpson
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 5
  • 4
9 Comments
 
LVL 71

Expert Comment

by:Chris Dent
ID: 24136068

Active Directory?
Do you use DHCP? If so, how long is the Lease?
Does DHCP update DNS for you (this is the default setting, so if you haven't changed anything it will)?
If DHCP updates DNS, do you have more than one DHCP server?
Have you configured Aging / Scavenging at all?

Chris
0
 
LVL 1

Author Comment

by:homerslmpson
ID: 24136835
Active Directory? YES
Do you use DHCP? If so, how long is the Lease? YES, the lease is 8 days
Does DHCP update DNS for you (this is the default setting, so if you haven't changed anything it will)? All 4 DHCP servers are set to the following option:
"Dynamically update DNS A and PTR records only if requested by DHCP clients"
If DHCP updates DNS, do you have more than one DHCP server? There are 4 DHCP servers total (2 in the main branch and 1 in each of the 2 branch locations)
Have you configured Aging / Scavenging at all? I just checked all 4 servers and none of them seem to have that option enabled

Thanks in advance for your help.
0
 
LVL 71

Expert Comment

by:Chris Dent
ID: 24137184

Do your clients move between sites at all? If they do, we should configure DHCP to use specific credentials when updating DNS, otherwise each DHCP server won't be able to change records created by other DHCP servers.

Aging and Scavenging is our cleanup process, it'll take a while to configure, but you have nothing really unusual. I would enable 3 Days No-Refresh and 5 Days Refresh on each zone where records are being added (and tick the box at the top that enables the zone for Scavenging). That makes a total of 8 days before a record can become Stale (and be Scavenged), matches up nicely with the DHCP Lease Time.

Once the settings are in you need one of your DNS servers to run the Scavenging process, this is set in the DNS console, Properties for the server under the Advanced Tab. I recommend setting the Scavenging Interval to 1 day (so it runs the task once a day).

It's not quite as straight-forward as that, even then it won't clean out anything immediately. This article from the MS guys does a good job of explaining the settings and how they work together:

http://blogs.technet.com/networking/archive/2008/03/19/don-t-be-afraid-of-dns-scavenging-just-be-patient.aspx

It's well worth reading. If it raises any questions about the process then I'll happily expand on it.

Chris
0
Bringing Advanced Authentication to the SMB Market

WatchGuard announces the acquisition of advanced authentication provider, Datablink, with one mission – to bring secure authentication to SMB, mid-market, and distributed enterprises with a cloud-based solution, ideal for resale via their established channel & MSSP community.

 
LVL 1

Author Comment

by:homerslmpson
ID: 24138393
OK I followed all of the steps you mentioned above.

I also right-clicked on each server and selected SCAVENGE STALE RESOURCE RECORDS on each server as well.

I don't know if that was beneficial or harmful.

Any final thoughts?

Thanks for your help, I really appreciate it.
0
 
LVL 71

Expert Comment

by:Chris Dent
ID: 24138455

You only want to make these changes on one server.

Changes made to each zones Aging will automatically replicate to all other DNS servers.
Only one server should be running the Scavenging task (Server Properties / Advanced / Enable Automatic Scavenging of Stale Records)

Enabling it on a single server prevents confusion, changes made by that server are replicated to the others.

Chris
0
 
LVL 1

Author Comment

by:homerslmpson
ID: 24138625
OK. I have made only 1 server responsible for the scavenging task.
I also unchecked the aging box on the other 3 servers as well.

Was it OK that I did this:
"I also right-clicked on each server and selected SCAVENGE STALE RESOURCE RECORDS on each server as well."

When setting up the aging on the one server I also checked the box that says:
APPLY THESE SETTINGS TO THE EXISTING ACTIVE DIRECTORY-INTEGRATED ZONES.

Was this OK?

Thanks again!
0
 
LVL 71

Accepted Solution

by:
Chris Dent earned 2000 total points
ID: 24138774

You have a few options that are getting confused here:

1. Set Aging\Scavenging for all zones

You find this option by right clicking on the server in the DNS console. You can use this option to configure Aging for all zones on a server.

Aging can be deselected on individual zones after this has been used if required.

2. Zone Properties / Aging

Found by opening the Properties for an individual zone, then clicking the Aging button. If you have a mixture of zones and you only want to use Aging / Scavenging on a small number of them.

If you set these via 1 it will overwrite the settings here.

Clearing the setting from here on any DNS server will cause the change to replicate to all DNS server hosting the zone. That means if you cleared the setting on one of the three DCs it will replicate to the other two. Make sure yours is still set.

Check yours are still enabled because unticking it on the other two should replicate to the third DC.

3. Enable Scavenging / Scavenging Interval

Found in the Server Properties under the Advanced Tab. This sets up a server to perform the cleaning task, without this one the other settings are just aesthetic (look pretty).

This one should be set on a single server, only one needs to be running this task.

Chris
0
 
LVL 1

Author Comment

by:homerslmpson
ID: 24139007
OK so:

1. Set Aging\Scavenging for all zones I DID ON ALL SERVERS

I skipped 2.

3. Enable Scavenging / Scavenging Interval I DID ON ONLY 1 SERVER

Is this correct?


0
 
LVL 71

Expert Comment

by:Chris Dent
ID: 24139199

Great, that's absolutely fine :-D

Chris
0

Featured Post

Get free NFR key for Veeam Availability Suite 9.5

Veeam is happy to provide a free NFR license (1 year, 2 sockets) to all certified IT Pros. The license allows for the non-production use of Veeam Availability Suite v9.5 in your home lab, without any feature limitations. It works for both VMware and Hyper-V environments

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

I wrote this article to explain some important DNS concepts that should be known to avoid some typical configuration errors I often see in forums. I assume that what is described here is the typical behavior of Microsoft DNS client. I don't know …
There have been a lot of times when we have seen the need to enter a large number of DNS entries in a forward lookup zone. The standard procedure would be to launch the DNS Manager console, create the Zone and start adding new hosts using the New…
This is my first video review of Microsoft Bookings, I will be doing a part two with a bit more information, but wanted to get this out to you folks.
In this video, Percona Solution Engineer Dimitri Vanoverbeke discusses why you want to use at least three nodes in a database cluster. To discuss how Percona Consulting can help with your design and architecture needs for your database and infras…
Suggested Courses
Course of the Month13 days, 19 hours left to enroll

801 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question