Potential DNS Rebind attack detected on my local network

comet424

@stephenw10
ok so remove the host and domain override.. i did the domain and pointed it to 192.168.0.1 so it would do all local hostnames least thats how i thought

what about that private-domain i added too how does that work?

as for ubuntu and dig command these are the screen shots
i thought once u tell dhcp dns is 192.168.0.1 all OSs would be resolved by pfsense

johnpoz

@comet424 that is not what he meant by a dig..

dig tardis.home.arpa

Your linux is using a local cache, that is why it points to127.0.0.53, if you want to know where that points.

user@UC:~$ resolvectl status
Global
       Protocols: -LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
resolv.conf mode: stub

Link 2 (ens3)
    Current Scopes: DNS
         Protocols: +DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
Current DNS Server: 192.168.3.10
       DNS Servers: 192.168.3.10
        DNS Domain: home.arpa
user@UC:~$

Private-domain sets a domain so that if you forward for that domain it will turn off rebind protection

You are making this so freaking difficult.. Out of the box dhcp will hand out the domain is set in general setup, ie home.arpa for example.. Your client may or may not use that..

When you query for dns, it has to be fully qualified, so either query the fqdn - ie tardis.home.arpa or make sure your client is using search suffix and will auto add it for you.

comet424

@johnpoz
sorry not trying to make it complicated.. all i thought is once you set it up in pfsense under dhcp server
your gate way and dns.. then pfsense did all the resolving of the local hostnames for any operating system.. i not familar with ubuntu alot so i just noticed i cant ping ill have to look up what a fqdn is

and all i want is once dhcp server shells out the ip then it doesnt matter what os... just be able to ping and access by the hostname in the arpa table so whatever i have to do to make it auto work like it auto works in unraid and windows.. but then you mention windows does its own thing

as for the dig and resolvectl this is the result

stephenw10

Try: dig @192.168.0.1 tardis.home.arpa.

In that example:

tardis is a hostname

home.arpa is a domain

tardis.home.arpa is a fully qualified domain name (fqdn).

johnpoz

@comet424 did you leave that domain forward in there - that is pointless, and prob going to break it.

Unless your register dhcp or static reservations. Unbound doesn't have a clue about other hosts you have on your network.

So you would either need to do one of those or both, and or just create a host override..

is 192.168.0.1 pfsense IP? Or some other NS?

Unbound wouldn't normally return a SOA like that.

comet424

@johnpoz
so i removed that domain and host override yesterday... only thing for domain i left i guess i should remove is

server:
private-domain: "home.arpa"

i can delete that

192.168.0.1 is pfsense 192.168.0.3 is the tardis
so host overide.. so i have to manaully enter then 200+ ips for ubuntu to be able to access them then ? like i always though under the ARP table the host name you could always ping or access the device by the hostname thats how i do it in unraid or windows like my 30+ ESP devices or all my IOT devices just access them by the Hostname through windows browser or ssh etc..

what is a SOA?

@stephenw10
this is the result of the dig @192.168.0.1 tardis.home.arpa.

johnpoz

@comet424 SOA is a record saying hey have no record of that - you should prob go ask the SOA (source of authority).. Out of the box unbound wouldn't return that record.. you would of had to create it.

If in the default transparent mode and you ask for anything.home.arpa and there is no record it would try and resolve it upstream, and that wouldn't return that soa either.

for home.arpa that you tried to resolve and had no record of and got sent upstream the soa would be

;; QUESTION SECTION:
;fsljfdsdf.home.arpa.           IN      A

;; AUTHORITY SECTION:
home.arpa.              3600    IN      SOA     prisoner.iana.org. hostmaster.root-servers.org. 1 604800 60 604800 604800

what do you have in the custom box of unbound? Do you have some host overrides setup.. domain overrides? unbound would not return that nobody soa

stephenw10

@comet424 said in Potential DNS Rebind attack detected on my local network:

@stephenw10
this is the result of the dig @192.168.0.1 tardis.home.arpa.

Sorry that last . was outside the quote! Muscle memory forced me to type it.

The command should be:

dig @192.168.0.1 tardis.home.arpa

johnpoz

@stephenw10 that wouldn't matter, and dig does it by default anyway unlike nslookup

stephenw10

Given the presence of Nord and PIA do you have Unbound in forwarding mode to other upstream servers over the VPN?

None of that should matter though, Unbound should still respond with hostoverrides in place.

comet424

@stephenw10
@johnpoz
so for custom options in dns resolver i have

server:
local-zone: "windowsupdate.com" redirect
local-data: "windowsupdate.com 86400 IN A 192.168.0.32"

server:
local-zone: "microsoft.com.edgesuite.net" redirect
local-data: "microsoft.com.edgesuite.net 86400 IN A 192.168.0.32"

server:
local-zone: "update.microsoft.com" redirect
local-data: "update.microsoft.com 86400 IN A 192.168.0.32"

server:
local-zone: "do.dsp.mp.microsoft.com" redirect
local-data: "do.dsp.mp.microsoft.com 86400 IN A 192.168.0.32"

