¿Cuáles son las diferencias y similitudes entre las zonas de código auxiliar y los reenviadores condicionales en Active Directory?

A stub zone is a small DNS zone that contains only the name server (NS) records and related info of another domain. It helps your DNS server know where to find authoritative answers without storing full DNS data. Think of it as a mini phonebook listing just the "operators" of a domain. Stub zones automatically update and are useful in trusted environments where DNS infrastructure may change. Your DNS uses the stub to directly contact the right server and fetch answers itself. They're great for internal networks or linked Active Directory domains where dynamic updates and consistent name resolution are important.

A conditional forwarder is a rule telling your DNS server to forward queries for a specific domain to a defined DNS server. It stores no zone data; it just knows who to ask when certain domain names are requested. It works like a hotline, your DNS forwards the question and waits for the answer. If the partner's DNS server IP changes, you must update the rule manually. This approach is ideal for external organisations or stable DNS setups where minimal exposure and simple configuration are priorities.

Both stub zones and conditional forwarders help resolve names in other domains efficiently. They avoid public lookups and direct DNS queries to the appropriate server, improving speed and security. They are used to build links between DNS namespaces, often within organisations or between trusted partners, and both can be stored in Active Directory. Their goal is the same: get accurate name resolution from another DNS source with minimal delay or misrouting.

Stub zones store a small portion of the other domain's DNS info and auto-refresh, while conditional forwarders rely on fixed IPs and need manual updates. Stub zones let your DNS server resolve queries directly; conditional forwarders pass queries to another server. One is dynamic, the other static.

Use stub zones in internal networks or where DNS servers change often. They auto-update and suit AD forests and trusted domains well. Conditional forwarders work best for external domains or stable environments where you control which server gets the query. If you need automated updates, use stub zones. If you prefer simplicity and minimal exposure, use conditional forwarders.

Qui dit zone stub, dit requête itérative. Qui dit redirection conditionnelle, dit requête récursive. Dans le premier cas, des ouvertures de flux supplémentaires peuvent s'avérer nécessaires entre le serveur DNS source et le serveur DNS hébergeant la zone. Dans le deuxième cas, l'ouverture est nécessaire entre le redirecteur (l'IP cible configurée sur le serveur DNS source) et le serveur DNS hébergeant la zone.

Make sure your DNS servers have proper network access to the target servers stub zones need connectivity for updates, and forwarders must reach the server to get answers. Stub zones may expose limited DNS details (like name server names), so evaluate privacy needs. Conditional forwarders avoid this but require manual updates if server IPs change. In hybrid or multi-forest environments, balancing automation (stub zones) and control (forwarders) is key. Choose based on trust, frequency of change, and admin effort.