Your company has an Active Directory domain. The main office has a DNS server named
DNS1 that is configured with Active Directory-integrated DNS. The branch office has a DNS
server named DNS2 that contains a secondary copy of the zone from DNS1. The two offices
are connected with an unreliable WAN link.
You add a new server to the main office.
Five minutes after adding the server, a user from the branch office reports that he is unable
to connect to the new server.
You need to ensure that the user is able to connect to the new server.
What should you do?
A.
Clear the cache on DNS2.
B.
Reload the zone on DNS1.
C.
Refresh the zone on DNS2.
D.
Export the zone from DNS1 and import the zone to DNS2.
Explanation:
Old answer) Refresh the zone on DNS2.
http://technet.microsoft.com/en-us/library/cc794900%28v=ws.10%29.aspx
Adjust the Refresh Interval for a Zone
You can use this procedure to adjust the refresh interval for a Domain Name System (DNS)
zone. The refresh interval determines how often other DNS servers that load and host the
zone must attempt to renew the zone.
By default, the refresh interval for each zone is set to 15 minutes.
http://blog.ijun.org/2008/11/difference-between-dnscmd-clearcache.html difference between
dnscmd /clearcache and ipconfig /flushdns
Q) Do “dnscmd /clearcache” and “ipconfig /flushdns” the exact same thing, on a windows
2003 server? What is the difference, if any?
A) Ipconfig /flushdns will flush the local computer cache. And dnscmd /clearcache will clear
the dns server cache.
Meaning that with the first you will clear the “local” cache of the server you work on. (Even if
it is the dns server. It will NOT clear the dns server cache.) While with dnscmd you will clear
the dns server cache.