Clients with dynamically-set network connections (DHCP clients) will communicate with both the authoritative DNS server and the DHCP server for updating A and PTR records.
The DHCP client will communicate with the authoritative DNS server directly for updating its A record, but the DHCP server updates the DNS server with the client’s PTR record In some cases, a DHCP server may update a client's A record on its behalf, even if the client did not specifically request this.
lease 192.168.1.25 lease 192.168.1.20 lease 192.168.1.21 lease 192.168.1.19 lease 192.168.1.23 lease 192.168.1.22 lease 192.168.0.244 lease 192.168.0.41 lease 192.168.0.243 lease 192.168.0.240 lease 192.168.0.242 lease 192.168.0.238 lease 192.168.0.75 lease 192.168.0.237 lease 192.168.0.236 lease 192.168.0.235 lease 192.168.0.234 lease 192.168.0.241 lease 192.168.0.239 And finally: Do you have any log entry in system logs about dhcpleases? Either you are on an old snapshot which had a problem with dhcpd.lease not present or you have tweaked your system. I AM .94 /usr/local/sbin/dnsmasq --local-ttl 1 --all-servers --dns-forward-max=5000 --cache-size=10000 --dhcp-hostsfile=/var/etc/hostsdhcpd 46822 0.0 0.9 3304 2104 ?? from the dnsmasq man page: DHCP host information from the specified file.
Hi, my pf Sense box hostname is "pfsense" and domain is "local" [[email protected]]/root(29): cat /etc/domain localnameserver 2X.46.237. X20 [[email protected]]/root(31): cat /var/etc/hosts 127.0.0.1 localhost localhost.local192.168.9.1 pfsense.local pfsense.169 pfsense.local pfsense Also, this may be the problem. Is AM .05 /usr/local/sbin/dhcpd -user dhcpd -group _dhcp -chroot /var/dhcpd -cf /var/dhcpd/etc/bridge0 Note: --dhcp-hostsfile=/var/etc/hosts . The file contains information about one host per line.
Indeed I was correct in that the php was never calling it in the first place.
Please see For a DHCP client, when some particular action causes its IP address to change, such as a DHCP lease renewal, if the client supports it, it will send Client FQDN information (DHCP option 81 flags) to the DHCP server.
The DHCP server will use this information, along with its dynamic update configuration, to determine whether or not the DHCP server will perform the PTR record update against the authoritative DNS server on behalf of the client, or if the client will perform the PTR update against the authoritative DNS server on its own. The first step of this process still involves the client machine sending an SOA-type query to the configured DNS server.
The roaming client forwards DNS queries listed in Internal Domains to the local DNS servers on the network.
As long as the Internal Domains are correctly populated, then any SOA queries for any internal-facing domains will be sent to the local DNS server.
nslookup from local machines works fine, as does ping.