dnsmasq is opensource software and is distributed under the terms of the GPL. dnsmasq supports static and dynamic DHCP leases and even BOOTP/TFTP for network booting of diskless hosts. It can serve the names of local hosts which are not in the global DNS, and its DHCP server integrates with its DNS server to allow hosts with DHCP-allocated addresses to appear in the DNS along with names configured either in each host or in its configuration file. dnsmasq solves this problem.ĭnsmasq is a small, lightweight, and easy to configure caching DNS proxy and DHCP server targeted at small or home networks. However, as the number of hosts on my network started to grow, configuring static IP addresses and constantly updating the host files became unwieldy.
This approach allowed me to easily communicate between these hosts by simply typing their name rather than trying to remember their static IP address.
In my home network I would typically assign a static IP address to each host on my network, and then use its host file to resolve the host’s name to the IP address it was assigned. So, why do you even need dnsmasq? Afterall, your ISP provides DNS and your home network gateway/router likely provides DHCP service for your network, right? Perhaps the best way to answer then is to explain the problem I was trying to solve. Once configured, you’ll be able to use dnsmasq to provide DNS and DHCP services in your home network. This post will describe how to install and configure dnsmasq on a Linux- or Unix-based host. Posted in Linux Tagged Linux, slitaz 24 Comments on Installing SliTaz Linux on a Hard Drive bookmark_border How to Install and Configure dnsmasq This led to the problem later when the GRUB device map did not agree with the GRUB configuration file.ĭespite the lack of some features in the SliTaz installer and the GRUB Error 21 problem, I found installing SliTaz Linux to be a fairly straightforward affair.
Even though it was the only hard drive attached to the system at the time of the install, the SliTaz installer erroneously assumed it was the third and designated it as /dev/hdc. What may have occurred was that my hard drive was attached as a master on the secondary EIDE slot on the motherboard. To fix this I simply changed (hd2,0) to (hd0,0) and I was back in business. As I suspected, the SliTaz installer assigned /dev/hdc1 to (hd2,0), a nonexistent drive and partition.