dns66 icon indicating copy to clipboard operation
dns66 copied to clipboard

Published 20 hours ago • verified publisher icon julian-klode

Allow DNS servers on non-standard ports

Open julian-klode opened this issue 9 years ago • 7 comments
trafficstars

DNS66 should allow specifying DNS servers with non-standard ports. This would allow it to interact with a DNSCrypt proxy running on the device (which helps #11) without root being required to run the proxy.

julian-klode avatar Oct 26 '16 08:10 julian-klode

please make this available, custom dns port on dns server lists.

the reason is that my isp transparently intercept and redirect default dns port 53 to their own dns server, for their local advertising and blocking website they "deemed necessary".

i've tried to input the ip in format 208.67.222.222:5353 but dns66 crashing.

cubakcabak avatar Aug 12 '17 02:08 cubakcabak

any news on this?

michyprima avatar May 15 '18 17:05 michyprima

not yet

julian-klode avatar May 15 '18 17:05 julian-klode

I saw that overriding the port in DnsPacketProxy is enough to get it working (line 189) so we just need an UI implementation. I could do it and make a PR. Any guideline I should follow?

michyprima avatar May 15 '18 17:05 michyprima

It's a bit difficult. We could hack that in somehow by parsing ports in the address fields, but I'm not sure that's correct. and adding a separate port field is a lot more complicated, I'm afraid.

julian-klode avatar May 15 '18 19:05 julian-klode

As we want a port field for dns servers, but not for host files. Hence we have to split Configuration.Item into subclasses I think.

julian-klode avatar May 15 '18 19:05 julian-klode

Actually; this gets kind of weirder with the tls stuff in #11 - a DNS server could be

  • DNS via HTTPS
  • DNS via TLS
  • DNS

an each could have a port or not.

julian-klode avatar May 16 '18 19:05 julian-klode