Forward zone, stub zone, or delegation?

From Brandonhutchinson.com

(Difference between revisions)
Jump to: navigation, search
(New page: == Forward zones == * When a forward zone is configured, BIND sends a recursive query to the forwarders and waits for an answer. If the forwarder does not allow recursion, and it is neede...)
Current revision (23:12, 18 August 2008) (edit) (undo)
 
Line 9: Line 9:
* With a stub zone, the BIND server "performs the work" when resolving the query.
* With a stub zone, the BIND server "performs the work" when resolving the query.
* BIND uses both UDP 53 and TCP 53 when populating a stub zone, even if the master name server allows [http://en.wikipedia.org/wiki/EDNS EDNS]. BIND uses UDP 53 when querying the SOA record for the zone, and TCP 53 when transferring the NS records and A glue records. I find this surprising as IXFR and AXFR aren't involved.
* BIND uses both UDP 53 and TCP 53 when populating a stub zone, even if the master name server allows [http://en.wikipedia.org/wiki/EDNS EDNS]. BIND uses UDP 53 when querying the SOA record for the zone, and TCP 53 when transferring the NS records and A glue records. I find this surprising as IXFR and AXFR aren't involved.
 +
* BIND will check the stub server(s) at the SOA REFRESH interval for any changes to the SOA, NS, and A glue records.
== Links ==
== Links ==
* [http://groups.google.com/group/comp.protocols.tcp-ip.domains/browse_thread/thread/cd985c5cddeb6ac6 Zone "type forward" vs. sub-domain delegation.]
* [http://groups.google.com/group/comp.protocols.tcp-ip.domains/browse_thread/thread/cd985c5cddeb6ac6 Zone "type forward" vs. sub-domain delegation.]

Current revision

Forward zones

  • When a forward zone is configured, BIND sends a recursive query to the forwarders and waits for an answer. If the forwarder does not allow recursion, and it is needed to resolve the query, the query will fail.
  • With a forward zone, the forwarder "performs the work" when resolving the query.

Stub zones

  • When a stub zone is used, BIND sends an iterative (non-recursive) query to one of the name servers in the stub zone. BIND will continue to send iterative queries to resolve the query.
  • With a stub zone, the BIND server "performs the work" when resolving the query.
  • BIND uses both UDP 53 and TCP 53 when populating a stub zone, even if the master name server allows EDNS. BIND uses UDP 53 when querying the SOA record for the zone, and TCP 53 when transferring the NS records and A glue records. I find this surprising as IXFR and AXFR aren't involved.
  • BIND will check the stub server(s) at the SOA REFRESH interval for any changes to the SOA, NS, and A glue records.

Links

Personal tools