...
When running DHCP servers, the following keys are needed:
Key | Description | Data-type | Used by: |
---|---|---|---|
profile::dhcp::omapi::key | The omapi key used to update the DHCP servers | String | |
profile::dhcp::omapi::name | The omapi key name | String | |
profile::dhcp::searchdomain | The default search-domain handed to DHCP clients | String | |
profile::dns::resolvers | The DNS resolvers for clients to use | List |
profile::dhcp::omapi::key: '<omapi-key>'
profile::dhcp::omapi::name: '<omapi-key-name>'
profile::dhcp::searchdomain: '<default-search-domain>'
- profile::dns::resolvers:
- '<IP-of-DNS-resolver 1>'
- '<IP-of-DNS-resolver 2>'
DNS server
If you are hosting a DNS server the following keys are needed:
profile::dns::forwarders:
- '129.241.0.200'
- '129.241.0.201'
profile::dns::key::transfer: 'UvetjoX5zMiw/NbQr3biug=='
profile::dns::key::update: 'RIrdwoP3xyCgbKuQb7E8iQ=='
profile::dns::ns1::ipv4: '192.168.254.11'
profile::dns::ns1::query::ipv4: '192.168.254.81'
profile::dns::ns1::name: 'ns1.sky.rothaugane.com'
profile::dns::ns1::key: "%{hiera('profile::dns::key::update')}"
profile::dns::resolvers:
- '192.168.254.11'
- '192.168.254.4'
profile::dns::slaves:
'ns2.sky.rothaugane.com': '192.168.254.80'
profile::dns::zones:
'sky.rothaugane.com': 'ns1'
'management.sky.rothaugane.com': 'ns1'
'services.sky.rothaugane.com': 'ns1'
'254.168.192.in-addr.arpa': 'ns1'
'255.168.192.in-addr.arpa': 'ns1'
Dashboard
The general configuration of the dashboard are based on the following keys:
...