DNS and ISP provider
-
@Antibiotic
DNS over TLS? -
@viragomann Please check image above
-
@Antibiotic
Nothing there, but since you removed the settings, I don't know from there. -
-
-
@Antibiotic
If you are using a vpn you have to use the vpn gateways and not the WAN in forwarding so local DNS server will go out the VPN Gateways not the WAN and there will be no DNS leak.
Also in general setup usually you enter the DNS servers provided by Mullvad. I also select the gateways they will go out. Also in general settings use the default DNS Resolution Behavior. -
@The-Party-of-Hell-No Sorry I do not use forwarding
-
-
-
@Antibiotic
In my use of vpn services they all require forwarding, be turned on - as in turning on forwarding in the DNS resolver - there is a checkbox. In the outgoing interfaces, if you are running a vpn like Mullvad you should only highlight the vpn gateways and the local dns server. if the WAN is checked this will cause the dns leakage because your isp will see your dns requests. you want the dns requests to go out through the encrypted VPN tunnel. -
@Antibiotic
Without stating a DNS server in the general setup, you cannot enable DNS forwarding.Anyway, I saw a thread here, where an ISP blocked the DNS root servers.
Also the ISP can redirect DNS request to any server he wants, as long as you do not DNS over TLS upstream requests.
You can try this, however.Search for DoT servers and enter some into the general settings with their host names.
The host names are essential to get sure, that you're connected to the correct server (verifying the SSL cert).In the DNS resolver you have to enable the query forwarding + SSL and disable DNSSEC.
-
@The-Party-of-Hell-No If set outgoing interface to lpcal and mullvad in dns resolver internet not working at all
-
@Antibiotic said in DNS and ISP provider:
trying to understand how they are doing this, if me do not use them DNS
because they most likely are intercepting.. Its not difficult, there is a guide on how to do it on pfsense.. Do you not think isp could do such a simple thing.
Quick test just do the dig test to 1.2.3.4, if you get an answer your dns is being intercepting
[23.09.1-RELEASE][admin@sg4860.home.arpa]/root: dig @1.2.3.4 www.cnn.com ;; communications error to 1.2.3.4#53: timed out ;; communications error to 1.2.3.4#53: timed out ;; communications error to 1.2.3.4#53: timed out ; <<>> DiG 9.18.16 <<>> @1.2.3.4 www.cnn.com ; (1 server found) ;; global options: +cmd ;; no servers could be reached [23.09.1-RELEASE][admin@sg4860.home.arpa]/root:If you get a response your being intercepted, there multiple other ways to check, maybe they only intercept specific dns? etc.. but if you get an answer to that query its a smoking gun that upstream of where you doing the query from interception of dns is happening.
-
-
@johnpoz OK, than what to do?
-
@johnpoz said in DNS and ISP provider:
there is a guide on how to do it on pfsense
Could you please give a link? Because did not found any here
-
@Antibiotic
Outgoing Network Interfaces - you still have the WAN highlighted. I don't know if you have the mullvad Interface highlighted. Only the VPN interfaces should be highlighted. Sorry I was calling them gateways should have been using the corrrect terminology - interfaces. -
@The-Party-of-Hell-No Yea but me using vpn only for one interface also using other interface without vpn. But anyway after did forwarding to mullvad dns in general setting and set tls over dns. Outgoing IN DNS RESOLVER set to only local Inernet start working.
-
@Antibiotic
You are making progress - I have to post my own difficulties with DNS so I can try and resolve my own thinking.There are ways to make multiple openvpn interfaces and I am sure Mullvad allows this. If it is wireguard you can do that also - just not as easy.
When I made multiple openvpn interfaces I copied the first interface and just changed the "Server Host or Address" to another server provided by the vpn service and save.
Another thing if you want to use both mullvad DNS servers - in case one goes down - just add it as another DNS server. The only time you run into problems if you try to send it out the same gateway. if you do not specify a gateway it will allow you to add the second.
Not sure if this is correct - I wait to be corrected, By only selecting the pfsense dns server 127.0.0.1 if it cannot resolve there is no higher DNS server to refer to.
-
@viragomann said in DNS and ISP provider:
Anyway, I saw a thread here, where an ISP blocked the DNS root servers
Oh, this is answer for blocking, i think
