How to establish trust between two Active Directory forests and provide cross-domain file access
Cross-domain file access requires routed connectivity, conditional DNS forwarding, time synchronization, validated trust, cross-domain groups, share permissions, and NTFS ACLs.

Establish a factual baseline with “bidirectional DNS conditional forwarding” and “inter-domain time synchronization”, then move to “trust direction and validation”. Use effective access, credentials and real file operations as the evidence chain and avoid changing production before the fault boundary is clear.
Risk boundaries and prerequisites
Start by checking bidirectional DNS conditional forwarding, inter-domain time synchronization and trust direction and validation 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 · bidirectional DNS conditional forwarding | Checking bidirectional DNS conditional forwarding 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 bidirectional DNS conditional forwarding. Capture read-only results from the affected controllers and clients. Compare objects, DNS records, policy versions and events before making changes. |
| 02 · inter-domain time synchronization | Checking inter-domain time synchronization 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 inter-domain time synchronization. Capture read-only results from the affected controllers and clients. Compare objects, DNS records, policy versions and events before making changes. |
| 03 · trust direction and validation | Checking trust direction and validation 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 trust direction and validation. Capture read-only results from the affected controllers and clients. Compare objects, DNS records, policy versions and events before making changes. |
| 04 · cross-domain security-group strategy | Checking cross-domain security-group strategy 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 cross-domain security-group strategy. Capture read-only results from the affected controllers and clients. Compare objects, DNS records, policy versions and events before making changes. |
| 05 · effective share/NTFS permissions | Checking effective share/NTFS permissions 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 effective share/NTFS permissions. Capture read-only results from the affected controllers and clients. Compare objects, DNS records, policy versions and events before making changes. |
| 06 · SPN/Kerberos and firewall ports | Checking SPN/Kerberos and firewall ports 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 SPN/Kerberos and firewall ports. 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 bidirectional DNS conditional forwarding and inter-domain time synchronization and compare it with a known-good system.
- Correlate evidence from trust direction and validation and cross-domain security-group strategy to distinguish the direct fault from dependent symptoms.
- Only if evidence points to effective share/NTFS permissions, plan a controlled change with backups, a change window and rollback triggers.
- Finally check SPN/Kerberos and firewall ports 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 effective share/NTFS permissions and SPN/Kerberos and firewall ports against the expected business outcome.
- Retain initial configuration, event evidence, validation results and rollback triggers for production changes.
Common actions that increase risk
- Assuming bidirectional DNS conditional forwarding is sufficient while overlooking inter-domain time synchronization and dependent checks.
- Changing several settings before preserving the original evidence for trust direction and validation.
- 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 bidirectional DNS conditional forwarding and inter-domain time synchronization. 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.
