pfSense

I couldn't reproduce it.

A hostname defined under System>General is pftest2.ipbgd.office

I made a host override record - aa.ipbgd.office pointing to the LAN IP address 192.168.10.2

Here is the content of the /var/unbound/host_entries.conf

local-zone: "ipbgd.office." transparent
local-data-ptr: "127.0.0.1 localhost.ipbgd.office" 
local-data: "localhost. A 127.0.0.1" 
local-data: "localhost.ipbgd.office. A 127.0.0.1" 
local-data-ptr: "::1 localhost.ipbgd.office" 
local-data: "localhost. AAAA ::1" 
local-data: "localhost.ipbgd.office. AAAA ::1" 
local-data-ptr: "192.168.10.2 pftest2.ipbgd.office" 
local-data: "pftest2.ipbgd.office. A 192.168.10.2" 
local-data: "aa.ipbgd.office. A 192.168.10.2" 

Here is what I get when I execute dig @127.0.0.1 -x 192.168.10.2

;; ANSWER SECTION:
2.10.168.192.in-addr.arpa. 3600    IN    PTR    pftest2.ipbgd.office.

It looks valid to me.

Danilo Zrenjanin wrote in #note-1:

I couldn't reproduce it.

A hostname defined under System>General is pftest2.ipbgd.office

I assume you mean the hostname? ;)

VERY interesting.

I made a host override record - aa.ipbgd.office pointing to the LAN IP address 192.168.10.2

Here are some additional differences between your test and mine. Perhaps one or more of these poke at the "real" issue?

1) I have ipv6 enabled. Thus, the start of my hosts_unbound is

• Same local-zone
• Same half-dozen localhost.* lines
• ipv6 entry and reverse for my hostname

PERHAPS that is the real bug! Because...

2) I have a host override record defined for my hostname! Without that, it doesn't exist at all for ipv4?!!

3) I also have many other host overrides defined, both pointing to my pfSense gateway (192.168.1.1 -- .2 and .3 are CARP IP's), and for other VLANs.