Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to www.eventid.net. The EventId.Net for Splunk Add-on assumes that Splunk is collecting information from Windows servers and workstation via the Splunk Universal Forwarder.
Zone transfer request for secondary zone <zone name> refused by master server at <ip address>. Check the zone at the master server <ip address> to verify that zone transfer is enabled to this server. To do so, use the DNS console, and select master server <ip address> as the applicable server, then in secondary zone <domain> Properties, view the settings on the Zone Transfers tab. Based on the settings you choose, make any configuration adjustments there (or possibly in the Name Servers tab) so that a zone transfer can be made to this server.
|English: Request a translation of the event description in plain English.|
|Concepts to understand:|
What is the role of a DNS server?
See ME915022 for information about this event.
I have found on Windows 2000 Server that the secondary server is not allowed to update because of the secondary serverís IP number order on the NIC card, if multiple IP numbers are assigned. If the Primary zone is set to allow zone transfers "To any server", the IP order on the secondary servers does not affect zone transfers.
As per Microsoft: "The zone transfer request initiated by the master DNS server was refused by the primary server". See MSW2KDB for details on this issue.
This may occur due to the DNS zone transfer throttling mechanism. See ME291016 for more details.
|Private comment: Subscribers only. See example of private comment|
|Links: ME291016, ME915022, MSW2KDB|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated