server/user-documentation
10
3
Fork 8
Code Issues Pull requests 2 Projects Activity

Review of the dnsmasq documentation

Browse source
This commit is contained in:
Emmanuel Seyman 2026-05-14 08:06:12 +00:00
commit 2d4051b42a
1 changed files with 4 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

8
modules/ROOT/pages/administration/dnsmasq.adoc
View file

@ -22,7 +22,7 @@ The DHCP component provides dynamic DNS for a DHCP-assigned IP address, offering
Each dnsmasq component is optional. A system can use the DHCP component alone, the DNS component alone, the DHCP caching component alone, or any combination of these. Each component is configured separately.
The target is a small to medium-sized subnet. Typically, a server performs this task as an additional responsibility, alongside its main duties. It is practically impossible to determine the upper limit with any degree of accuracy. However, as a rule of thumb, dnsmasq can handle over 100 machines with ease. Significantly larger networks require better management and structuring capabilities. In this case, the __ISC DHCP Server__ would be a more suitable choice.
The target is a small to medium-sized subnet. Typically, a server performs this task as an additional responsibility, alongside its main duties. It is practically impossible to determine the upper limit with any degree of accuracy. However, as a rule of thumb, dnsmasq can handle over 100 machines with ease. Significantly larger networks require better management and structuring capabilities. In this case, Kea, the ISC DHCP Server would be a more suitable choice.
For additional information, see the _Fedora Magazine_ article https://fedoramagazine.org/using-the-networkmanagers-dnsmasq-plugin/[Using the NetworkManager’s DNSMasq plugin] (2019).
@ -64,7 +64,7 @@ The NetworkManager dnsmasq plugin included by default provides a basic configur
In case dnsmasq is not already installed
[source,]
----
[…]# dnf install dnsmasq
[…]# dnf install dnsmasq
----
[IMPORTANT]
@ -233,7 +233,7 @@ Allow ports for DHCP and DNS (53) service on the public interface.
[source,]
----
[…]# systemctl restart NetworkManager
[…]# ps -ef | grep dnsmasq
[…]# ps -ef | grep dnsmasq
----
+
NetworkManager should have started __dnsmasq__ shown by the '__ps__'
@ -338,7 +338,7 @@ This method is much clearer, improves maintainability and reduces sources of pot
== Integrate libvirt's virtual interface
In case libvirt and virtualization including a virtual network for the virtual machines, libvirt installs and configures its own dnsmasq instance. In most cases it is just convenient, instead of replacing the libvirt _default_ network to integrate it in NetworkManagers dnsmasq plugin. Thus, two instances of dnsmasq operate along each other.
To make it work, just add onother configuration file. The example uses libvirt.lan as the libvirt virtual network domain name. Adjust as appropriate.
To make it work, just add another configuration file. The example uses libvirt.lan as the libvirt virtual network domain name. Adjust as appropriate.
We just add the name resolution (DNS) for the libvirt virtual network (libvirt.lan), leaving the DHCP functionality untouched.