Host Overrides doesn't override

johnpoz

@sensei-two host overrides have zero to do with dhcp registrations. Registering dhcp can be problematic - because every time a dhcp is registered unbound restarts.

And when you created this host override, example.com wouldn't be a "host" override - that would be a domain override, host.example.com would be a host override.

$ dig @192.168.9.253 zzz.testdomain.tld

; <<>> DiG 9.16.34 <<>> @192.168.9.253 zzz.testdomain.tld
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 41165
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;zzz.testdomain.tld.            IN      A

;; ANSWER SECTION:
zzz.testdomain.tld.     3600    IN      A       192.168.1.100

;; Query time: 1 msec
;; SERVER: 192.168.9.253#53(192.168.9.253)
;; WHEN: Sat Jan 07 06:33:05 Central Standard Time 2023
;; MSG SIZE  rcvd: 63

sensei-two

@johnpoz

So you're suggesting me to uncheck those two options? ok

My purpose is to check if DNS redirection is working.

I set a host override entry this way:

and ran a nslookup in my client and got this
2023-01-07 13_44_04-Window.jpg

pfsense dns servers are 1.1.1.1 and 1.1.1.2
I set openDNS in the Windows machine.
So, It seems to be working to me , but I am anything but an expert so I might be missing something here.
Thank you.

johnpoz

@sensei-two I have no idea what you think is happening there.. but from what you posted you asked 208.67.222.222 directly.. Host overrides would never work like that.. For pfsense to return something you are changing you would have to be asking unbound on pfsense.

Are you redirecting/intercepting dns on pfsense so when asking any dns, it gets redirected to pfsense?

https://docs.netgate.com/pfsense/en/latest/recipes/dns-redirect.html

If that is the case - ok your host overrides can work. But if your just going to redirect what your clients use for dns anyway, why not just hand them pfsense IP in the first place?

registration of dhcp static (reservations) are fine - this does cause restart of unbound every time a lease is renewed or handed out, etc. Any dhcp reservations you have set are loaded when unbound starts.

pfsense dns servers are 1.1.1.1 and 1.1.1.2

So your forwarding in unbound, not resolving - setting dns in pfsense general means nothing to a client asking unbound for dns, unless you clicked on the use forwarding in the unbound setup.

sensei-two

@johnpoz

I already had set a NAT DNS redirection rule of course, as the article you linked says to do.
The override entry is just a trick to make sure that the rule is doing its job

johnpoz

@sensei-two ah ok..

Summer

@sensei-two did you solved?

I'm trying now with pfsense 23.05.1 but looking at host-overrides

Warning

Do not use DNS override functionality as the only means of blocking access to sites.

With DNS Forward (deprecated package) this feature was working fine, with DNS Resolver(unbound) seems to run fine too.

gig@robot:~# nslookup acciaio.internal
Server:		PFSENSELAN
Address:	PFSENSELAN#53

Name: acciaio.internal
Address: 192.168.22.3

Now my question is I can safely use this or should expect some side effect?

i.e. over OPENVPN I cannot resolve acciaio.internal, even if with on server Custom option: push "dhcp-option DNS LAN.LAN.LAN.DNS"

johnpoz

@Summer said in Host Overrides doesn't override:

Warning

There is a warning because dns overrides only work if the client is using pfsense as its dns, what if using other dns, what if using doh in their browser. etc...

dns filtering of any kind is only good if the client can not use any other form of dns. Even then - maybe they will just go to the IP directly.

It states the reason why it might not work - right there in the article

Summer

@johnpoz thanks for clarification, that's ok.

I'm trying from a OVPN client:
checked on ovpnconnect log the DNS is pfsense but:

gig@robot:~# nslookup acciaio.internal
Server:		8.8.8.8
Address:	8.8.8.8#53

Name: acciaio.internal
** server can't find note.tb: NXDOMAIN

could it be Android issue that goes to google instead to pfsenseDNS?

gig@robot:~# nslookup PFSENSEDNS - acciaio.internal
Server:		PFSENSEDNS
Address:	PFSENSEDNS#53

Name: acciaio.internal
Address: 192.168.22.3

johnpoz

@Summer said in Host Overrides doesn't override:

could it be Android issue that goes to google instead to pfsenseDNS?

If your openvpn client isn't asking pfsense dns - then no its not going to be able to resolve stuff that is in pfsense dns only.

If your client is trying to use some other dns, make sure all traffic flows through the vpn, and do dns redirection.

Gertjan

@Summer said in Host Overrides doesn't override:

could it be Android issue that goes to google instead to pfsenseDNS?

You've created a host override @pfsensation
Then an android comes into play - and now, you tell me : you did't know that android always phones to home = uses 8.8.8.8 ?
Anyway, this android uses 8.8.8.8 as it DNS source.
With other words : this android connects to 8.8.8.8 and does the DNS requests.
This means that pfSense will never see/smell/be aware of this DNS request.
So you can place whatever host override on pfSense what you want, it doesn't matter.

For host overrides to work in such a situation, make a list of them, call Google (8.8.8.8) and give them your host override list.
This is a joke of course.

edit :
Let me rephrase the subject :

Host Overrides (registred on pfSense) doesn't override (when the LAN device uses another DNS like 8.8.8.8

Get it ?

Summer

@Gertjan said in Host Overrides doesn't override:

Host Overrides (registred on pfSense) doesn't override (when the LAN device uses another DNS

That's fine but how can it be changed that DNS?

If client get in it's log:

[dhcp-option][DOMAIN][internal]
[register-dns]
[redirect-gateway][def1]

And on server:

Gertjan

@Summer

I have :

[Aug 25, 2023, 15:45:55] OPTIONS:
0 [dhcp-option] [DOMAIN] [bhf.net]
1 [dhcp-option] [DNS] [192.168.3.1]
2 [block-outside-dns]
3 [register-dns]
4 [redirect-gateway] [def1]
5 [route-gateway] [192.168.3.1]
6 [topology] [subnet]
7 [ping] [10]
8 [ping-restart] [60]
9 [ifconfig] [192.168.3.2] [255.255.255.0]
10 [peer-id] [0]
11 [cipher] [AES-256-GCM]
12 [key-derivation] [tls-ekm]

Server side :

and I've set the DNS as :

and, unbound listens on "All" interface, which includes my "OPENVPN" interface (which uses 192.168.3.1/24 - which is the tunnel) :

A test on my Phone, connected uing the OpenVPN Client app :

as you can see, it uses 192.168.3.1 as it's DNS. That unbound. And unbound knows about my host overrides.

Lets that : I create a very special host name :

I pre test that AAAABBBBCDDDDDEEEEE.bhf.net on my pfSense LAN connected PC :

Microsoft Windows [version 10.0.22621.2215]
(c) Microsoft Corporation. Tous droits réservés.

C:\Users\Gauche>nslookup AAAABBBBCDDDDDEEEEE.bhf.net
Serveur :   pfSense.bhf.net
Address:  2a01:cb19:907:a6dc:92ec:77ff:fe29:392c

Nom :    AAAABBBBCDDDDDEEEEE.bhf.net
Address:  1.2.3.4

So, that works.

Now my Phone :

1.2.3.4 also.

Now : your turn.

johnpoz

@Summer if you have some app or browser or whatever on your phone that is wanting to use some hard coded dns.. and not doh like in a browser. One way to work around that could be dns redirection.

So if your phone insists on using 8.8.8.8 for example - you could on pfsense do a dns redirection so when it tries to talk to some dns, you redirect it to use unbound on pfsense.

https://docs.netgate.com/pfsense/en/latest/recipes/dns-redirect.html

Summer

Thanks @johnpoz you've made it!
Finally it works!

SteveITS

@Summer You may also want to block DoH, where (many) browsers bypass DNS to connect out to their DNS over HTTPS service. This page has a pfSense PDF that is very detailed but thorough.
https://github.com/jpgpi250/piholemanual#doh