Since upgrading to iOS 17, I’ve seen I am not in a position to go to my dwelling server from my dwelling community when in Personal Searching Mode in Safari.
I am pretty positive that the difficulty is that Safari is doing DNS lookups otherwise in Personal Searching Mode. The server I am attempting to connect with (name it www.instance.com) has a non-public IP tackle on my dwelling community. My router (which has a public IP tackle), is configured to port-forward port 443 from the general public IP to my dwelling server, so I can entry it after I’m not dwelling. Nonetheless, port forwarding does not work for shoppers on the house community.
Due to that, my router (which gives DNS for my dwelling community) is configured to return the server’s personal IP tackle for www.instance.com, as a substitute of the general public IP tackle which is returned by wanting up www.instance.com within the public DNS. Due to this fact, shoppers on my dwelling community attempting to connect with https://www.instance.com use the personal IP tackle, and every thing works.
This all labored tremendous on iOS 16. On iOS 17, https://www.instance.com works tremendous in regular searching mode. However in Personal Searching Mode, it seems to be attempting to make use of my public IP tackle as a substitute of the personal tackle. I can inform as a result of I get a nasty certificates warning, and the certificates is the one my router makes use of for its administration console.
What DNS servers does Personal Searching Mode use, and is there a setting I can change to make it use the community’s default DNS as a substitute?
I’ve seen that if I exploit a hostname that isn’t discovered within the public DNS, then it does appear to fall again to my community’s DNS server. However that is not likely handy for my use case. I need to have the ability to entry the server at dwelling or away utilizing the identical hostname.
