pfSense

Bug #5041

Updated by Chris Buechler about 9 years ago

I just noticed DNS pointer entries don't work for one of my pfSense installations. 

 It looks like the dhcpd.conf is generated wrong when the subnet is 192.168.0.0 
 In my example I set an option to update the DNS server and the pointer records don't show on the Windows DNS server (where it works with other installations). Checking the dhcpd.conf it has the following lines (192.168.0.7 is the DNS server) for DNS updates: 
 <pre> 
 } 
 ddns-update-style interim; 
 update-static-leases on; 
 zone testdomain.local. { 
	 primary 192.168.0.7; 
 } 
 zone 168.192.in-addr.arpa { 
	 primary 192.168.0.7; 
 } 

 The "0." is missing for the reverse lookup zone. It should be: 
 } 
 ddns-update-style interim; 
 update-static-leases on; 
 zone testdomain.local. { 
	 primary 192.168.0.7; 
 } 
 zone +*0.*+168.192.in-addr.arpa { 
	 primary 192.168.0.7; 
 } 

 Looks like this only affects networks with x.x.0.x 
 Another system (with the same configuration but different subnet 192.168.15.0/24) works well and the dhcpd.conf looks like this: 
 } 
 ddns-update-style interim; 
 update-static-leases on; 
 zone anothertestdomain.local. { 
	 primary 192.168.15.10; 
 } 
 zone 15.168.192.in-addr.arpa { 
	 primary 192.168.15.10; 
 } 
 </pre>

Back