Add a config list to the 'config dnsmasq' section to specify fixed DNS
addresses.
For example:
config dnsmasq:
[snip]
list address '/example.com/192.168.0.1'
will result in the argument '-A /example.com/192.168.0.1' to the dnsmasq
options. This configures dnsmasq to return the specified IP for any
queries to '*.example.com' names.
Useful for overriding lookups to a range of DNS names.
[jow: "append args" -> "xappend", "-A" -> "--address"]
Signed-off-by: Jeremy Kerr <jk@ozlabs.org>
SVN-Revision: 32624
-T, --local-ttl=<time>
When replying with information from /etc/hosts or the DHCP leases
file dnsmasq by default sets the time-to-live field to zero, meaning
that the requestor should not itself cache the information. This is
the correct thing to do in almost all situations. This option allows a
time-to-live (in seconds) to be given for these replies. This will
reduce the load on the server at the expense of clients using stale
data under some circumstances.
[jow: change -T to --local--ttl to conform with the other options]
Signed-off-by: Andrew Byrne <openwrt@andy.id.au>
openwrt-devel mailing list
openwrt-devel@lists.openwrt.orghttps://lists.openwrt.org/mailman/listinfo/openwrt-devel
SVN-Revision: 32623
This adds a new boolean option, fqdn, to the "config dnsmasq" section of
/etc/config/dhcp. The default is off. When set on, it enables the dhcp-fqdn
option to dnsmasq. dhcp-fqdn causes dnsmasq's DNS server to not resolve
unqualifed local hostnames. The "domain" option is required when using "fqdn".
Local hostnames will remain available for lookup using fully-qualified names.
Signed-off-by: Mark Mentovai <mark@moxienet.com>
SVN-Revision: 32569
dnsmasq currently permits dhcp_options to be specified only in "config dhcp"
sections of /etc/config/dhcp. When dnsmasq is providing DHCP service for
multiple subnets and there are multiple "config dhcp" sections without "option
ignore", it makes sense to allow dhcp_options that should apply globally in
the "config dnsmasq" section of /etc/config/dhcp. dhcp_option is a list option.
[jow: rework patch to apply after dhcp-option-force handling got introduced]
Signed-off-by: Mark Mentovai <mark@moxienet.com>
SVN-Revision: 32568
The option 'force' when set to '1' will transform a dhcp-option to dhcp-option-force instead in the config.
This is useful for forcing options to be sent back to a client (even options it didn't ask for).
Signed-off-by: Philip Prindeville <philipp@redfish-solutions.com>
SVN-Revision: 31816
On my network, I have a variety of machines and appliances, some of which need different configuration issues than the default options.
For example:
config host
option name 'client'
option mac '00:01:02:03:04:05'
option ip '192.168.1.20'
option tag 'acme'
config tag acme
option force '1'
list dhcp_option 'option:router,192.168.1.253'
list dhcp_option 'option:domain-name,acme.com'
list dhcp_option 'option:domain-search,acme.com,redfish-solutions.com'
which allows me to override the default router for my client's host, as well as its domain-name, and its domain-search.
this causes the following config lines:
dhcp-host=00:01:02:03:04:05,set:acme,192.168.1.20,client
dhcp-option-force=tag:acme,option:router,192.168.1.253
dhcp-option-force=tag:acme,option:domain-name,acme.com
dhcp-option-force=tag:acme,option:domain-search:acme.com,redfish-solutions.com
This could be useful elsewhere, for instance, if you have an IP CCTV that you don't want to have a default-route, etc.
Signed-off-by: Philip Prindeville <philipp@redfish-solutions.com>
SVN-Revision: 31815
Sometimes it's useful to compare the generated config file from UCI config with a hand-edited dnsmasq config file, especially if you're migrating to an OpenWRT router from something else (such as Astlinux).
Putting the generated config makes it easier to capture and diff, etc.
Signed-off-by: Philip Prindeville <philipp@redfish-solutions.com>
SVN-Revision: 31182
Adding the following syntax support:
config mxhost
option domain mydomain.com
option relay svr10.ironport.com
option pref 50
and this will generate an MX record for mydomain.com pointing at the relay with a given preference.
Redux: default the preference to 0 if absent.
Signed-off-by: Philip Prindeville <philipp@redfish-solutions.com>
SVN-Revision: 31057
The SRV record also requires the class and weight fields... Currently you can overload the "port" keyword as:
option port xxxx,class,weight
but this is counter-intuitive. Here we fix this.
Redux: make the port required.
Signed-off-by: Philip Prindeville <philipp@redfish-solutions.com>
SVN-Revision: 31056
It corresponds to the following example in dnsmasq.conf.example:
# Always set the name of the host with hardware address
# 11:22:33:44:55:66 to be "fred"
#dhcp-host=11:22:33:44:55:66,fred
Regards
Mathias
SVN-Revision: 26983
'limit' is actually the number of IP addresses to serve. See the use of ipcalc.sh.
For getting the expected number of IP addresses served, we have to decrement
limit by one.
Patch from: kentarou matsuyama <matsuyama@thinktube.com>
SVN-Revision: 25100
This tiny patch makes the dnsmasq init.d script listen to a parameter called "notinterface", which tells dnsmasq to not listen on a defined set of interfaces.
By default dnsmasq *always* listens on the loopback interface, even if you tell it to specifically listen on a certain other interface. Sometimes this is not desirable behaviour, so you might want to turn it off. This is useful when, for example, you want to have your own DNS server listening on the loopback interface.
Signed-off-by: Johnny Halfmoon <jhalfmoon at milksnot.com>
SVN-Revision: 17599
dnsmasq.init tried to set range options even when ignore was
set to "1". Now the functions stops processing after evaluating
the "ignore" option when the result is > 0
SVN-Revision: 15618
Jo-Philipp Wich