diff -Nru dnsmasq-2.62/CHANGELOG dnsmasq-2.63/CHANGELOG --- dnsmasq-2.62/CHANGELOG 2012-06-06 10:41:34.000000000 +0000 +++ dnsmasq-2.63/CHANGELOG 2012-08-17 09:30:10.000000000 +0000 @@ -1,3 +1,54 @@ +version 2.63 + Do duplicate dhcp-host address check in --test mode. + + Check that tftp-root directories are accessible before + start-up. Thanks to Daniel Veillard for the initial patch. + + Allow more than one --tfp-root flag. The per-interface + stuff is pointless without that. + + Add --bind-dynamic. A hybrid mode between the default and + --bind-interfaces which copes with dynamically created + interfaces. + + A couple of fixes to the build system for Android. Thanks + to Metin Kaya for the patches. + + Remove the interface: argument in --dhcp-range, and + the interface argument to --enable-tftp. These were a + still-born attempt to allow automatic isolated + configuration by libvirt, but have never (to my knowledge) + been used, had very strange semantics, and have been + superceded by other mechanisms. + + Fixed bug logging filenames when duplicate dhcp-host + addresses are found. Thanks to John Hanks for the patch. + + Fix regression in 2.61 which broke caching of CNAME + chains. Thanks to Atul Gupta for the bug report. + + Allow the target of a --cname flag to be another --cname. + + Teach DHCPv6 about the RFC 4242 information-refresh-time + option, and add parsing if the minutes, hours and days + format for options. Thanks to Francois-Xavier Le Bail for + the suggestion. + + Allow "w" (for week) as multiplier in lease times, as well + as seconds, minutes, hours and days. Álvaro Gámez Machado + spotted the ommission. + + Update French translation. Thanks to Gildas Le Nadan. + + Allow a DBus service name to be given with --enable-dbus + which overrides the default, + uk.org.thekelleys.dnsmasq. Thanks to Mathieu + Trudel-Lapierre for the patch. + + Set the "prefix on-link" bit in Router + Advertisements. Thanks to Gui Iribarren for the patch. + + version 2.62 Update German translation. Thanks to Conrad Kostecki. @@ -22,7 +73,6 @@ two addresses in the same network. Thanks to Jim Bos for his help nailing this. - version 2.61 Re-write interface discovery code on *BSD to use getifaddrs. This is more portable, more straightforward, diff -Nru dnsmasq-2.62/FAQ dnsmasq-2.63/FAQ --- dnsmasq-2.62/FAQ 2012-06-06 10:41:34.000000000 +0000 +++ dnsmasq-2.63/FAQ 2012-08-17 09:30:10.000000000 +0000 @@ -236,53 +236,70 @@ A: Ethernet (and 802.11 wireless) are supported on all platforms. On Linux all network types (including FireWire) are supported. -Q: What is this strange "bind-interface" option? +Q: What are these strange "bind-interface" and "bind-dynamic" options? -A: The DNS spec says that the reply to a DNS query must come from the - same address it was sent to. The traditional way to write an UDP - server to do this is to find all of the addresses belonging to the - machine (ie all the interfaces on the machine) and then create a - socket for each interface which is bound to the address of the - interface. Then when a packet is sent to address A, it is received - on the socket bound to address A and when the reply is also sent - via that socket, the source address is set to A by the kernel and - everything works. This is the how dnsmasq works when - "bind-interfaces" is set, with the obvious extension that is misses - out creating sockets for some interfaces depending on the - --interface, --address and --except-interface flags. The - disadvantage of this approach is that it breaks if interfaces don't - exist or are not configured when the daemon starts and does the - socket creation step. In a hotplug-aware world this is a real - problem. - - The alternative approach is to have only one socket, which is bound - to the correct port and the wildcard IP address (0.0.0.0). That - socket will receive _all_ packets sent to port 53, no matter what - destination address they have. This solves the problem of - interfaces which are created or reconfigured after daemon - start-up. To make this work is more complicated because of the - "reply source address" problem. When a UDP packet is sent by a - socket bound to 0.0.0.0 its source address will be set to the - address of one of the machine's interfaces, but which one is not - determined and can vary depending on the OS being run. To get round - this it is neccessary to use a scary advanced API to determine the - address to which a query was sent, and force that to be the source - address in the reply. For IPv4 this stuff in non-portable and quite - often not even available (It's different between FreeBSD 5.x and - Linux, for instance, and FreeBSD 4.x, Linux 2.0.x and OpenBSD don't - have it at all.) Hence "bind-interfaces" has to always be available - as a fall back. For IPv6 the API is standard and universally - available. - - It could be argued that if the --interface or --address flags are - used then binding interfaces is more appropriate, but using - wildcard binding means that dnsmasq will quite happily start up - after being told to use interfaces which don't exist, but which are - created later. Wildcard binding breaks the scenario when dnsmasq is - listening on one interface and another server (most probably BIND) - is listening on another. It's not possible for BIND to bind to an - (address,port) pair when dnsmasq has bound (wildcard,port), hence - the ability to explicitly turn off wildcard binding. +A: Dnsmasq from v2.63 can operate in one of three different "networking + modes". This is unfortunate as it requires users configuring dnsmasq + to take into account some rather bizzare contraints and select the + mode which best fits the requirements of a particular installation. + The origin of these are deficiencies in the Unix networking + model and APIs and each mode has different advantages and + problems. Just to add to the confusion, not all modes are available on + all platforms (due the to lack of supporting network APIs).To further + add to the confusion, the rules for the DHCP subsystem on dnsmasq are + different to the rules for the DNS and TFTP subsystems. + + The three modes are "wildcard", "bind-interfaces" and "bind-dynamic". + + In "wildcard" mode, dnsmasq binds the wildcard IP address (0.0.0.0 or + ::). This allows it to recieve all the packets sent to the server on + the relevant port. Access control (--interface, --except-interface, + --listen-address, etc) is implemented by dnsmasq: it queries the + kernel to determine the interface on which a packet was recieved and + the address to which it was sent, and applies the configured + rules. Wildcard mode is the default if neither of the other modes are + specified. + + In "bind-interfaces" mode, dnsmasq runs through all the network + interfaces available when it starts, finds the set of IP addresses on + those interfaces, filters that set using the access control + configuration, and then binds the set of IP addresses. Only packets + sent to the allowed addresses are delivered by the kernel to dnsmasq. + + In "bind-dynamic" mode, access control filtering is done both by + binding individual IP addresses, as for bind-interfaces, and by + inspecting individual packets on arrival as for wildcard mode. In + addition, dnsmasq notices when new interfaces appear or new addresses + appear on existing interfaces, and the resulting IP addresses are + bound automatically without having to restart dnsmasq. + + The mode chosen has four different effects: co-existence with other + servers, semantics of --interface access control, effect of new + interfaces, and legality of --interface specifications for + non-existent inferfaces. We will deal with these in order. + + A dnsmasq instance running in wildcard mode precludes a machine from + running a second instance of dnsmasq or any other DNS, TFTP or DHCP + server. Attempts to do so will fail with an "address in use" error. + Dnsmasq running in --bind-interfaces or bind-dynamic mode allow other + instances of dnsmasq or other servers, as long as no two servers are + configured to listen on the same interface address. + + The semantics of --interface varies subtly between wildcard or + bind-dynamic mode and bind-interfaces mode. The situation where this + matters is a request which arrives via one interface (A), but with a + destination address of a second interface (B) and when dnsmasq is + configured to listen only on B. In wildcard or bind-dynamic mode, such + a request will be ignored, in bind-interfaces mode, it will be + accepted. + + The creation of new network interfaces after dnsmasq starts is ignored + by dnsmasq when in --bind-interfaces mode. In wildcard or bind-dynamic + mode, such interfaces are handled normally. + + A --interface specification for a non-existent interface is a fatal + error at start-up when in --bind-interfaces mode, by just generates a + warning in wildcard or bind-dynamic mode. Q: Why doesn't Kerberos work/why can't I get sensible answers to queries for SRV records. diff -Nru dnsmasq-2.62/VERSION dnsmasq-2.63/VERSION --- dnsmasq-2.62/VERSION 2012-06-06 10:41:34.000000000 +0000 +++ dnsmasq-2.63/VERSION 2012-08-17 09:30:10.000000000 +0000 @@ -1 +1 @@ - (HEAD, v2.62, master) + (HEAD, v2.63rc6, v2.63, master) diff -Nru dnsmasq-2.62/bld/Android.mk dnsmasq-2.63/bld/Android.mk --- dnsmasq-2.62/bld/Android.mk 2012-06-06 10:41:34.000000000 +0000 +++ dnsmasq-2.63/bld/Android.mk 2012-08-17 09:30:10.000000000 +0000 @@ -17,4 +17,6 @@ LOCAL_CFLAGS := -O2 -g -W -Wall -D__ANDROID__ -DNO_IPV6 -DNO_TFTP -DNO_SCRIPT LOCAL_SYSTEM_SHARED_LIBRARIES := libc libcutils +LOCAL_LDLIBS := -L$(SYSROOT)/usr/lib -llog + include $(BUILD_EXECUTABLE) diff -Nru dnsmasq-2.62/dbus/DBus-interface dnsmasq-2.63/dbus/DBus-interface --- dnsmasq-2.62/dbus/DBus-interface 2012-06-06 10:41:34.000000000 +0000 +++ dnsmasq-2.63/dbus/DBus-interface 2012-08-17 09:30:10.000000000 +0000 @@ -19,7 +19,8 @@ Dnsmasq provides one service on the DBus: uk.org.thekelleys.dnsmasq -and a single object: /uk/org/thekelleys/dnsmasq +and a single object: /uk/org/thekelleys/dnsmasq +The name of the service may be changed by giving an argument to --enable-dbus. 1. METHODS ---------- diff -Nru dnsmasq-2.62/debian/changelog dnsmasq-2.63/debian/changelog --- dnsmasq-2.62/debian/changelog 2012-09-09 19:24:13.000000000 +0000 +++ dnsmasq-2.63/debian/changelog 2012-09-09 19:24:13.000000000 +0000 @@ -1,3 +1,40 @@ +dnsmasq (2.63-1ubuntu1) quantal; urgency=low + + * Merge with Debian unstable; remaining changes: + - debian/control: dnsmasq-base Breaks/Replaces dnsmasq (<< 2.62-3ubuntu1) + due to the dbus config file move. + * dnsmasq 2.63 noteworthy changes: + - Allow setting a dbus name with --enable-dbus which overrides the default + name. (LP: #1034946) + - Add --bind-dynamic. A hybrid mode between default and --bind-interfaces + which copes with dynamically created interfaces. (LP: #526386) + - Fix regression in 2.61 which broke caching of CNAME chains. + - Allow the target of a --cname flag to be another --cname. + - Teach DHCPv6 about the RFC 4242 information-refresh-time option, and add + parsing for the minutes, hours and days format for options. + - Allow "w" (for week) as multiplier in lease times. + + -- Mathieu Trudel-Lapierre Mon, 20 Aug 2012 14:24:30 -0400 + +dnsmasq (2.63-1) unstable; urgency=low + + * New upstream. + * Move /etc/dbus-1/system.d/dnsmasq.conf from dnsmasq to dnsmasq-base. + + -- Simon Kelley Mon, 11 Jun 2012 21:55:35 +0000 + +dnsmasq (2.62-3ubuntu1) quantal; urgency=low + + * debian/rules: install the dnsmasq dbus configuration in dnsmasq-base, since + users of the standalone binary might want to use DBus (ie. NetworkManager). + (LP: #1029977) + * debian/control: dnsmasq-base Breaks/Replaces dnsmasq (<< 2.62-3ubuntu1) due + to the file move. + * debian/dnsmasq.conffiles, debian/dnsmasq-base.conffiles: make sure the dbus + configuration file is properly listed as such. + + -- Mathieu Trudel-Lapierre Tue, 24 Jul 2012 08:57:45 -0400 + dnsmasq (2.62-3) unstable; urgency=low * Do resolvconf and /etc/default startup logic when @@ -9,7 +46,7 @@ * Pass LDFLAGS to make to get hardening in linker. - -- Simon Kelley Thu, 7 June 2012 09:53:43 +0000 + -- Simon Kelley Thu, 7 Jun 2012 09:53:43 +0000 dnsmasq (2.62-1) unstable; urgency=low diff -Nru dnsmasq-2.62/debian/conffiles dnsmasq-2.63/debian/conffiles --- dnsmasq-2.62/debian/conffiles 2012-09-09 19:24:13.000000000 +0000 +++ dnsmasq-2.63/debian/conffiles 2012-09-09 19:24:13.000000000 +0000 @@ -2,5 +2,4 @@ /etc/default/dnsmasq /etc/dnsmasq.conf /etc/resolvconf/update.d/dnsmasq -/etc/dbus-1/system.d/dnsmasq.conf /etc/insserv.conf.d/dnsmasq diff -Nru dnsmasq-2.62/debian/control dnsmasq-2.63/debian/control --- dnsmasq-2.62/debian/control 2012-09-09 19:24:13.000000000 +0000 +++ dnsmasq-2.63/debian/control 2012-09-09 19:24:13.000000000 +0000 @@ -2,7 +2,8 @@ Section: net Priority: optional Build-depends: gettext, libnetfilter-conntrack-dev [linux-any], libidn11-dev, libdbus-1-dev (>=0.61) -Maintainer: Simon Kelley +Maintainer: Ubuntu Developers +XSBC-Original-Maintainer: Simon Kelley Standards-Version: 3.9.3 Package: dnsmasq @@ -23,7 +24,8 @@ Package: dnsmasq-base Architecture: any Depends: ${shlibs:Depends} -Conflicts: dnsmasq (<<2.41) +Breaks: dnsmasq (<< 2.62-3ubuntu1) +Replaces: dnsmasq (<< 2.62-3ubuntu1) Description: Small caching DNS proxy and DHCP/TFTP server This package contains the dnsmasq executable and documentation, but not the infrastructure required to run it as a system daemon. For diff -Nru dnsmasq-2.62/debian/dnsmasq-base.conffiles dnsmasq-2.63/debian/dnsmasq-base.conffiles --- dnsmasq-2.62/debian/dnsmasq-base.conffiles 1970-01-01 00:00:00.000000000 +0000 +++ dnsmasq-2.63/debian/dnsmasq-base.conffiles 2012-09-09 19:24:13.000000000 +0000 @@ -0,0 +1 @@ +/etc/dbus-1/system.d/dnsmasq.conf diff -Nru dnsmasq-2.62/debian/rules dnsmasq-2.63/debian/rules --- dnsmasq-2.62/debian/rules 2012-09-09 19:24:13.000000000 +0000 +++ dnsmasq-2.63/debian/rules 2012-09-09 19:24:13.000000000 +0000 @@ -85,7 +85,6 @@ -d debian/daemon/etc/resolvconf/update.d \ -d debian/daemon/usr/lib/resolvconf/dpkg-event.d \ -d debian/daemon/etc/default \ - -d debian/daemon/etc/dbus-1/system.d \ -d debian/daemon/lib/systemd/system \ -d debian/daemon/etc/insserv.conf.d install -m 644 debian/conffiles debian/daemon/DEBIAN @@ -96,7 +95,6 @@ install -m 644 debian/default debian/daemon/etc/default/dnsmasq install -m 644 dnsmasq.conf.example debian/daemon/etc/dnsmasq.conf install -m 644 debian/readme.dnsmasq.d debian/daemon/etc/dnsmasq.d/README - install -m 644 debian/dbus.conf debian/daemon/etc/dbus-1/system.d/dnsmasq.conf install -m 644 debian/systemd.service debian/daemon/lib/systemd/system/dnsmasq.service install -m 644 debian/insserv debian/daemon/etc/insserv.conf.d/dnsmasq ln -s $(package) debian/daemon/usr/share/doc/dnsmasq @@ -111,6 +109,7 @@ rm -rf debian/base install -m 755 \ -d debian/base/DEBIAN \ + -d debian/base/etc/dbus-1/system.d \ -d debian/base/usr/share/doc/$(package) \ -d debian/base/usr/share/doc/$(package)/examples \ -d debian/base/var/run \ @@ -129,10 +128,12 @@ install -m 644 dbus/DBus-interface debian/base/usr/share/doc/$(package)/. gzip -9 debian/base/usr/share/doc/$(package)/DBus-interface endif + install -m 644 debian/dnsmasq-base.conffiles debian/base/DEBIAN/conffiles install -m 644 debian/changelog debian/base/usr/share/doc/$(package)/changelog.Debian gzip -9 debian/base/usr/share/doc/$(package)/changelog.Debian install -m 644 debian/readme debian/base/usr/share/doc/$(package)/README.Debian install -m 644 debian/copyright debian/base/usr/share/doc/$(package)/copyright + install -m 644 debian/dbus.conf debian/base/etc/dbus-1/system.d/dnsmasq.conf gzip -9 debian/base/usr/share/man/man8/dnsmasq.8 for f in debian/base/usr/share/man/*; do \ if [ -f $$f/man8/dnsmasq.8 ]; then \ diff -Nru dnsmasq-2.62/dnsmasq.conf.example dnsmasq-2.63/dnsmasq.conf.example --- dnsmasq-2.62/dnsmasq.conf.example 2012-06-06 10:41:34.000000000 +0000 +++ dnsmasq-2.63/dnsmasq.conf.example 2012-08-17 09:30:10.000000000 +0000 @@ -326,6 +326,9 @@ # dnsmasq and another. #dhcp-option=option6:dns-server,[::],[1234::88] +# Ask client to poll for option changes every six hours. (RFC4242) +#dhcp-option=option6:information-refresh-time,6h + # Set the NTP time server address to be the same machine as # is running dnsmasq #dhcp-option=42,0.0.0.0 @@ -522,7 +525,7 @@ # If you want to disable negative caching, uncomment this. #no-negcache -# Normally responses which come form /etc/hosts and the DHCP lease +# Normally responses which come from /etc/hosts and the DHCP lease # file have Time-To-Live set as zero, which conventionally means # do not cache further. If you are happy to trade lower load on the # server for potentially stale date, you can set a time-to-live (in diff -Nru dnsmasq-2.62/man/dnsmasq.8 dnsmasq-2.63/man/dnsmasq.8 --- dnsmasq-2.62/man/dnsmasq.8 2012-06-06 10:41:34.000000000 +0000 +++ dnsmasq-2.63/man/dnsmasq.8 2012-08-17 09:30:10.000000000 +0000 @@ -204,6 +204,17 @@ same machine. Setting this option also enables multiple instances of dnsmasq which provide DHCP service to run in the same machine. .TP +.B --bind-dynamic +Enable a network mode which is a hybrid between +.B --bind-interfaces +and the default. Dnsmasq binds the address of individual interfaces, +allowing multiple dnsmasq instances, but if new interfaces or +addresses appear, it automatically listens on those (subject to any +access-control configuration). This makes dynamically created +interfaces work in the same way as the default. Implementing this +option requires non-standard networking APIs and it is only available +under Linux. On other platforms it falls-back to --bind-interfaces mode. +.TP .B \-y, --localise-queries Return answers to DNS queries from /etc/hosts which depend on the interface over which the query was received. If a name in /etc/hosts has more than one address associated with @@ -260,11 +271,13 @@ Don't read /etc/resolv.conf. Get upstream servers only from the command line or the dnsmasq configuration file. .TP -.B \-1, --enable-dbus +.B \-1, --enable-dbus[=] Allow dnsmasq configuration to be updated via DBus method calls. The configuration which can be changed is upstream DNS servers (and corresponding domains) and cache clear. Requires that dnsmasq has -been built with DBus support. +been built with DBus support. If the service name is given, dnsmasq +provides service at that name, rather than the default which is +.B uk.org.thekelleys.dnsmasq .TP .B \-o, --strict-order By default, dnsmasq will send queries to any of the upstream servers @@ -450,14 +463,16 @@ Return a CNAME record which indicates that is really . There are significant limitations on the target; it must be a DNS name which is known to dnsmasq from /etc/hosts (or additional -hosts files) or from DHCP. If the target does not satisfy this +hosts files), from DHCP or from another +.B --cname. +If the target does not satisfy this criteria, the whole cname is ignored. The cname must be unique, but it is permissable to have more than one cname pointing to the same target. .TP .B --dns-rr=,,[] Return an arbitrary DNS Resource Record. The number is the type of the record (which is always in the C_IN class). The value of the record is -given by the hex data, which may be of the for 01:23:45 or 01 23 45 or +given by the hex data, which may be of the form 01:23:45 or 01 23 45 or 012345 or any mixture of these. .TP .B --interface-name=, @@ -518,9 +533,9 @@ included and configured. This option cannot be combined with --query-port. .TP -.B \-F, --dhcp-range=[interface:,][tag:[,tag:],][set:[,][,][,[,]][,] +.B \-F, --dhcp-range=[tag:[,tag:],][set:[,][,][,[,]][,] .TP -.B \-F, --dhcp-range=[interface:,][tag:[,tag:],][set:[,][,][,][,] +.B \-F, --dhcp-range=[tag:[,tag:],][set:[,][,][,][,] Enable the DHCP server. Addresses will be given out from the range to and from statically defined addresses given @@ -613,8 +628,6 @@ and .B slaac. -The interface: section is not normally used. See the -NOTES section for details of this. .TP .B \-G, --dhcp-host=[][,id:|*][,set:][,][,][,][,ignore] Specify per host parameters for the DHCP server. This allows a machine @@ -1358,12 +1371,11 @@ as recursive DNS server. If provided, the DHCPv6 options dns-server and domain-search are used for RDNSS and DNSSL. .TP -.B --enable-tftp[=] +.B --enable-tftp Enable the TFTP server function. This is deliberately limited to that needed to net-boot a client. Only reading is allowed; the tsize and blksize extensions are supported (tsize is only supported in octet -mode). See NOTES section for use of the interface argument. - +mode). .TP .B --tftp-root=[,] Look for files to transfer using TFTP relative to the given @@ -1627,52 +1639,6 @@ as is the tag "bootp", allowing some control over the options returned to different classes of hosts. -.B dhcp-range -may have an interface name supplied as -"interface:". The semantics if this are as follows: -For DHCP, if any other dhcp-range exists _without_ an interface name, -then the interface name is ignored and and dnsmasq behaves as if the -interface parts did not exist, otherwise DHCP is only provided to -interfaces mentioned in dhcp-range -declarations. For DNS, if there are no -.B --interface -or -.B --listen-address -flags, behaviour is unchanged by the interface part. If either of -these flags are present, the interfaces mentioned in -dhcp-ranges are added to the set which get DNS service. - -Similarly, -.B enable-tftp -may take an interface name, which enables TFTP only for a particular -interface, ignoring -.B --interface -or -.B --listen-address -flags. In addition -.B --tftp-secure -and -.B --tftp-unique-root -and -.B --tftp-no-blocksize -are ignored for requests from such interfaces. (A -.B --tftp-root -directive giving a root path and an interface should be -provided too.) - -These rules may seem odd at first sight, but they -allow a single line of the form "dhcp-range=interface:virt0,192.168.0.4,192.168.0.200" -to be added to dnsmasq configuration which then supplies -DHCP and DNS services to that interface, without affecting -what services are supplied to other interfaces and irrespective of -the existance or lack of "interface=" -lines elsewhere in the dnsmasq configuration. -"enable-tftp=virt0" and "tftp-root=,virt0" do the same job for TFTP. - The idea is -that such a line can be added automatically by libvirt -or equivalent systems, without disturbing any manual -configuration. - .SH EXIT CODES .PP 0 - Dnsmasq successfully forked into the background, or terminated diff -Nru dnsmasq-2.62/man/fr/dnsmasq.8 dnsmasq-2.63/man/fr/dnsmasq.8 --- dnsmasq-2.62/man/fr/dnsmasq.8 2012-06-06 10:41:34.000000000 +0000 +++ dnsmasq-2.63/man/fr/dnsmasq.8 2012-08-17 09:30:10.000000000 +0000 @@ -232,6 +232,18 @@ machine. Utiliser cette option permet également d'avoir plusieurs instances de Dnsmasq fournissant un service DHCP sur la même machine. .TP +.B --bind-dynamic +Autorise un mode réseau intermédiaire entre +.B --bind-interfaces +et le mode par défaut. Dnsmasq s'associe à une seule interface, ce qui permet +plusieurs instances de dnsmasq, mais si une interface ou adresse apparaissent, +il se mettra automatiquement à écouter sur celles-ci (les règles de contrôle +d'accès s'appliquent). +De fait, les interfaces créées dynamiquement fonctionnent de la même façon que +dans le comportement par défaut. Ce fonctionnement nécessite des APIs réseau +non standard et n'est disponible que sous Linux. Sur les autres plateformes, +le fonctionnement est celui du mode --bind-interfaces. +.TP .B \-y, --localise-queries Retourne des réponses aux requêtes DNS dépendantes de l'interface sur laquelle la requête a été reçue, à partir du fichier /etc/hosts. Si un nom dans @@ -532,9 +544,17 @@ Retourne un enregistrement de type CNAME qui indique que est en réalité . Il existe des contraintes significatives sur la valeur de cible; il doit s'agir d'un nom DNS qui est connu de dnsmasq via /etc/hosts -(ou un fichier hôtes additionnel) ou via DHCP. Si une cible ne satisfait -pas ces critères, le CNAME est ignoré. Le CNAME doit être unique, mais -il est autorisé d'avoir plus d'un CNAME pointant vers la même cible. +(ou un fichier hôtes additionnel), ou via DHCP, ou par un autre +.B --cname. +Si une cible ne satisfait pas ces critères, le CNAME est ignoré. Le CNAME +doit être unique, mais il est autorisé d'avoir plus d'un CNAME pointant +vers la même cible. +.TP +.B --dns-rr=,,[] +Retourne un enregistrement DNS arbitraire. Le numéro correspond au type +d'enregistrement (qui est toujours de la classe C_IN). La valeur de +l'enregistrement est donnée dans les données hexadécimales, qui peuvent +être de la forme 01:23:45, 01 23 45,+012345 ou n'importe quelle combinaison. .TP .B --interface-name=, Définit un entregistrement DNS associant le nom avec l'adresse primaire sur @@ -601,9 +621,9 @@ configuré pour cela. Cette option ne peut pas être combinée avec --query-port. .TP -.B \-F, --dhcp-range=[interface:,][tag: