@themac
I never needed bind to that.
The default pfSense settings - two lines to edit, did that for me :
[image: 1619695368684-a076c41b-fe60-4fd7-93cf-9f3df057119d-image.png]
And bang, now the entire network knows it's part of the domain name (see image).
And pfSense knows it's called pfSense.
Let's check :
[image: 1619695882056-677d863c-f0f6-409c-9dc1-78220815c2a5-image.png]
More checks :
[image: 1619695942263-ad0a06d3-8a8d-4799-953b-e1ba601a8c90-image.png]
I used a magic trick :
Didn't had to change anything on the Resolver setting page neither.
Use the default and you're good.
I tend to say : " don't break things if toy want it to work. "
Because I own (== I rent) this domain name, and because I do my own domain name server handling on a dedicated server some where on the Internet I can now do click-click install acme and hoppa, real trusted certs for me.
Free Dynds for all my devices with some more clicks.
( DNSSEC while you're at it - but this time the mouse will abandon you, a head, some brains and a keyboard are needed)
The name server uses bind ,of course.
But why role out the tank if you can wipe the bug with a bug wiper ?