b0d27692de
Firstly, my understanding of "adns" is that it's short for authoritative-dns; i.e. things related to our main non-recursive DNS servers for the zones we manage. The "a" is useful to distinguish this from any sort of other dns services we might run for CI, etc. The way we do this is with a "hidden" server that applies updates from config management, which then notifies secondary public servers which do a zone transfer from the primary. They're all "authoritative" in the sense they're not for general recursive queries. As mentioned in Ibd8063e92ad7ff9ee683dcc7dfcc115a0b19dcaa, we currently have 3 groups adns : the hidden primary bind server ns : the secondary public authoratitive servers dns : both of the above This proposes a refactor into the following 3 groups adns-primary : hidden primary bind server adns-secondary : the secondary public authoritative servers adns : both of the above This is meant to be a no-op; I just feel like this makes it a bit clearer as to the "lay of the land" with these servers. It will need some considering of the hiera variables on bridge if we merge. Change-Id: I9ffef52f27bd23ceeec07fe0f45f9fee08b5559a
13 lines
280 B
YAML
13 lines
280 B
YAML
- hosts: adns-primary:!disabled
|
|
name: "Base: configure primary authoritative nameserver"
|
|
roles:
|
|
- iptables
|
|
- master-nameserver
|
|
|
|
- hosts: "adns-secondary:!disabled"
|
|
name: "Base: configure secondary authoritative nameservers"
|
|
roles:
|
|
- iptables
|
|
- nameserver
|
|
|