Skip to content

Several zones

One process can serve several apexes. Add a zones mapping instead of the top-level keys; the lot 1 shape stays valid for one zone.

health: {interval: 5, timeout: 2, fail_threshold: 2, success_threshold: 1}
zones:
  app.example.com.:
    ttl: 30
    default_pool: site_paris
    pools: {site_paris: [...]}
    network_rules: [{cidr: 10.10.0.0/16, pool: site_paris}]
  api.example.com.:
    ttl: 60
    default_pool: api
    pools: {api: [...]}
    network_rules: []
  • A query goes to the zone whose apex is the longest suffix of its name: sub.app.example.com. belongs to the app.example.com. zone.
  • Pools, routing rules and counters are isolated per zone. The same pool name may exist in two zones without merging; the console labels them apex/pool as soon as more than one zone is served.
  • health is process-wide: one probe loop per zone, one interval.
  • SOA and _whoami are per zone.
  • A single-zone file still produces the exact lot 2 snapshot vocabulary, so an existing deployment sees no change.
  • A name outside every zone is REFUSED, and counted against the first zone's denominator.

There is no zone transfer (AXFR/IXFR): the content of a zone is computed from the configuration and the live health of the backends, so there is nothing to replicate. Each instance answers from its own view, which is what a GSLB is for.

examples/multizone.yaml is a complete two-zone example.