It can be that this causes some problems, that's why the manpage of doesn't recommend the use of it.
If you experience problems, turn it off, but then you have to configure these hosts statically not only for DHCP, but also for DNS.
The default configuration not only wastes global Internet resources but also introduces a multitude of security, privacy and intellectual property concerns.
``So what if my host leaks a few packets to the global Internet? '' The reason is that inconsistent configuration between your home hosts and your local DNS servers can, and often does, cause leakage of DNS updates for private IP addresses to the global Internet.This leakage causes the following problems: Unfortunately, most users have no knowledge of their own misbehaving hosts broadcasting private information to the world.To configure this, just delete the line notify no;.Then you have to create two zone files, one for the forward lookup zone (db.example.org) and one for the reverse lookup zone (db.192.168.2).By default the DHCP-Server doesn't update the DNS entries of static leases.
If you want it to update them, you need to set this option to on.
The primary statement specifies the IP address of the name server whose zone information is to be updated.
In this case DHCP and DNS server are running on the same machine, that's why we put 127.0.0.1 there.
While this service can reduce administrative overhead, it also can, and does, have deleterious effects on the larger Internet by leaking traffic regarding private IP addresses that should never leave the local area network.
You do not need to disable dynamic DNS updates if: However, if you have configured your host to act as a DHCP client/server and you make use of the private IP address space (including 10.0.0.0/8, 172.16.0.0/12, and 192.168.0.0/16) specified in RFC1918, you should turn off the dynamic DNS update feature.
This information should not be forwarded to outside your network, unless you use public IP addresses.