Dustin C. Hatch
1c575c4340
Since DNS only allowed to be sent over the VPN, it is not possible to resolve the VPN server name unless the VPN is already connected. This naturally creates a chicken-and-egg scenario, which we can resolve by manually providing the IP address of the server we want to connect to.
72 lines
1.3 KiB
YAML
72 lines
1.3 KiB
YAML
protonvpn_tunnel: 1.1.1.1,1.0.0.1
|
|
protonvpn_server: 104.200.145.225
|
|
named_forward_only: true
|
|
named_forwarders:
|
|
- 1.1.1.1
|
|
- 1.0.0.1
|
|
named_listen:
|
|
- addresses:
|
|
- any
|
|
named_listen_v6:
|
|
- addresses:
|
|
- any
|
|
named_allow_query:
|
|
- any
|
|
named_dnssec_validation: false
|
|
named_response_policy:
|
|
- zone "blackhole.rpz"
|
|
named_queries_syslog: true
|
|
named_rpz_syslog: true
|
|
|
|
pyrocufflink_common_zones:
|
|
- zone: pyrocufflink.blue
|
|
type: forward
|
|
forward: only
|
|
forwarders:
|
|
- 172.30.0.10
|
|
- 172.30.0.9
|
|
- zone: 0.30.172.in-addr.arpa
|
|
type: forward
|
|
forward: only
|
|
forwarders:
|
|
- 172.30.0.10
|
|
- 172.30.0.9
|
|
- zone: securepassage.com
|
|
type: forward
|
|
forward: only
|
|
forwarders:
|
|
- 192.168.20.146
|
|
- 192.168.20.147
|
|
- zone: lab.firemon.com
|
|
type: forward
|
|
forward: only
|
|
forwarders:
|
|
- 192.168.20.146
|
|
- 192.168.20.147
|
|
- zone: fmos.test
|
|
type: forward
|
|
forward: only
|
|
forwarders:
|
|
- 192.168.20.146
|
|
- 192.168.20.147
|
|
- zone: 168.192.in-addr.arpa
|
|
type: forward
|
|
forward: only
|
|
forwarders:
|
|
- 192.168.20.146
|
|
- 192.168.20.147
|
|
- zone: 4.16.172.in-addr.arpa
|
|
type: forward
|
|
forward: only
|
|
forwarders:
|
|
- 192.168.20.146
|
|
- 192.168.20.147
|
|
- zone: 5.16.172.in-addr.arpa
|
|
type: forward
|
|
forward: only
|
|
forwarders:
|
|
- 192.168.20.146
|
|
- 192.168.20.147
|
|
|
|
named_zones: '{{ pyrocufflink_red_zones + pyrocufflink_common_zones + rpz_zones }}'
|