Event Message:

DNS server secondary zone name , had no master IP addresses in registry. Secondary zones require masters.

Source

Event Log

Event ID

Event Type

DNS

System

133

Error

Explanation:

When defining secondary zones, an IP address must be configured for the master server from which the zone information is obtained during startup or when the refresh interval times out in the SOA record.

User Action:

Verify that the master IP address of the secondary zone has been defined on the server: 1. In DNS Manager, right-click the specified secondary zone file, then click Properties. 2. Verify that the primary server IP address is defined in the IP Masters address list. If the primary server IP address is missing, add it to the list. 3. If the IP address is defined, delete it and then add it back to the IP Masters address list. 4. Click OK. 5. Click DNS on the menu bar and click Update Server Data Files. Check the Registry to verify that the primary server IP address has been added to the zone directory: 1. Click Start, and then click Run. 2. In the Open box, type regedit and press ENTER. 3. Open the \HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\DNS\Zones subkey. 4. Click the specified zone name in the left pane, and click Delete. 5. Click the secondary zone file specified in the error message. 6. Verify that the MasterServers value has an IP address assigned to it. This value is in hexadecimal format. For example: 01 00 00 00 9d 39 79 57.You can convert the last four sets of numbers in the hexadecimal value to a decimal value to obtain the IP address entered in the IP Masters list.