We earn commission when you buy through affiliate links.
This does not influence our reviews or recommendations.Learn more.
DNSmasq can be used to cache DNS requests for Linux distributions.
however, it can be a little challenging.
First Lets see what is DNS Caching.
What Is DNS Caching?
It may be compared to a telephone directory.
This is when DNS caching comes into play.
The DNS server is accessed whenever its necessary to resolve an IP address to a domain name.
A DNS cache is utilized so that decrease DNS requests and response times.
The resolved IP addresses along with host details are saved locally.
How does DNS caching help to fix intermittent DNS resolve issues on Amazon EC2 Instances?
The majority of Linux systems dont use a local DNS cache.
DNS resolution problems occur when there are a lot of requests.
Resolver makes recurrent lookups across public DNS servers for all additional web addresses.
It maintains a log of every existing and subsequent session.
This DNS cache makes the domain resolution easier and prevents errors with Amazon EC2 Linux instances.
Many users typically use Amazons Route 53 service for DNS when accessing AWS.
It is really easy to use and almost free.
But there are a number of reasons that could influence the users decision to use a local DNS server.
What is dnsmasq?
DNSmasqis a Linux-related tool that supports DNS, DHCP, TFTP, and DNS caching.
It is incredibly straightforward to install and configure.
so that set up DNS and DHCP for subnetworks, dnsmasq is a flexible and practical solution.
Dynamic and static DHCP options are both supported by dnsmasq.
It is portable and has the ability to manage DNS and DHCP for at least 1,000 clients.
Utilizing the dnsmasq tool instead of the browsers built-in DNS cache greatly enhances internet browsing performance.
Features of dnsmasq
Installation
Thesystemd-resolvedservice must be turned off prior to installing and configuring thednsmasqutility.
you could also conceal it using themaskattribute so that it wont start automatically when you reboot.
Installing dnsmasq is the initial action you should probably perform after turning off thesystemd-resolved.
DNSmasq comes pre-installed in almost all Linux distributions.
If not it’s possible for you to install it manually.
Launch a command terminal, and then punch in the following command to do it.
After successful installation, you could check the status ofdnsmasqby using the below command.
This will fix the error.
Default config file is located at/etc/dnsmasq.conf.
This config file must be modified to make it set updnsmasqutility in the system.
Use this command to open and edit the config file.
Let me briefly describe what each of the parameters means.
After performing all necessary changes, save and kill the config file.
And the next step is to edit the/etc/resolv.conffile to add the local host resolution address.
Use the below command to open with the nano editor.
Here, you might find all the nameservers your system uses for address resolution.
In that list, add the loopback address also.
Add nameserver 127.0.0.1 and keep it in the first line.
Save and exit the config file.
In order for the updated setting to take effect, restart the dnsmasq utility.
Testing Local DNS Caching server
Its easy to test the local DNS server.
Open a command line and use the dig command to check for DNS caching.
When you initiate the dig command for the first time, the result ought to be quite common.
Execute the very same dig command once more, and youll notice a significant decrease in the query time.
Here, the query time is 0 msec.
Restarting dnsmasq is necessary if you want to delete the stored DNS cache.
