| Event Id | 6527 |
| Source | Microsoft-Windows-DNS-Server-Service |
| Description | Zone %1 expired before it could obtain a successful zone transfer or update from a master server acting as its source for the zone. The zone has been shut down |
| Event Information | According to Microsoft : Cause : This event is logged when Zone expired before it could obtain a successful zone transfer or update from a master server acting as its source for the zone. Resolution : Correct master server problems The master-server configuration for a secondary zone is not correct, which is preventing the zone from being transferred from the master server. To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority. To correct problems with zone transfers from a master server: 1.On the DNS server, start Server Manager. To start Server Manager, click Start, click Administrative Tools, and then click Server Manager. 2.In the console tree, double-click Roles, double-click DNS Server, and then double-click DNS. 3.Expand the DNS server, and then expand the folder that contains the affected zone. 4.Right-click the zone, and then click Properties. 5.On the General tab, confirm that the list contains the correct IP addresses and fully qualified domain names (FQDNs) of the master servers of the zone. If the list is correct, ensure that the listed master servers are functioning properly. Ensure that zone transfers are allowed on the master server and that, if zone transfers are restricted by IP address, this server is included in the list. If not, correct the problem, and then restart the zone transfer. To confirm that the local server is included in the list of servers that can receive zone transfers: 1.On the DNS server, start DNS Manager. To start DNS Manager, on a DNS server, click Start, click Administrative Tools, and then click DNS. 2.Connect to the master server. To connect to a DNS server, right-click DNS, click Connect to DNS Server, click The following computer, type the DNS name or IP address of the remote DNS server, and then click OK. 2.Expand the server, and then expand the folder that contains the zone. 4.Right-click the zone, click Properties, and then click Zone Transfers. 5.If it is not already selected, click Allow zone transfers. 6.Do one of the following: If Only to servers listed on the Name Servers tab is selected, click Name Servers, and confirm that the server that hosts the secondary zone is listed with the correct IP address in the Name servers list. If Only to the following servers is selected, confirm that the server that hosts the secondary zone is listed with the correct IP address in the list. To restart a zone transfer: 1.In Server Manager or DNS Manager, expand DNS, expand the server that hosts the secondary zone, and then expand the folder that contains the zone. 2.Right-click the zone, and then click Reload from master. Verify To verify that the Domain Name System (DNS) configuration is correct, verify that all configuration settings are correct, check the event log for events that indicate continuing problems, and then verify that DNS client computers are able to resolve names properly. To verify DNS configuration settings: 1.On the DNS server, start Server Manager. To start Server Manager, click Start, click Administrative Tools, and then click Server Manager. 2.In the console tree, double-click Roles, double-click DNS Server, and then double-click DNS. 3.Right-click the DNS server, and then click Properties. 4.Review the settings on each tab, and verify that they contain the intended values. 5.Expand the DNS server. 6.Expand a zone folder, right-click a zone, and then click Properties. 7.Review the settings on each tab, and verify that they contain the intended values. 8.Repeat steps 6 and 7 for each zone. To verify that DNS client computers can resolve names properly: 1.On a DNS client computer, open a command prompt. To open a command prompt, click Start, click Run, type cmd, and then click OK. 2. At the command prompt, type pinghostname (where hostname is the DNS name of a computer with a known IP address), and then press ENTER. If the client can resolve the name, the ping command responds with the following message: Pinging hostname [ip_address] Note: The name resolution is successful even if the ping command reports that the destination is unreachable. If the client cannot resolve the name, the ping command responds with the following message: Ping request could not find host hostname |
| Reference Links | Event ID 6527 from Microsoft-Windows-DNS-Server-Service |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.