On Mon, Mar 9, 2020 at 2:14 PM Brian Dickson <[email protected]> wrote:
> > > On Mon, Mar 9, 2020 at 1:14 PM Eric Rescorla <[email protected]> wrote: > >> >> As I said, Chrome does its own name resolution and has for quite some >> time, using the resolvers configured into the system and then sending its >> own DNS packets. This used to be common practice in SIP softphones, but I >> haven't worked on one in quite some time. I'm not sure on what basis you >> claim iOS doesn't support this, as that's not my understanding. Can you >> provide a citation here? >> > > Sure. > > From > https://developer.apple.com/documentation/networkextension/dns_proxy_provider > > DNS proxy providers are only supported on supervised iOS devices. > > > (And the latter is described here: > https://support.apple.com/guide/apple-configurator-2/supervised-devices-apd9e4f64088/mac > ) > > So basically, the ability to use third party DNS is limited to managed > devices, corporate or education. > The only other exception is the one done via VPN services, which is a > different set of frameworks, IIUC. > (That's why 1.1.1.1 is a VPN app rather than just a resolver, I believe.) > Ah. I think we are talking about different things: - Yes, it seems like iOS does not officially support an app which provides DNS services for other apps (though apparently there is an unofficial way to do it via the VPN hooks) - Individual apps, however, are able to do their own DNS resolution via the obvious mechanism of sending their own UDP packets to port 53. -Ekr
_______________________________________________ dns-privacy mailing list [email protected] https://www.ietf.org/mailman/listinfo/dns-privacy
