-
-
Notifications
You must be signed in to change notification settings - Fork 4
Expand file tree
/
Copy pathcaptive-dns.env.example
More file actions
68 lines (54 loc) · 2.91 KB
/
captive-dns.env.example
File metadata and controls
68 lines (54 loc) · 2.91 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
# CIDR range for the Primary and Secondary DNS host(s)
# This is an array, set each allowed destination as its own element
allowedDNS=("10.10.10.0/24")
# Primary DNS server IP address
primaryDNS="10.10.10.10"
# Secondary DNS server IP address
# If you do not have a secondary DNS server, you can leave this blank
secondaryDNS="10.10.10.11"
# Tertiary DNS resolver to use if both Primary/Secondary DNS providers are down
# This should probably be something outside your network
tertiaryDNS="1.1.1.1"
# The port that should be used for DNS lookups, should be default (53) in almost all scenarios
dnsPort="53"
# Domain you want to look up to test if captive DNS is working or not
testDomain="cloudfare.com"
# List of VLAN's you want to force to use captive DNS
# Your default vlan0 is "br0", vlan2 is "br2", vlan1010 is "br1010", etc.
# This is an array, set each desired VLAN as its own element
vlanInterfaces=("br0" "br2" "br3" "br4" "br5" "br99")
# Are we allowed to check for and notify of updates each time the script runs?
# Can be "Yes" "No" "True" "False"
updateCheck="Yes"
# How verbose should our output be?
# Possible values:
# 1 - Error only
# 2 - Informational
# 3 - Verbose
outputVerbosity="2"
## Optional
# If you want to send a Telegram message notifying of DNS updates, fill these out.
# Telegram bot API key, obtained from @BotFather
telegramBotId=""
# Telegram channel ID, if you don't know how to get this, use these instructions:
# https://gist.github.com/goose-ws/1c82c98ac4701af433eb5c7562109e51
# This is an array, so you can do multiple channels if you want.
# Format is: ("-100xxxxxxx2" "-100xxxxxxx1")
# Modifiers include threads for super groups, and silent notifications.
# If sending to a super group thread, you can specify the thread by adding '&message_thread_id=[int]',
# where [int] is the interger of the thread ID. (e.g. "-100xxxxxxxxx1&message_thread_id=12")
# For silent notifications, you can add the modifier '&silent=true' (e.g. "-100xxxxxxxxx1&silent=true")
telegramChannelId=("")
# IP address of Telegram API server, in case the hostname cannot be resolved.
# You can find this with the command: dig +short -q a api.telegram.org
# If you really don't want to use an IP address, you can set it to "api.telegram.org"
telegramAddr="149.154.167.220"
# Do you want to send a Telegram message for script errors? Beware, the script is not capable of checking
# to see if an error message has already been sent, so depending on your cron settings this could become
# very spammy. Can be "Yes" "No" "True" "False"
telegramErrorMessages="No"
# If you enabled Telegram messages for script errors, you can define a different channel for errors to
# be sent to, instead of the ones defined in the 'telegramChannelId' array above. This can only be a single
# channel, not an array. If you leave this blank, and have error messages enabled, then they will send to
# all channels in the 'telegramChannelId' array above.
telegramErrorChannel=""