Dnsmasq: Difference between revisions

Dnsmasq
Developer(s)	Simon Kelley
Stable release	2.52 / January 22, 2010
Repository	thekelleys.org.uk/gitweb/?p=dnsmasq.git ;
Operating system	Unix-like
Type	DNS server
License	GNU General Public License
Website	thekelleys.org.uk/dnsmasq/

Browse history interactively

← Previous edit Next edit →

Content deleted Content added

VisualWikitext

Inline

Revision as of 03:54, 25 May 2010

Dnsmasq is a lightweight, easy to configure, DNS forwarder and DHCP server, designed to provide DNS (and optionally DHCP) services to a small-scale network. It can serve the names of local machines which are not in the global DNS. The DHCP server integrates with the DNS server and allows machines with DHCP-allocated addresses to appear in the DNS with names configured either in each host or in a central configuration file. Dnsmasq supports static and dynamic DHCP leases and BOOTP for network booting of diskless machines.

The developers of dnsmasq targeted home networks using NAT and connected to the internet via a modem, cable-modem or ADSL connection. But the system would function well in any small network where low resource-use and ease of configuration are important.

Supported platforms include Linux (with glibc and uClibc), BSD and Mac OS X.

Features

Dnsmasq provides the following features:

Simple DNS configuration of machines behind the firewall, independent of the details of an ISP's DNS servers
Clients which try to do DNS lookups while a modem-link to the internet is down will time out immediately.
Dnsmasq will serve names from the /etc/hosts file (or an alternate). The names of local machines provided in this way can all be addressed without having to maintain /etc/hosts on each machine.
The integrated DHCP server supports static and dynamic DHCP leases and multiple networks and IP ranges. It works across BOOTP relays and supports DHCP options including RFC 3397 DNS search lists.
Machines configured via DHCP have their names automatically included in the DNS and the names can be specified by each machine or centrally by associating a name with a MAC address in the dnsmasq config file.
Dnsmasq caches internet addresses (A records and AAAA records) and address-to-name mappings (PTR records), reducing the load on upstream servers and improving performance (especially on modem connections).
Users can configure dnsmasq to automatically pick up the addresses of its upstream nameservers from ppp or dhcp configuration. It will automatically reload this information if it changes. This facility helps maintainers of Linux firewall distributions to automate DNS configuration.
On IPv6-enabled boxes, dnsmasq can both talk to upstream servers via IPv6 and offer DNS service via IPv6. On dual-stack (IPv4 and IPv6) boxes it talks both protocols and can even act as IPv6-to-IPv4 or IPv4-to-IPv6 forwarder.
Users can configure dnsmasq to send queries for certain domains to upstream servers handling only those domains. This makes integration with private DNS systems easy.
Dnsmasq supports MX records and can return MX records for any or all local machines.
Some internet service-providers rewrite the NXDOMAIN (domain does not exist) responses from DNS servers. This forces web browsers to a search page whenever a user attempts to browse to a domain that does not exist. Dnsmasq can filter these "bogus nxdomain" records out, preventing this potentially unwanted behavior.

External links

http://www.thekelleys.org.uk/dnsmasq/doc.html
"Dnsmasq". Freecode.
http://packages.debian.org/dnsmasq (debian package page)

@@ Line 35: / Line 35: @@
 * Users can configure dnsmasq to send queries for certain domains to upstream servers handling only those domains. This makes integration with private DNS systems easy.
 * Dnsmasq supports [[MX record]]s and can return MX records for any or all local machines.
-* Some internet service-providers (such as [[Rogers Communications]]) perform deep packet-inspection and rewrite the NXDOMAIN (domain does not exist) responses from DNS servers. This forces web browsers to a search page whenever a user attempts to browse to a domain that does not exist. [[VeriSign]] also did this to the .com and .net [[Top-level domain | TLD]]s with their [[Site Finder]] tool in 2003. Dnsmasq can filter these "bogus nxdomain" records out, preventing this unwanted behavior.
+* Some internet service-providers rewrite the NXDOMAIN (domain does not exist) responses from DNS servers. This forces web browsers to a search page whenever a user attempts to browse to a domain that does not exist. Dnsmasq can filter these "bogus nxdomain" records out, preventing this potentially unwanted behavior.
 == See also ==