Non standard port for Upstream DNS

Feature Requests Implemented
1

I know DNS exclusively uses port 53 pretty much. But it would be VERY useful if there were some way to enter a custom Upstream DNS Server with a specific port number. Let me explain why.

My ISP (Sky TV in the UK) employs a transparent DNS cache. Meaning they intercept all outgoing DNS requests (port 53 intercepting, I tested this by running an OpenVPN server on my VPS on port 53 UDP, I couldn't connect, but I could connect when using another internet connection) no matter what the destination is and proxy them. This is troublesome for DDNS which I use a lot. It dramatically increases the latency of any changes made to the DDNS records which causes me problems. Not to mention the privacy concerns; and well, I just don't like it !

I have Pi-Hole running on my network, but of course, its upstream requests are still going to be proxied by my ISP. So my solution to this would be to set up my remote VPS with a DNS server running on a custom port. Then if I could set this as an upstream DNS server in Pi-Hole using the custom port, I could bypass the ISP cache as all upstream requests would not be occurring on port 53 and my ISP would ignore them.

Just a thought. Thanks for reading this.
Cheers
Marc

2

If I'm understanding the request, you can already do this:

https://docs.pi-hole.net/guides/unbound/#configure-pi-hole
RecursiveResolver

2 Likes
3

Well, don't I feel the i***t?
My apologies for my ignorance. And many thanks.

4

I've opened an issue for noting on Custom DNS that other ports may be used.

2 Likes
5

Hello,
for me, it does not accept the #. I just cannot type it.
It just accepts numbers.
Even when editing setupvars manually (127.0.0.1#5354) in the web-interface this turns into 127.0.0.153.
I am using pihole f38c65d78a67 (docker:latest)

Greetings,
Hendrik

6

Ok, got it. pi-hole was to-late, as I was using diginc/pi-hole instead of pihole/pihole. The first was not being updated anymore.