Your network contains an Active Directory forest named contoso.com.
Users frequently access the website of an external partner company.
The URL of the website is http://partners.adatum.com.
The partner company informs you that it will perform maintenance on its Web server and that the
IP addresses of the Web server will change.
After the change is complete, the users on your internal network report that they fail to access the
website. However, some users who work from home report that they can access the website.
You need to ensure that your DNS servers can resolve partners.adatum.com to the correct IP
address immediately.
What should you do?
A.
Run dnscmd and specify the CacheLockingPercent parameter.
B.
Run Set-DnsServerGlobalQueryBlockList.
C.
Run ipconfig and specify the Renew parameter.
D.
Run Set-DnsServerCache.
Explanation:
http://technet.microsoft.com/en-us/library/jj649852.aspx
Run Set-DnsServerCache with the -LockingPercent switch. dnscmd technically works also.
Technically, none of these options will work if the internal clients have it cached locally. You’d still end up waiting for the TTL of the client cache it expire or run an IPCONFIG /FLUSHDNS on every client.
Exactly
“…ensure that your DNS servers can resolve partners.adatum.com… ”
Set-DnsServerCache -MaxTtl 0x0
-MaxTtl 0x0
Specifies how many seconds (0x0-0xFFFFFFFF) a record is saved in cache. If you use the 0x0 setting, the DNS server does not cache records. The default setting is 0x15180 (86,400 seconds, or one day).
altenative answers list:
A Run ipconfig and specify the FlushDns parameter
B Run ipconfig and specify the Renew parameter.
C Run dnscmd and specify the ClearCache parameter <==== Correct answer
D Run Set-DnsServerResourceRecordAging
Sample usage
dnscmd dnssvr1.contoso.com /clearcache