server:
local-zone: "dl.delivery.mp.microsoft.com" redirect
local-data: "dl.delivery.mp.microsoft.com 86400 IN A 192.168.0.32"

server:
local-zone: "cdn.blizzard.com" redirect
local-data: "cdn.blizzard.com 86400 IN A 192.168.0.32"

server:
private-domain: "home.arpa"

server:include: /var/unbound/pfb_dnsbl.*conf

my host over ride is

the
dig @192.168.0.1 tardis.home.arpa command without the extra .

dns resolver i set to all all so i can then do the bypass routing policy on Lan

i disabled NordVPN and switched over to PIA they do different things... like no proper video for PIA but one had NAT just 192.168.0.0 and another used the pia for 1::128 and those other generated in NAT table so i dubbed them like i read in a PIA setup tutorial.. its like there is different ways to set up there vpn..

i dont use the DNS forwarder... as it wasnt part of the setup of PIA or norvpn in the past.. and i think i read or watched you cvan have dns resolver and forwarder same time?

only other VPN i use is Site to Site to my sisters Pfsense so i can access her network like it was here.. and i have to re add remote access...

and this is my LAN rules

any other screen shots you need..

johnpoz

@comet424 said in Potential DNS Rebind attack detected on my local network:

server:
private-domain: "home.arpa"

that is not needed, like I said that tells unbound hey if I forward home.arpa to some other NS or get an answer from some other ns and the answer is rfc1918 its ok.. But in no scenario that I can think of should that soa be returned for anything in home.arpa domain - unless you created the local record for it.

Or your forwarding to some other NS that has that soa setup or returns that soa for its local records... Unbound sure and the hell does not do that out of that box.

; <<>> DiG 9.16.50 <<>> @192.168.9.253 home.arpa SOA
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 31045
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;home.arpa.                     IN      SOA

;; Query time: 0 msec
;; SERVER: 192.168.9.253#53(192.168.9.253)
;; WHEN: Sat Nov 23 12:36:13 Central Standard Time 2024
;; MSG SIZE  rcvd: 38

You can see there is no SOA record for home.arpa That tells me unbound is asking something else for home.arpa - or your client isn't actually asking unbound. Or you have a local-data record setup your not showing. You don't have bind package running do you on pfsense?

And if you did ask the public internet for home.arpa or any normal NS on the public internet for something in home.arpa it should return that prisioner soa, because home.arpa has been set aside for private local use only.

Also that you would ever get back a rebind tells me unbound did not return what it had in its local records.. But asked/forwarded to someone else.. A rebind is when unbound asks some other NS and the answer is rfc1918.. That is by definition a rebind.

comet424

@johnpoz ok ill remove that server private domain then
as for NS thats Name Server right...
and only dns is pfsense minus 192.168.0.32 but thats the lancache for Windows updates and some games.. as my internet is only like 2 megabit and pay 100 bucks a month for internet thats not always stable.. but thats the only DNS stuff i setup

now the only local data setup i setup i guess is under the dhcp server i set static IPs like tardis.. but i set the Tardis hostname and ip of 192.168.0.3 and the DNS 192.168.0.1 and gateway of 192.168.0.1 so i dont do anything fancy

do you need a full display of NAT table.. or my PIA vpn right now i disabled the Nordvpn interface so i was able to shut off the openvpn client...

but ill remove the private domain and do a reboot of pfsense so its fresh.. i sometimes find pfsense works better after a reboot

comet424

and i thought i was good everything was find after i changed the general to the home.arpa

and i was able to ping again from Windows and unraid so i thought i was good

but then noticed i couldnt do it from ubuntu or raspberry pi

also i cant ping "tardis" from pfsense ping doesnt allow me there but i was sure i used to be able to

stephenw10

You are forwarding requests to whatever DNS servers you have set in System > General Setup via whatever gateways are set there.

But more importantly you don't appear to have any DHCP registration options in the Resolver. So either you are running 24.03 with Kea or pfSense is not the DHCP server on your network?

comet424

@stephenw10
pfsense is the dhcp server for all my vlans and lan
the general tab

i have it set for kea

i do not know what 24.03 is if thats pfsense version no i not running that version must be new
i only have 2.7.2
i looked under dns resolver under the 3 tabs didnt find a registration option

stephenw10

Ah Ok. In that case DHCP registration in the DNS server was not available in Kea at that point. If you switch back to ISC you can enable that and can then resolve other clients by hostname.

comet424

@stephenw10 so i flipped back to the ISC and enabled the dns registration... nothing happened so i rebooted everything pfsense switchs computers..
i still only can ping tardis from windows or unraid

ubuntu, raspberry pi,. and pfsense cant ping hostnames

and since ithe ISC is being depreciated the features in KEA will it get the ISC features when it gets released? like the hostname resolving you mentioned

stephenw10

Yes it's in the upcoming 24.11 Plus release.

But pfSense itself should certainly be able to resolve them if they appear in the DHCP leases table.

comet424

@stephenw10 maybe by morning it fix itself will see if not its werid as i can "ping pfsense" from ubuntu and it does it ok but i cant ping tardis and pfsense i cant ping either tardis or any local hostnames

is that a rule order issue or conflicting nat and not sure what 1:1 nat is really