It is possible that the delegation was done correctly, but that the primary DNS for the subzone, has any incorrect NS record pointing back at this server. For more information about this behavior, see "Event ID 7062 logs even when zone transfers are disabled" in the More Information section.MORE INFORMATIONHow to find the actual requested domainsTo find the The… Storage Software Disaster Recovery Windows Server 2008 Advertise Here 804 members asked questions and received personalized solutions in the past 7 days. English: This information is only available to subscribers.
Thoughts ? 0Votes Share Flag Collapse - Your problem is the missing forwarders. Users can access the server resources, as well as external websites, but in order to access external sites, I had to configure external DNS along with internal server DNS on each All clients can access server resources as well as internet at all times. (as far as I know). to no avail: -remove dns in configure your server -remove dns folder from system32 -in system32\config remove netlogon.dnb and netlogon.dns reinstall dns (configure your server) with the correct zone name then
For additional information about replacing the existing root hints with the default root hints, click the following article number to view the article in the Microsoft Knowledge Base: 249868 (http://support.microsoft.com/kb/249868/) Replacing Dns Forwarders According to a newsgroup post: "After many hours of research and scouring of newsgroups I finally have fixed my DNS packets being sent to itself. Additionally, the root DNS servers delegate the namespace under those domains to other DNS servers. I believe that most of the users affected by 7062 (and still unable to resolve it) simply reserved domain names for the future use and never added them to the DNS
but would it not be easier and less time consuming to simply(or so it would seem) remove the DNS component properly, then reinstall it ?Keith 0Votes Share Flag Collapse - It Join & Ask a Question Need Help in Real-Time? Event Id 7062 Windows Server 2008 R2 x 32 EventID.Net As per Microsoft: "This error is caused by a configuration error or is the result of a delegation of a domain (or subdomain) to a server for which Event Id 7062 Dns Windows 2003 If your DNS is listed in your name servers, the Notify function by default will send to all that are listed.
You can use the DNS server debug logging facility to track down the cause of this problem. 0 Question by:Hubman Facebook Twitter LinkedIn Google LVL 24 Active today Best Solution bysmckeown777 Click the Forwarders tab. 3. x 36 Anonymous I got this error when I changed the root hints so that Server A pointed to itself and Server B pointed to server A. by Peconet Tietokoneet-217038187993258194678069903632 · 8 years ago In reply to Easier to remove/reinstal ...
You should not register the outside NIC on the DNS record. Join Now Server keeps logging this event very frequently, thus filling up event log. what you have tried.
The client computer sends a query for www.example.org to the root servers. Event ID 7062 — DNS Server Message Processing Updated: November 25, 2009Applies To: Windows Server 2008 R2 These events represent problems processing data received by the DNS server that may or may The packet will be discarded. Must not contain NS record for DNS server.As part of your troubleshooting, you may find that none of the steps that are listed in event ID 7062 apply to your DNS
Especially the removal. 0Votes Share Flag Collapse - updates... Neither did any new group suggestions. Custom search for *****: Google - Bing - Microsoft - Yahoo Feedback: Send comments or solutions - Notify me when updated Printer friendly Subscribe Subscribe to EventID.Net now!Already a subscriber? Menu Articles Products Forums Forums Quick Links Search Forums Recent Posts Recent Posts Vendors Resources Resources Quick Links Search Resources Most Active Authors Members Members Quick Links Notable Members Current Visitors
This situation usually indicates a configuration error. My servers have addresses of 192.168.1.2 and 192.168.1.3. However, the root DNS servers maintain the .com, .net, and other domains. Therefore it sent itself a packet.
Of course the event viewer says check lame delegation, etc.None of those solutions fixed the problem in my case. When I remove/reinstall, the same settings are present. Install Backup Exec 2012 on the new server and apply all of the latest hotfixes and service packs. From a newsgroup post: "Since the installation of NT SP4, many of us started getting DNS Error 7062.
Else check your forwarders (long shot but good to check). 0 This discussion has been inactive for over a year.