| Event Id | 708 |
| Source | DNS |
| Description | The DNS server has no primary or secondary zones. The DNS server will run as a caching-only server, but will not be authoritative for any zones. |
| Event Information | According to Microsoft: Although all DNS servers cache queries that they have resolved, caching-only servers are DNS servers that only perform queries, cache the answers, and return the results. They are not authoritative for any domains and the information that they contain is limited to what has been cached while resolving queries. In determining when to use this kind of server, note that when this server is initially started, it has no cached information. This information is obtained over time as client requests are serviced. However, if you are dealing with a slow-speed WAN link between sites, this option might be ideal because, once the cache is built, traffic decreases. In addition, the caching-only server does not perform zone transfers, which can also be network intensive in WAN environments. 1. To install a caching-only DNS server, install a DNS server on the server computer. 2. Do not configure the DNS server (as you might normally) to load any zones. 3. Verify server root hints are configured or updated correctly. To perform this procedure, you must be a member of the Administrators group on the local computer, or you must have been delegated the appropriate authority. If the computer is joined to a domain, members of the Domain Admins group might be able to perform this procedure. As a security best practice, consider using Run as to perform this procedure. Caching-only DNS servers do not host any zones and are not authoritative for a particular domain. They are DNS servers that build a local server cache of names learned while performing recursive queries on behalf of their clients. This information is then available from its cache when answering subsequent client queries. A caching-only DNS server can be valuable at a site where DNS functionality is needed locally but it is not administratively desirable to create a separate domain or zone for that location. It is strongly recommended that, when operating the computer as a DNS serv |
| Reference Links | DNS Event IDs 1 Through 1657 for Windows NT 4.0 SP4 A MicrosoftDNS container is created before full replication and causes a DNS conflict in Windows Server 2003 |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.