Chapter 18. Using dnsmasq in NetworkManager to send DNS requests for a specific domain to a selected DNS server
By default, Red Hat Enterprise Linux (RHEL) sends all DNS requests to the first DNS server specified in the /etc/resolv.conf
file. If this server does not reply, RHEL tries the next server in this file until it finds a working one. In environments where one DNS server cannot resolve all domains, administrators can configure RHEL to send DNS requests for a specific domain to a selected DNS server.
For example, you connect a server to a Virtual Private Network (VPN), and hosts in the VPN use the example.com
domain. In this case, you can configure RHEL to process DNS queries in the following way:
-
Send only DNS requests for
example.com
to the DNS server in the VPN network. - Send all other requests to the DNS server that is configured in the connection profile with the default gateway.
You can configure NetworkManager to start an instance of dnsmasq
. This DNS caching server then listens on port 53
on the loopback
device. Consequently, this service is only reachable from the local system and not from the network.
With this configuration, NetworkManager adds the nameserver 127.0.0.1
entry to the /etc/resolv.conf
file, and dnsmasq
dynamically routes DNS requests to the corresponding DNS servers specified in the NetworkManager connection profiles.
Prerequisites
- The system has multiple NetworkManager connections configured.
A DNS server and search domain are configured in the NetworkManager connection profile that is responsible for resolving a specific domain.
For example, to ensure that the DNS server specified in a VPN connection resolves queries for the
example.com
domain, the VPN connection profile must contain the following settings:-
A DNS server that can resolve
example.com
-
A search domain set to
example.com
in theipv4.dns-search
andipv6.dns-search
parameters
-
A DNS server that can resolve
-
The
dnsmasq
service is not running or configured to listen on a different interface thanlocalhost
.
Procedure
Install the
dnsmasq
package:dnf install dnsmasq
# dnf install dnsmasq
Copy to Clipboard Copied! Edit the
/etc/NetworkManager/NetworkManager.conf
file, and set the following entry in the[main]
section:dns=dnsmasq
dns=dnsmasq
Copy to Clipboard Copied! Reload the
NetworkManager
service:systemctl reload NetworkManager
# systemctl reload NetworkManager
Copy to Clipboard Copied!
Verification
Search in the
systemd
journal of theNetworkManager
unit for which domains the service uses a different DNS server:journalctl -xeu NetworkManager
# journalctl -xeu NetworkManager ... Jun 02 13:30:17 <client_hostname>_ dnsmasq[5298]: using nameserver 198.51.100.7#53 for domain example.com ...
Copy to Clipboard Copied! Use the
tcpdump
packet sniffer to verify the correct route of DNS requests:Install the
tcpdump
package:dnf install tcpdump
# dnf install tcpdump
Copy to Clipboard Copied! On one terminal, start
tcpdump
to capture DNS traffic on all interfaces:tcpdump -i any port 53
# tcpdump -i any port 53
Copy to Clipboard Copied! On a different terminal, resolve host names for a domain for which an exception exists and another domain, for example:
host -t A www.example.com host -t A www.redhat.com
# host -t A www.example.com # host -t A www.redhat.com
Copy to Clipboard Copied! Verify in the
tcpdump
output that Red Hat Enterprise Linux sends only DNS queries for theexample.com
domain to the designated DNS server and through the corresponding interface:... 13:52:42.234533 tun0 Out IP server.43534 > 198.51.100.7.domain: 50121+ A? www.example.com. (33) ... 13:52:57.753235 enp1s0 Out IP server.40864 > 192.0.2.1.domain: 6906+ A? www.redhat.com. (33) ...
... 13:52:42.234533 tun0 Out IP server.43534 > 198.51.100.7.domain: 50121+ A? www.example.com. (33) ... 13:52:57.753235 enp1s0 Out IP server.40864 > 192.0.2.1.domain: 6906+ A? www.redhat.com. (33) ...
Copy to Clipboard Copied! Red Hat Enterprise Linux sends the DNS query for
www.example.com
to the DNS server on198.51.100.7
and the query forwww.redhat.com
to192.0.2.1
.
Troubleshooting
Verify that the
nameserver
entry in the/etc/resolv.conf
file refers to127.0.0.1
:cat /etc/resolv.conf nameserver 127.0.0.1
# cat /etc/resolv.conf nameserver 127.0.0.1
Copy to Clipboard Copied! If the entry is missing, check the
dns
parameter in the/etc/NetworkManager/NetworkManager.conf
file.Verify that the
dnsmasq
service listens on port53
on theloopback
device:ss -tulpn | grep "127.0.0.1:53"
# ss -tulpn | grep "127.0.0.1:53" udp UNCONN 0 0 127.0.0.1:53 0.0.0.0:* users:(("dnsmasq",pid=7340,fd=18)) tcp LISTEN 0 32 127.0.0.1:53 0.0.0.0:* users:(("dnsmasq",pid=7340,fd=19))
Copy to Clipboard Copied! If the service does not listen on
127.0.0.1:53
, check the journal entries of theNetworkManager
unit:journalctl -u NetworkManager
# journalctl -u NetworkManager
Copy to Clipboard Copied!