0e5789820201ef73fd1015fb17c8ae448755b35f
[web.git] / docs / uci_dnsmasq.txt
1 DNS and DHCP configuration
2 ==========================
3
4 The _dnsmasq_ and dhcpd configuration is located in '/etc/config/dhcp' and controls both DNS and DHCP server options on the device.
5
6 In the default configuration this file contains one _common section_ to specify DNS and daemon related options and one or more _DHCP pools_ to define DHCP ranges serving on network interfaces.
7
8 == Sections
9
10 Possible section types of the 'dhcp' configuration file are defined below. Not all types may appear in the file and most of them are only needed for special configurations. The common ones are the _Common Options_, the _DHCP Pools_ and _Static Leases_.
11
12 === Common Options
13
14 The config section type 'dnsmasq' determines values and options relevant to the overall operation of dnsmasq and the DHCP options on all interfaces served. The following table lists all available options, their default value, as well as the corresponding _dnsmasq_ command line option. See link:http://www.thekelleys.org.uk/dnsmasq/docs/dnsmasq-man.html[the dnsmasq man page] for further details.
15
16 These are the default settings for the common options:
17
18 ----
19 config 'dnsmasq'
20 option domainneeded 1
21 option boguspriv 1
22 option filterwin2k 0
23 option localise_queries 1
24 option rebind_protection 1
25 option rebind_localhost 0
26 option local '/lan/'
27 option domain 'lan'
28 option expandhosts 1
29 option nonegcache 0
30 option authoritative 1
31 option readethers 1
32 option leasefile '/tmp/dhcp.leases'
33 option resolvfile '/tmp/resolv.conf.auto'
34 ----
35
36 * Options 'local' and 'domain' enable _dnsmasq_ to serve entries in '/etc/hosts' as well as the DHCP client's names as if they were entered into the _lan_ DNS domain.
37 * Options 'domainneeded', 'boguspriv', 'localise_queries', and 'expandhosts' make sure that requests for these local host names (and the reverse lookup) never get forwarded to the upstream DNS servers.
38 * Option 'authoritative' makes the router the only DHCP server on this network; clients get their IP lease a lot faster this way.
39 * Option 'leasefile' stores the leases in a file, so that they can be picked up again if _dnsmasq_ is restarted.
40 * Option 'resolvfile' tells _dnsmasq_ to use this file to find upstream name servers; it gets created by the WAN DHCP client or the PPP client.
41
42 === All Options
43 [cols="4*1,4",options="header"]
44 |====
45 | Name | Type | Default | Option | Description
46 | 'add_local_domain' | boolean | '1' | | Add the local domain as search directive in resolv.conf.
47 | 'add_local_hostname' | boolean | '1' | | Add A and PTR records automatically for the local hostname.
48 | 'addnhosts' | list of file paths | _(none)_ | '-H' | Additional host files to read for serving DNS responses
49 | 'authoritative' | boolean | '0' | '-K' | Force _dnsmasq_ into authoritative mode. This speeds up DHCP leasing. Used if this is the only server on the network
50 | 'bogusnxdomain' | list of IP addresses | _(none)_ | '-B' | IP addresses to convert into NXDOMAIN responses (to counteract upstream DNS servers that never return NXDOMAIN).
51 | 'boguspriv' | boolean | '0' | '-b' | Reject reverse lookups to private IP ranges where no corresponding entry exists in '/etc/hosts'
52 | 'cachelocal' | boolean | '1' | | When set to '0', use each network interface's 'dns' address in the local '/etc/resolv.conf'. Normally, only the loopback address is used, and all queries go through _dnsmasq_.
53 | 'cachesize' | integer | '150' | '-c' | Size of _dnsmasq_ query cache.
54 | 'dbus' | boolean | '0' | '-1' | Enable DBus messaging for _dnsmasq_. *CAUTION*: Standard builds of _dnsmasq_ do not include DBus support.
55 | 'dhcp_boot' | string | _(none)_ |--dhcp-boot>| Specifies BOOTP options, in most cases just the file name
56 | 'dhcphostsfile' | file path | _(none)_ | --dhcp-hostsfile | Specify an external file with per host DHCP options
57 | 'dhcpleasemax' | integer | '150' | '-X' | Maximum number of DHCP leases
58 | 'dnsforwardmax' | integer | '150' | '-0' (zero) | Maximum number of concurrent connections
59 | 'domain' | domain name | _(none)_ | '-s' | DNS domain handed out to DHCP clients
60 | 'domainneeded' | boolean | '0' | '-D' | Tells _dnsmasq_ never to forward queries for plain names, without dots or domain parts, to upstream nameservers. If the name is not known from /etc/hosts or DHCP then a "not found" answer is returned
61 | 'dnssec' | boolean | '0' | --dnssec | Validate DNS replies and cache DNSSEC data. *CAUTION*: Requires the _dnsmasq-full_ package.
62 | 'dnsseccheckunsigned' | boolean | '0' | --dnssec-check-unsigned | Check the zones of unsigned replies to ensure that unsigned replies are allowed in those zones. This protects against an attacker forging unsigned replies for signed DNS zones, but is slower and requires that the nameservers upstream of _dnsmasq_ are DNSSEC-capable. *CAUTION*: Requires the _dnsmasq-full_ package.
63 | 'ednspacket_max' | integer | '1280' | '-P' | Specify the largest EDNS.0 UDP packet which is supported by the DNS forwarder
64 | 'enable_tftp' | boolean | '0' | --enable-tftp | Enable the builtin TFTP server
65 | 'expandhosts' | boolean | '0' | '-E' | Add the local domain part to names found in '/etc/hosts'
66 | 'filterwin2k' | boolean | '0' | '-f' | Do not forward requests that cannot be answered by public name servers
67 | 'fqdn' | boolean | '0' | --dhcp-fqdn | Do not resolve unqualified local hostnames. Needs 'domain' to be set.
68 | 'interface' | list of interface names | _(all interfaces)_ | '-i' | List of interfaces to listen on. If unspecified, _dnsmasq_ will listen to all interfaces except those listed in 'notinterface'. Note that _dnsmasq_ listens on loopback by default.
69 | 'leasefile' | file path | _(none)_ | '-l' (ell) | Store DHCP leases in this file
70 | 'local' | string | _(none)_ | '-S' | Look up DNS entries for this domain from '/etc/hosts'. This follows the same syntax as 'server' entries, see the man page.
71 | 'localise_queries' | boolean | '0' | '-y' | Choose IP address to match the incoming interface if multiple addresses are assigned to a host name in '/etc/hosts'. *CAUTION*: Note well the spelling of this option.
72 | 'localservice' | boolean | '1' | --local-service | Accept DNS queries only from hosts whose address is on a local subnet, ice. a subnet for which an interface exists on the server.
73 | 'logqueries' | boolean | '0' | '-q' | Log the results of DNS queries, dump cache on SIGUSR1
74 | 'nodaemon' | boolean | '0' | '-d' | Don't daemonize the _dnsmasq_ process
75 | 'nohosts' | boolean | '0' | '-h' | Don't read DNS names from '/etc/hosts'
76 | 'nonegcache' | boolean | '0' | '-N' | Disable caching of negative "no such domain" responses
77 | 'noresolv' | boolean | '0' | '-R' | Don't read upstream servers from '/etc/resolv.conf'
78 | 'notinterface' | list of interface names | _(none)_ | '-I' (eye) | Interfaces _dnsmasq_ should not listen on.
79 | 'nonwildcard' | boolean | '0' | '-z' | Bind only configured interface addresses, instead of the wildcard address.
80 | 'port' | port number | '53' | '-p' | Listening port for DNS queries, disables DNS server functionality if set to '0'
81 | 'queryport' | integer | _(none)_ | '-Q' | Use a fixed port for outbound DNS queries
82 | 'readethers' | boolean | '0' | '-Z' | Read static lease entries from '/etc/ethers', re-read on SIGHUP
83 | 'rebind_protection' | boolean | '1' | --stop-dns-rebind | Enables DNS rebind attack protection by discarding upstream RFC1918 responses
84 | 'rebind_localhost' | boolean | '0' | --rebind-localhost-ok | Allows upstream 127.0.0.0/8 responses, required for DNS based blacklist services, only takes effect if rebind protection is enabled
85 | 'rebind_domain' | list of domain names | _(none)_ | --rebind-domain-ok | List of domains to allow RFC1918 responses for, only takes effect if rebind protection is enabled
86 | 'resolvfile' | file path | '/etc/resolv.conf' | '-r' | Specifies an alternative resolv file
87 | 'server' | list of strings | _(none)_ | '-S' | List of DNS servers to forward requests to. See the _dnsmasq_ man page for syntax details.
88 | 'strictorder' | boolean | '0' | '-o' | Obey order of DNS servers in '/etc/resolv.conf'
89 | 'tftp_root' | directory path | _(none)_ | --tftp-root | Specifies the TFTP root directory
90 |====
91
92 === DHCP Pools
93
94 Sections of the type 'dhcp' specify per interface lease pools and settings for serving DHCP requests. Typically there is at least one section of this type present in the '/etc/config/dhcp' file to cover the lan interface.
95
96 You can disable a lease pool for a specific interface by specifying the 'ignore' option in the corresponding section.
97
98 A minimal example of a 'dhcp' section is listed below:
99
100 ----
101 config 'dhcp' 'lan'
102 option 'interface' 'lan'
103 option 'start' '100'
104 option 'limit' '150'
105 option 'leasetime' '12h'
106 option ra server
107 option dhcpv6 server
108 ----
109
110 * 'lan' specifies the OpenWrt interface that is served by this DHCP pool
111 * '100' is the offset from the network address, in the default configuration this would mean start leasing addresses from '192.168.1.100'
112 * '150' is the maximum number of addresses that may be leased, in the default configuration this would mean leasing addresses up to '192.168.1.250'
113 * '12h' specifies the time to live for handed out leases, twelve hours in this example
114 * 'server' defines the mode for IPv6 configuration (RA & DHCPv6)
115
116 Below is a listing of legal options for 'dhcp' sections.
117
118 [cols="4*1,4",options="header"]
119 |====
120 | Name | Type | Required | Default | Description
121 | 'dhcp_option' | list of strings | no | _(none)_ | The ID dhcp_option here must be with written with an underscore. The init script will translate this to --dhcp-option, with a hyphen, as ultimately used by dnsmasq. Multiple option values can be given for this _network-id_, with a a space between them and the total string between "". E.g. '26,1470' or 'option:mtu, 1470' that can assign an MTU per DHCP. Your client must accept MTU by DHCP for this to work. Or "3,192.168.1.1 6,192.168.1.1" to give out gateway and dns server addresses.
122 | 'dynamicdhcp' | boolean | no | '1' | Dynamically allocate client addresses, if set to '0' only clients present in the 'ethers' files are served
123 | 'force' | boolean | no | '0' | Forces DHCP serving on the specified interface even if another DHCP server is detected on the same network segment
124 | 'ignore' | boolean | no | '0' | Specifies whether _dnsmasq_ should ignore this pool if set to '1'
125 | 'dhcpv6' | string | no | 'none' | Specifies whether DHCPv6 server should be enabled ('server'), relayed ('relay') or disabled ('disabled')
126 | 'ra' | string | no | 'none' | Specifies whether Router Advertisements should be enabled ('server'), relayed ('relay') or disabled ('disabled')
127 | 'ndp' | string | no | 'none' | Specifies whether NDP should be relayed 'relay' or disabled 'none'
128 | 'master' | boolean | no | 0 | Specifies whether DHCPv6, RA and NDP in relay mode is a master interface or not.
129 | 'interface' | logical interface name | yes | _(none)_ | Specifies the interface associated with this DHCP address pool; must be one of the interfaces defined in '/etc/config/network'.
130 | 'leasetime' | string | yes | '12h' | Specifies the lease time of addresses handed out to clients, for example '12h' or '30m'
131 | 'limit' | integer | yes | '150' | Specifies the size of the address pool (e.g. with start=100, limit=150, maximum address will be .249)
132 | 'networkid' | string | no | _(value of 'interface')_ | The dhcp functionality defined in the dhcp section is limited to the interface indicated here through its _network-id_. In case omitted the system tries to know the network-id via the 'interface' setting in this dhcp section, through consultation of /etc/config/network. Some IDs get assigned dynamically, are not provided by network, but still can be set here.
133 | 'start' | integer | yes | '100' | Specifies the offset from the network address of the underlying interface to calculate the minimum address that may be leased to clients. It may be greater than 255 to span subnets.
134 |====
135
136 Notes:
137
138 * Although called 'interface', this is the network name, i.e. lan, wan, wifi etc. (section names in /etc/config/network), NOT the interface name used internally, like eth0, eth1, wlan0 etc. (the 'ifname' IDs in /etc/config/network).
139 * Although called 'networkid', this is the interface name used internally, i.e. eth0, eth1, wlan0 etc., not the network name (lan, wan, wifi etc.).
140 This departs from 'ifname' and 'network' as used in /etc/config/network and in /etc/config/wireless, so double check!
141
142 === Static Leases
143
144 You can assign fixed IP addresses to hosts on your network, based on their MAC (hardware) address.
145
146 The configuration options in this section are used to construct a '-G' option for _dnsmasq_.
147
148 ----
149 config host
150 option ip '192.168.1.2'
151 option mac '00:11:22:33:44:55'
152 option name 'mypc'
153 ----
154 This adds the fixed IP address 192.168.1.2 and the name "mypc" for a machine with the (Ethernet) hardware address 00:11:22:33:44:55.
155
156 ----
157 config host
158 option ip '192.168.1.3'
159 option mac '11:22:33:44:55:66 aa:bb:cc:dd:ee:ff'
160 option name 'mylaptop'
161 ----
162 This adds the fixed IP address 192.168.1.3 and the name "mylaptop" for a machine with the (Ethernet) hardware address 11:22:33:44:55:66 or aa:bb:cc:dd:ee:ff. Note that this is **unreliable** if more than one of the listed mac addresses is on the network simultaneously. It's useful for cases such as a laptop with both wireless and wired interfaces, provided that only one will be active at a given time.
163
164 [cols="4*1,4",options="header"]
165 |====
166 | Name | Type | Required | Default | Description
167 | 'ip' | string | yes | _(none)_ | 'ignore' or the IP address to be used for this host.
168 | 'mac' | string | no | _(none)_ | The hardware address(es) of this host, separated by commas.
169 | 'hostid' | string | no | _(none)_ | The IPv6 interface identifier (address suffix) as hexadecimal number (max. 8 chars)
170 | 'duid' | string | no | _(none)_ | The DHCPv6-DUID of this host.
171 | 'name' | string | no | _(none)_ | Optional hostname to assign.
172 | 'tag' | string | no | _(none)_ | Set the given tag for matching hosts.
173 | 'dns' | boolean | no | '0' | Add static forward and reverse DNS entries for this host.
174 | 'broadcast' | boolean | no | '0' | Force broadcast DHCP response.
175 | 'leasetime' | string | no | _(none)_ | Host-specific lease time, e.g. 2m, 3h, 5d. Note: introduced by r48801 in trunk
176 |====
177
178 As well as adding 'host' sections, you can also enable the 'dnsmasq' section option 'readethers', and add entries to the '/etc/ethers' file.
179
180 === DHCP OPTION example to set an alternative default gateway
181
182 You can specify an alternative default Gateway
183
184 ----
185 config 'dhcp' 'lan'
186 option 'interface' 'lan'
187 option 'start' '100'
188 option 'limit' '150'
189 option 'leasetime' '12h'
190 list 'dhcp_option' '3,192.168.1.2'
191 ----
192
193 use the list 'dhcp_option' '3,192.168.1.2' to set the default gateway. A list of options can be found here link:http://www.networksorcery.com/enp/protocol/bootp/options.htm[here]
194
195 === Booting Options
196
197 Some hosts support booting over the network (PXE booting). DHCP/BOOTP is used to tell the host which file to boot and the server to load it from. Each client can only receive one set of filename and server address options. If different hosts should boot different files, or boot from different servers, you can use _network-ids_ to map options to each client.
198
199 Usually, you need to set additional DHCP options (through 'dhcp_option') for further stages of the boot process. See the _dnsmasq_ man page for details on the syntax of the 'O' option.
200
201 The configuration options in this section are used to construct a '-M' option for _dnsmasq_.
202
203 *Note*: odhcp currently lacks support root-path specification. If you need this functionality, disable odhcpd and use dnsmasq instead.
204
205 ----
206 config boot linux
207 option filename '/tftpboot/pxelinux.0'
208 option serveraddress '192.168.1.2'
209 option servername 'fileserver'
210 list dhcp_option 'option:root-path,192.168.1.2:/data/netboot/root'
211 ----
212 This tells the client to load pxelinux.0 from the server at 192.168.1.2, and mount root from /data/netboot/root on the same server.
213 [cols="4*1,4",options="header"]
214 |====
215 | Name | Type | Required | Default | Description
216 | 'dhcp_option' | list of strings | no | _(none)_ | Additional options to be added for this network-id. *CAUTION*: If you specify this, you also need to specify the network-id.
217 | 'filename' | string | yes | _(none)_ | The filename the host should request from the boot server.
218 | 'networkid' | string | no | _(none)_ | The network-id these boot options should apply to. Applies to all clients if left unspecified.
219 | 'serveraddress' | string | yes | _(none)_ | The IP address of the boot server.
220 | 'servername' | string | yes | _(none)_ | The hostname of the boot server.
221 | 'force' | bool | no | _(none)_ | dhcp-option will always be sent, even if the client does not ask for it in the parameter request list. This is sometimes needed, for example when sending options to PXELinux.
222 |====
223
224 === Classifying Clients And Assigning Individual Options
225
226 DHCP can provide the client with numerous options, such as the domain name, NTP servers, network booting options, etc. While some settings are applicable to all hosts in a network segment, other are more specific and apply only to a group of hosts, or even only a single one. _dnsmasq_ offers to group DHCP options and their values by a _network-id_, an alphanumeric identifier, and sending options only to hosts which have been tagged with that _network-id_.
227
228 In OpenWrt, you can tag hosts by the DHCP range they're in (section 'dhcp'), or a number of options the client might send with their DHCP request. In each of these sections, you can use the 'dhcp_option' list to add DHCP options to be sent to hosts with this _network-id_.
229
230 Each classifying section has two configuration options: the value of the DHCP option used to distinguish clients, and the _network-id_ that these clients should be tagged with. Here's a template:
231
232 ----
233 config _classifier_
234 option _classifier_ '_value_'
235 option networkid '_network-id_'
236 list dhcp_option '_DHCP-option_'
237 ----
238
239 The placeholder '_classifier_' can be one of these values:
240 [cols="1,4",options="header"]
241 |====
242 | Classifier | Description
243 | 'mac' | Hardware address of the client
244 | 'vendorclass' | String sent by the client representing the vendor of the client. _dnsmasq_ performs a substring match on the vendor class string using this value.
245 | 'userclass' | String sent by the client representing the user of the client. _dnsmasq_ performs a substring match on the user class string using this value.
246 | 'circuitid' | Matches the circuit ID as sent by the relay agent, as defined in RFC3046.
247 | 'remoteid' | Matches the remote ID as sent by the relay agent, as defined in RFC3046.
248 | 'subscrid' | Matches the subscriber ID as sent by the relay agent, as defined in RFC3993.
249 |====
250
251
252 An example using the 'mac' classifier to create a tagged network for openvpn would look like this in the config file:
253
254 ----
255 config mac 'opnvpn'
256 option mac '00:FF:*:*:*:*'
257 option networkid 'opnvpn'
258 list dhcp_option '3'
259 ----
260
261
262 And like this in UCI
263 ----
264 dhcp.opnvpn=mac
265 dhcp.opnvpn.mac=00:FF:*:*:*:*
266 dhcp.opnvpn.networkid=opnvpn
267 dhcp.opnvpn.dhcp_option=3
268 ----
269
270 _DHCP-option_ adds a DHCP option for this _network-id_. See the _dnsmasq_ man page for a complete explanation of the syntax of the '-O' option.
271
272 _force_ is a bool option. It forces dhcp-option to always be sent, even if the client does not ask for it in the parameter request list. This is sometimes needed, for example when sending options to PXELinux.
273
274
275 == Using plain dnsmasq.conf
276
277 It is possible to mix the traditional '/etc/dnsmasq.conf' configuration file with the options found in '/etc/config/dhcp'.
278
279 The 'dnsmasq.conf' file does not exist by default but will be processed by _dnsmasq_ on startup if it is present. Note that options in '/etc/config/dhcp' take precedence over 'dnsmasq.conf' since they are translated to command line arguments.
280
281 You can have 'dnsmasq' execute a script on every action:
282
283 ----
284 dhcp-script=/sbin/action.sh
285 ----
286
287 === DNS and DHCP Ports
288
289 DNS needs TCP and UDP port 53 open on the firewall. DHCP needs UDP ports 67 and 68 open from your zone to/from the firewall. See http://wiki.openwrt.org/doc/recipes/guest-wlan and http://www.thekelleys.org.uk/dnsmasq/docs/dnsmasq-man.html (viz "--dhcp-alternate-port") for more information.
290
291 == Examples
292
293 === Static Lease (MAC address hot swap)
294
295 Define a static lease for a host with MAC addresses '00:a0:24:5a:33:69' and '00:11:22:33:44:55' (handy when you use both wired and wireless connection on the same computer/laptop - of course, you can use just one MAC address) and assign the IP address '192.168.1.230' and the hostname 'example-host' to it. We call this _MAC address hot swap_, since IP address stay same, but MAC address changes.
296
297 ----
298 config 'host'
299 option 'name' 'example-host'
300 option 'ip' '192.168.1.230'
301 option 'mac' '00:a0:24:5a:33:69 00:11:22:33:44:55'
302 ----
303
304 === Troubleshooting ===
305
306 *CAUTION*: **Windows 7** has introduced a new _Microsoft-enhanced_ feature. It won't assign IP address obtained from a DHCP server to an interface, if the IP was used before for another interface, even if that other interface is **NOT** active currently (i.e. cable disconnected). This behaviour is unique and was not reported for older Windows versions, Mac OS nor Linux.
307
308 If you try configure MAC address hot swap on your router, Windows 7 clients will end up in an infinite link:http://tools.ietf.org/html/rfc1531#section-3.1[DORA] loop.
309
310 Solution:
311 - Create a bridge from the wireless and ethernet interfaces on your client
312
313 * it's trivial: google->windows 7 create bridge
314 * you will have to add the MAC address of the bridge to '/etc/config/dhcp'
315 *
316 ----
317 config 'host'
318 option 'name' 'example-host'
319 option 'ip' '192.168.1.230'
320 option 'mac' '00:a0:24:5a:33:69 00:11:22:33:44:55 02:a0:24:5a:33:69 02:11:22:33:44:55'
321 ----
322 * Since the bridge will probably take and alter your ethernet MAC address, you will lose SLAAC on wifi interface, making your laptop IPv6-disabled when only wireless is up.
323 - Another solution is IPv6 friendly, you don't need to create a bridge, nor add MAC address to dnsmasq config file, but it involves user interaction:
324 * When you plug the ethernet cable in, disable wireless interface in control panel (power off wireless won't do it).
325 * When you unplug ethernet cable, enable wireless and disable ethernet.
326
327 Notes:
328
329 * http://answers.microsoft.com/en-us/windows/forum/windows_7-networking/windows-7-refuses-dhcp-addresses-if-they-were/1b72b289-0f58-492f-afb8-e76c80a81f00
330 * _force_ is a bool option that will force dhcp-option to always be sent, even if the client does not ask for it in the parameter request list. This is sometimes needed, for example when sending options to PXELinux.
331
332 === Only allow static leases
333
334 If you want to distribute IPv4 addresses to known clients only (static leases), use:
335
336 ----
337 config dhcp 'lan'
338 ...
339 option dynamicdhcp 0
340 ----
341
342 With this, dnsmasq will consider static leases defined in "config host" blocks and in /etc/ethers, and refuse to hand out any IPv4 address to unknown clients.
343
344 Note that you shouldn't use this as a security feature to prevent unwanted clients from connecting. A client can simply configure a static IP in the right range to have access to the network.
345
346 === Custom Domain
347
348 Define a custom domain name and the corresponding PTR record - assigns the IP address '192.168.1.140' to the domain name 'typhoon' and construct an appropriate reverse record '140.1.168.192.in-addr.arpa'. It works like an entry in '/etc/hosts' but more flexible
349 and integrated.
350
351 *CAUTION*: Note that this currently only works for IPv4 addresses and that this functionality is not present in release prior to 8.09.2 .
352 *CAUTION*: Note that reverse records are not properly generated at present. (Barrier Breaker 14.07-RC2)
353
354 ----
355 config 'domain'
356 option 'name' 'typhoon'
357 option 'ip' '192.168.1.140'
358 ----
359
360 another example: redirect www.example.com to 1.2.3.4
361 ----
362 config 'domain'
363 option 'name' 'www.example.com'
364 option 'ip' '1.2.3.4'
365 ----
366
367 === SRV RR for SIP
368
369 To define an SRV record for SIP over UDP, with the default port of 5060 on the host pbx.mydomain.com, with a class of 0 and a weight of 10 one would use:
370
371 ----
372 config 'srvhost'
373 option srv '_sip._udp.mydomain.com'
374 option target 'pbx.mydomain.com'
375 option port 5060
376 option class 0
377 option weight 10
378 ----
379
380 === CNAME RR
381
382 A Canonical Name record specifies that a domain name is an alias for another domain, the "canonical" domain. To specify that the web server also doubles as the FTP server, one might use:
383
384 ----
385 config 'cname'
386 option cname 'ftp.example.com'
387 option target 'www.example.com'
388 ----
389 Note that it is necessary to use fully qualified domain names.
390
391 === MX RR
392
393 If you're running the mail server for your domain behind a firewall (and therefore, with split-horizon for your own domain) then you might need to convince that mailer that it's actually authoritative for your domain.
394
395 If sendmail tells you "Domain of sender address xxx@yyy.zzz does not exist" this is because it isn't finding an MX record confirming that it's an MX relay for that domain.
396
397 Adding:
398
399 ----
400 config 'mxhost'
401 option domain 'yyy.zzz'
402 option relay 'my.host.com'
403 option pref 10
404 ----
405
406 will mitigate the issues caused by split-horizon.
407
408 === TFTP Boot
409
410 Direct BOOTP requests to the TFTP server at the IP address '192.168.1.2' and use '/tftpboot/pxelinux.0' as boot file name.
411
412 ----
413 config 'boot'
414 option 'filename' 'pxelinux.0'
415 option 'servername' 'data'
416 option 'serveraddress' '192.168.1.2'
417 ----
418
419 === Multiple DHCP options
420
421 Multiple DHCP options can be configured under a single dhcp_option object. In this case, option 66 (tftp-server) and option 150 (multiple tftp servers) were used for a Cisco Callmanager deployment.
422
423 ----
424 config 'dhcp' 'lan'
425 option 'interface' 'lan'
426 option 'start' '62'
427 option 'limit' '192'
428 option 'leasetime' '600h'
429 list 'dhcp_option' '66,172.16.60.64'
430 list 'dhcp_option' '150,172.16.60.64'
431 ----
432
433 === Multiple DHCP/DNS server/forwarder instances
434
435 If you need multiple DNS forwarders with different configurations or DHCP server with different sets of lease files,
436 have a look at this link:https:_dev.openwrt.org/ticket/8862[patch].
437 Multiple dnsmasq "named" instances can be configured:
438 ----
439 config 'dnsmasq' 'hotspot'
440 option nonwildcard '1' # Tell dnsmasq to bind specific address(es)
441 option resolvfile '/tmp/resolv.conf.hotspot'
442 ...
443 ----
444
445 Your configs are usually active for all instances, but you can limit them to single instances by:
446 ----
447 config 'dhcp' 'lan'
448 option 'interface' 'lan'
449 option 'dnsmasq_config' 'hotspot'
450
451 config 'host'
452 option 'name' 'chef'
453 option 'mac' '00:00:00:00:00:00'
454 option 'ip' '192.168.1.66'
455 option 'dnsmasq_config' 'hotspot'
456 ----
457
458 The web interface (luci) has not been updated for this patch yet.
459
460 === Assigning DHCP pool to a subnet in a large network
461
462 In DHCP pool limit setting, the start and limit values do *not* refer to the "last digit", they're relative offsets to the network address.
463 * the network address of 10.0.0.1 / 255.0.0.0 is 10.0.0.0
464 * the 10.22.0.1 start address is 22 x /16 subnets away: (2^16) * 22 = 1441792
465 * 10.0.0.0 + 1441792 + 1 = 10.22.0.1 -> start = 1441793
466 * 10.22.0.254 - 10.22.0.1 = 253 -> limit = 253
467
468 ----
469 config dhcp lan
470 option interface lan
471 option start 1441793
472 option limit 253
473 ----
474
475 Test:
476
477 ----
478 root@OpenWrt:~# ipcalc.sh 10.0.0.1 255.0.0.0 1441793 253
479 IP=10.0.0.1
480 NETMASK=255.0.0.0
481 BROADCAST=10.255.255.255
482 NETWORK=10.0.0.0
483 PREFIX=8
484 START=10.22.0.1
485 END=10.22.0.254
486 root@OpenWrt:~#
487 ----
488
489 === Classifying Clients And Assigning Individual Options
490
491 Assign different dhcp-options to a single MAC address:
492
493 ----
494 uci batch <<'EOF'
495 add dhcp mac
496 set dhcp.@mac[-1].mac=00:11:22:33:44:55
497 set dhcp.@mac[-1].networkid=someone
498 add_list dhcp.@mac[-1].dhcp_option=6,192.168.1.3,192.168.1.2,192.168.1.1
499 add_list dhcp.@mac[-1].dhcp_option=3,192.168.1.2
500 add_list dhcp.@mac[-1].dhcp_option=44,192.168.1.3
501 commit dhcp
502 EOF
503 uci commit dhcp
504 /etc/init.d/dnsmasq reload
505 ----
506 Where 6=DNS, 3=Default Gateway, 44=WINS
507
508 Assign different dhcp-options to multiple hosts:
509
510 ----
511 config host
512 option name 'j400'
513 option mac '00:21:63:75:aa:17'
514 option ip '10.11.12.14'
515 option tag 'vpn' # assign tag "vpn" to this host
516
517 config host
518 option name 'j500'
519 option mac '01:22:64:76:bb:18'
520 option ip '10.11.12.15'
521 option tag 'vpn' # assign tag "vpn" to this host
522
523 config tag 'vpn' # match tag "vpn"
524 list dhcp_option '6,8.8.8.8,8.8.4.4' # assign arbitrary extra dhcp options to this tag
525 option force '1' #dhcp-option will always be sent, even if the client does not ask for it in the parameter request list. This is sometimes needed, for example when sending options to PXELinux.
526 ----
527
528 *CAUTION*: Specifying a dhcp option without any value, would disable that option. so for example you can use:
529 ----
530 list dhcp_option '3'
531 ----
532 to disable sending a default gateway to a specific client
533
534 === Enabling DHCP without enabling DNS
535
536 This is useful when you just want to hand out addresses to clients, without doing any DNS.
537
538 ----
539 config dnsmasq
540 ...
541 option port 0
542 option domain ''
543 ----
544
545 The second option prevents dnsmasq from giving out a domain name and DNS search list to clients: this is useless without DNS resolving.
546
547 Of course, you will want to hand out the address of a DNS resolver to clients:
548
549 ----
550 config dhcp lan
551 option interface lan
552 ...
553 list dhcp_option "6,80.67.188.188,6,80.67.169.12"
554 list dns "2001:913::8"
555 list dns "2001:910:800::12"
556 ----
557
558 The `dhcp_option` entry is meant for dnsmasq, while the more elegant `dns` entries are understood by odhcpd. By default, odhcpd is only used for IPv6, but if you also use odhcpd for IPv4, you can just use `dns` entries for everything.
559
560 === Several DNS servers
561
562 ----
563 config dnsmasq
564 option domainneeded '1'
565 option localise_queries '1'
566 option local '/lan/'
567 option domain 'lan'
568 option expandhosts '1'
569 option authoritative '1'
570 option readethers '1'
571 option leasefile '/tmp/dhcp.leases'
572 option resolvfile '/tmp/resolv.conf.auto'
573 list server '/subdomain.example.com/192.0.2.1'
574 #be careful that some options should be absent (or set to False)
575 #to allow the forwarding towards the "so defined" private networks
576 #http://en.wikipedia.org/wiki/Private_network
577 # likely 'bogusprivat'
578 list server '/example.com/208.67.222.222'
579 option rebind_protection '0'
580 ----
581
582 === Conditional DNS Forwarding for Windows Active Directory Domains / DNS Dependent Directory Based Authentication Services
583
584 1. Install dnsmasq using your local package manager
585 2. Edit /etc/dnsmasq.conf
586 . Tells dnsmasq to forward anything with the domain of remote.local to dns server 10.25.11.2
587 server=/remote.local/10.25.11.2
588 . Listen to requests only coming from the local machine
589 listen-address=127.0.0.1
590 . Do not cache anything
591 . A decent dns server will already cache for your local network
592 cache-size=0
593 3. Edit /etc/resolv.conf
594
595 . Local LAN Domain
596 domain ion.lan
597
598 . local dnsmasq server
599 nameserver 127.0.0.1
600
601 . Your main dns server (dnsmasq will forward all requests to this server)
602 nameserver 10.20.1.1
603 4. Start dnsmasq
604
605 5. Test – ping a local server and remote server using the FQDN
606
607 All dns requests will be forwarded to 10.20.1.1 except any matching *.remote.local. server.remote.local will be forwarded to 10.25.11.2
608
609 Credit: link:http://pyther.net/2010/12/dns-conditional-forwarding-dnsmasq/[here]
610
611 ----
612
613 cat /etc/config/dhcp
614
615 config dnsmasq
616 option localise_queries '1'
617 option rebind_protection '0'
618 option authoritative '1'
619 option leasefile '/tmp/dhcp.leases'
620 option localservice '1'
621 option dnssec '0'
622 option cachesize '0'
623 option domain 'example.local'
624 option readethers '1'
625 option logqueries '1'
626 option fliterwin2k '0'
627 #Define your Domain and Domain Controllers IP address here.
628 option local '/example.local/192.168.1.X'**
629 list server '/0.openwrt.pool.ntp.org/8.8.8.8'
630 list server '/1.openwrt.pool.ntp.org/8.8.8.8'
631 list server '/2.openwrt.pool.ntp.org/8.8.8.8'
632 list server '/3.openwrt.pool.ntp.org/8.8.8.8'
633 option resolvfile '/etc/resolv.conf'
634 option boguspriv '1'
635
636 config dhcp 'lan'
637 option interface 'lan'
638 option start '100'
639 option limit '150'
640 option leasetime '12h'
641 ----
642 Almost completed, Now on to the finalisation of the /etc/resolv.conf Traditionally /etc/resolv.conf is populated via symlink based on interface settings which get inserted via script into /tmp/resolv.conf. We're going to disable this symlink because without doing so it would override our static settings.
643
644 You'll want to remove /etc/resolv.conf
645 That will remove the resolv.conf symlink. Then we will add the ip address of the secondary DNS and external resolving address inside the /etc/resolv.conf file finally establishing conditional forwarding, something that should be specified for easy configuration via the GUI.
646
647 ----
648 rm /etc/resolv.conf
649 echo "domain example.local">>/etc/resolv.conf
650 echo "nameserver 127.0.0.1">>/etc/resolv.conf
651 echo "nameserver 208.67.220.220">>/etc/resolv.conf
652
653 ----
654
655 ----
656
657 cat /etc/resolv.conf
658 #Define your Domain Below & Public DNS you desire.
659
660 domain example.local
661 nameserver 127.0.0.1
662 nameserver 208.67.220.220
663
664 ----