With two enterprise DNS servers, must forwarders, cache and root hints be identical?
AD-integrated zones can replicate, but conditional forwarders, server forwarders, root hints, cache and firewall paths still require separate verification.

Establish a factual baseline with “AD-integrated zone replication” and “AD storage of conditional forwarders”, then move to “server-level forwarder differences”. Use identity, name resolution, replication and policy as the evidence chain and avoid changing production before the fault boundary is clear.
Risk boundaries and prerequisites
Start by checking AD-integrated zone replication, AD storage of conditional forwarders and server-level forwarder differences independently. A healthy result for one of these checks does not establish the state of the entire service path.
Evidence and safe checks
| Check | Why it matters | Recommended action |
|---|---|---|
| 01 · AD-integrated zone replication | Checking AD-integrated zone replication helps establish whether the directory, name resolution and policy state are consistent; compare it with a known-good baseline and the incident timeline. | Record the actual state of AD-integrated zone replication. Capture read-only results from the affected controllers and clients. Compare objects, DNS records, policy versions and events before making changes. |
| 02 · AD storage of conditional forwarders | Checking AD storage of conditional forwarders helps establish whether the directory, name resolution and policy state are consistent; compare it with a known-good baseline and the incident timeline. | Record the actual state of AD storage of conditional forwarders. Capture read-only results from the affected controllers and clients. Compare objects, DNS records, policy versions and events before making changes. |
| 03 · server-level forwarder differences | Checking server-level forwarder differences helps establish whether the directory, name resolution and policy state are consistent; compare it with a known-good baseline and the incident timeline. | Record the actual state of server-level forwarder differences. Capture read-only results from the affected controllers and clients. Compare objects, DNS records, policy versions and events before making changes. |
| 04 · root hints and recursion policy | Checking root hints and recursion policy helps establish whether the directory, name resolution and policy state are consistent; compare it with a known-good baseline and the incident timeline. | Record the actual state of root hints and recursion policy. Capture read-only results from the affected controllers and clients. Compare objects, DNS records, policy versions and events before making changes. |
| 05 · TCP/UDP 53 egress path | Checking TCP/UDP 53 egress path helps establish whether the directory, name resolution and policy state are consistent; compare it with a known-good baseline and the incident timeline. | Record the actual state of TCP/UDP 53 egress path. Capture read-only results from the affected controllers and clients. Compare objects, DNS records, policy versions and events before making changes. |
| 06 · cache and failover verification | Checking cache and failover verification helps establish whether the directory, name resolution and policy state are consistent; compare it with a known-good baseline and the incident timeline. | Record the actual state of cache and failover verification. Capture read-only results from the affected controllers and clients. Compare objects, DNS records, policy versions and events before making changes. |
Investigation and change sequence
- Capture a baseline for AD-integrated zone replication and AD storage of conditional forwarders and compare it with a known-good system.
- Correlate evidence from server-level forwarder differences and root hints and recursion policy to distinguish the direct fault from dependent symptoms.
- Only if evidence points to TCP/UDP 53 egress path, plan a controlled change with backups, a change window and rollback triggers.
- Finally check cache and failover verification and the real business workflow. Retest representative user sign-in, domain discovery, Group Policy or cross-domain access and confirm replication and event health.
Validation and rollback evidence
- Retest representative user sign-in, domain discovery, Group Policy or cross-domain access and confirm replication and event health.
- Recheck TCP/UDP 53 egress path and cache and failover verification against the expected business outcome.
- Retain initial configuration, event evidence, validation results and rollback triggers for production changes.
Common actions that increase risk
- Assuming AD-integrated zone replication is sufficient while overlooking AD storage of conditional forwarders and dependent checks.
- Changing several settings before preserving the original evidence for server-level forwarder differences.
- Do not replace root-cause analysis with destructive directory operations or forced rebuilds.
Common questions and acceptance criteria
What should be checked first?
Begin with AD-integrated zone replication and AD storage of conditional forwarders. Capture reproducible errors and protect recoverable data before changing production.
What proves the issue is resolved?
Retest representative user sign-in, domain discovery, Group Policy or cross-domain access and confirm replication and event health.
What evidence should be retained?
Retain original logs, configuration snapshots, the approved change scope, business verification and rollback conditions.
