Windows 2008 dns reload zone

Can you help us improve? Resolved my issue. Clear instructions. Easy to follow. No jargon. Pictures helped. Didn't match my screen. Incorrect instructions. Too technical. Not enough information. Not enough pictures. Any additional feedback? Submit feedback. Note : The time it takes to update the target controller depends on network performance.

If you want something ticking over in the background, use repadmin: Repadmin. I've used this to do pretty much the same thing. The OP has probably moved on to other things by now but there is one piece missing from the other answers. I found the solution on a blog alexwinner. Try this, worked in my situation albeit a different situation. After removing the secondary zone and changing the primary zone to ad domain integrated zone, first ensure the zone transfers are setup correctly then reload the zone on the primary.

In my case reloading the zone on primary forced the immediate sync to the other dns servers specified in the name servers tab. Sign up to join this community. The best answers are voted up and rise to the top. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Learn more. Server r2 Ask Question. Asked 9 years, 4 months ago. Active 4 years, 8 months ago. Viewed k times. We actually have two sites involved with this, so we have to wait even longer for the replication to the second site Is there some way to speed up DNS replication between: servers on the same site, and servers at different sites?

Improve this question. I tested everyone's suggestions and I just can not find a way to affect replication speed. It seems that there is still a minute delay, no matter what I do. After repeated testing PowerShell script loop running nslookup , I consistently see zones replicated between servers at the same -- and even different -- sites within one or two minutes. Unfortunately, I have not been able to reduce the time by any of your suggestions, although I am very grateful for the help.

Add a comment. Active Oldest Votes. Sure is. Cause Immediate Replication If you want replication to occur immediately instead of waiting for the typical replication cycle, follow these steps: In Administrative Tools , start Active Directory Sites and Services.

Expand Sites. There should be at least one site labeled "default-first-site-name" or others if they have been manually configured.

Expand default-first-site-name , expand Server s, and then expand Computer. For instance, there is a listing for our old server that is no longer in commission anymore. Finally, could anyone tell me why I would not want to add my switches to the DNS manually? The whole reason I am even at this is because I am running some network diagnostics traffic patterns, etc.

It is outdated so I have no idea what traffic is coming from where! For instance, there was a lot of RDP traffic going between my test machine and another machine that was listed as someone else's. It took me a while to figure out that it was actually MY machine!

To continue this discussion, please ask a new question. Get answers from your peers along with millions of IT pros who visit Spiceworks. Best Answer. Kyle12 This person is a verified professional. Verify your account to enable IT peers to see that you are a professional.

You can trun on stale records scaveging. View this "Best Answer" in the replies below ». Popular Topics in Windows Server.