The first question is what server OS? The second question is do you really need a ". I've seen this configuration required for isolating networks or where a proxy server is in use for internet access. A DNS server first queries its cache, it checks its zone records, it sends requests to forwarders, and then it tries resolution by using root servers. When you use the Dcpromo tool to promote a server to a domain controller, the domain controller requires DNS.
If you install DNS during the promotion process, a root zone is created. This root zone indicates to your DNS server that it is a root Internet server. Therefore, your DNS server does not use forwarders or root hints in the name-resolution process.
To continue this discussion, please ask a new question. See ASP. I will try what you suggested. Net directly from the Microsoft Event Viewer! Net FAQ Advertise with us Articles Managing logsRecommended We tried removing the reverse zones from all servers but when one of all reboot the zones magically re-appear. From Active Directory. If the zone and its contents appear normal and you are able to create and delete a test record within it, the error is still likely not indicative of a serious Dns Event Id Server Dell shall not be liable for any loss, including but not limited to loss of data, loss of profit or loss of revenue, which customers may incur by following any procedure From accounting app support through to highly available solutions for accounting firms we've got it covered.
Terms of Use Trademarks Privacy Statement 5. While replicating a colleague of mine created the reversezones, because he thought it was not replicating. From that moment on we have this event. We tried removing the reverse zones from all servers but when one of all reboot the zones magically re-appear. I looked there for one that was corrupted and with little records in it and decided to delete it.
I restarted the DNS server and that zone did not appear anymore in the DNS server and also did not cause any eventlog messages. All corrupt DNS zones where gone and my eventlog now looks just fine. I did not apply the hotfix from the article though. It seems when re starting a DNS-server the information in that container is used as configuration and the life data was appended to it. I have been looking at the link you have sent me.
I saw in there that events from to should be logged but they do. This DNS server is configured to obtain and use information from the directory for this zone and is unable to load the zone without it. Check that the Active Directory is functioning properly and reload the zone. The event data is the error code. And while running event The DNS server received indication that zone xx. The zones that we try to remove are "broken" in some way.
We can't use them when we delete them they reappear after DNS service restart. We are now migrating to windows , which tries to delete the zones by itself but the events keep apearing. Our reverse lookup functionality is nog working properly because not all zones are there.
We have 1 tree and 1 domain with standard replication in one site. We are wondering if it is possible to remove these zones from the AD database so they won't reappear.
0コメント