| Event Id | 503 |
| Source | Microsoft-Windows-DNS-Server-Service |
| Description | The DNS server has detected that the secondary zone %1 has no master IP addresses in registry data. Secondary zones require at least one master server to act as a source. You can add or update the IP address for the master server for this zone using the DNS console. |
| Event Information | According to Microsoft : Cause : This event is logged when DNS server has detected that the secondary zone has no master IP addresses in registry data. Resolution : Update the master server A secondary zone must be configured with the IP addresses of one or more master servers that host the primary zone. To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority. To update the master server for a secondary zone: 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 containing the applicable secondary zone. 4.Right-click the secondary zone, and then click Properties. 5.On the General tab, click Edit. 6.In the Edit Master Servers dialog box, click the IP addresses of master servers list, type the name or IP address of a master server, and then click the list again. 7.Click OK to close the dialog box, and then click OK to close 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 503 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.