DHCP reports client lease, but DNS doesn't know about
|Affected version:||2.0.1||Affected Architecture:|
A client was assigned a lease, but the DNS server doesn't know about the client. It keeps not knowing about the client until the server is, at least, restarted.
#1 Updated by Jim P over 1 year ago
- Status changed from New to Feedback
Not enough detail here. Do you have a forum thread where this was discussed in more detail?
#2 Updated by Thomas Schweikle over 1 year ago
No, but details follow as soon as I have full access to the machine again (later this evening).
#3 Updated by Thomas Schweikle over 1 year ago
:~# host phai
Host phai not found: 3(NXDOMAIN)
:~# dig phai
; <<>> DiG 9.8.1-P1 <<>> phai
;; global options: +cmd
;; Got answer:
>>HEADER<< opcode: QUERY, status: NXDOMAIN, id: 20799
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;phai. IN A
;; AUTHORITY SECTION:
. 3544 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2012022100 1800 900 604800 86400
;; Query time: 2 msec
;; SERVER: 192.168.116.27#53(192.168.116.27)
;; WHEN: Tue Feb 21 12:45:59 2012
;; MSG SIZE rcvd: 97
:~# cat /etc/resolv.conf
pfSenses address is the dns-address entered, but the entered lease "phai" is never resolved until the dns-server on pfSense is restarted or reloaded ...
pfSense itself is configured to deliver dhcp assigned address mappings first, before going to static lists or accessing dns-servers within the internet.
#4 Updated by Jim P over 1 year ago
The real question is if the hostname is in /etc/hosts on the firewall when it does and does not resolve.
#5 Updated by Thomas Schweikle about 1 year ago
If it does not resolve the host is not entered into /etc/hosts, but visible within the web interface.
#6 Updated by Thomas Schweikle about 1 year ago
This may be an error known for version 2.55 as used by pfSense. This bug has been fixed later and shall be resolved with the latest version 2.60 as available for FreeBSD 8.x in ports "dns/dnsmasq". Some more info is available at "http://www.freshports.org/dns/dnsmasq/".
BTW: why not using dnsmasq for dns/dhcp/tftp? It is much more complicated to crop with dnsmasq, dhcpd, and tftpd ( --- all binaries together take up much more space than dnsmasq alone).
#7 Updated by Janne Enberg 10 months ago
I'm having the same issue in 2.0-RC1 with dnsmasq 2.55 .. it takes a long time (often several hours) for DHCP leases to be reflected to the DNS forwarder, can get them there instantly if I restart the dnsmasq service.
After a talk in ##pfsense, this is apparently not an issue for some 2.0.1 users, is there a fix for this already, and if not, when could we expect one?