Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

As in the title... I've made a new (Active Directory connected) conditional forwarder on one of our DNS servers (running Windows Server 2012).

Firstly, how long does it take to propagate to other DNS servers in our environment? And, how can I force it to propagate now?

EDIT: some more info

For the purpose of this discussion, we have two Windows Server 2012 machines (one at a remote site, and one locally). They are at different locations. Both are domain controllers, and have the DNS role enabled. I've added a conditional forwarder on the remote server, made sure it's replicated through AD (it's a checkbox you enable), and would like to know how long it'll take for that to propagate to the local DNS server.

By propagate I mean when will the conditional forwarder show up on the local DNS server?

share|improve this question
It depends on how sites and services are set up, but it should be done by now! – Dan Apr 4 '13 at 9:22
How do you have Active Directory Sites and Services configured? AD integrated DNS zones and/or Conditional Forwarders that are stored in AD should be replicated based on the replication settings and schedule in ADS&S. If you want to force it to replicate then force a replication in ADS&S. – joeqwerty Apr 4 '13 at 15:09
up vote 1 down vote accepted

As you know, AD Integrated zones are stored in AD and therefore are replicated along the same schedule. Inter-site replication occurs by default every three hours but can be configured to as little as 15 minutes (I can't think of a reason not to go down to 15 minutes, anyone?)

Although relatively miniscule, there is a second, shorter interval to be aware of. After the data has replicated to the DC, the DNS service must read this data from the local directory. How often this is done is based on the DsPollingInterval value, which defaults to three minutes.

So the latency is Inter-site replication interval + DsPollingInterval. In a default environment, the maximum latency is as long as 183 minutes.


  1. Absolute must-read on how AD replication works:
  2. Great post describing DsPollingInterval:
share|improve this answer

Define propagated, and define your other DNS servers.

DNS records are valid for as long as the other server considers them valid - once that time's up, the other DNS servers will forward requests onwards. There is no "pushing" from your DNS server, it's purely a pull mechanism.

So, to answer your questions explicitly:

  1. Your other DNS servers will (indirectly) use your new forwarder immediately, but only your DNS records which aren't cached or have expired.

  2. From your current DNS server, you can't. You could probably go to your other servers and flush their DNS cache, though.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.