1.Windows Server--DNS aging time and cleanup

DNS Summary of issues:

• Problem Description: There are two identical records in the DNS server. one of the dates is older and has been kept in DNS .

• Problem Analysis: Preliminary judgment is due to DNS does not have an aging mechanism enabled so that old records persist.

• < Span style= "font-family: ' The song Body '; > problem diagnosis: Delete the same record, Dns aging and cleanup; set dns 1 1 hour , 1 hour , 1 hour. After one hours, the old record is automatically cleared;

Reference: https://technet.microsoft.com/zh-cn/library/cc771362.aspx

• the impact of: because the old records were removed, the member server could not be connected, because in There are no records found in DNS. Impact on the use of the entire network, resulting in a large area of the drop line;

• workaround: Because the destination server cannot be connected by hostname;

1. through IP address, set up a task schedule on each host;

2. first delete the task schedule with the same name on each host, and then set up a task schedule with the same name;

3. You must obtain the administrator password for each host, use this task schedule to set the specific time for execution, and at every 2 minutes to Dns register in DNS

   &NBSP;

• Summary: Before making every seemingly simple change, it is best to have a backup, and to get the customer's consent to carry out related operations, do not do other more operations, only solve customer problems, especially in the production environment to be extra careful, and in the case of the certainty of resolving unexpected problems, make relevant changes. Better understand the purpose of this change, impact, etc.;

This article comes from the "Ricky's blog" blog, please be sure to keep this source http://57388.blog.51cto.com/47388/1639499

1.Windows Server--DNS aging time and cleanup