Getting a little frustrated trying to resolve this issue and seeing a variety of proposed solutions that don't seem to work.
I have an FQDN that exists on my local network with an RFC1918 IP address and also exists on the public network with an address that is learned via dynamic dns. For the local resolution I run a pair of pi-holes that have static entries for my local devices and simply return the IP address for those names when they get a query. Unknown names are forwarded to CloudFlare.
This, for years, has allowed me to access this host either locally on my network or when travelling using the same fully qualified domain name.
Now, after updating two Macs to Ventura I am seeing strange behavior.
Mac #1 is an iMac and appears to be randomly bypassing local DNS when resolving this host name. I've tried the following things;
1. Verify private relay turned off.
2. Verify ip privacy turned off both on the local network setting and in Safari.
3. Tried coding the entry in /etc/hosts (bypassing DNS completely).
If I flush DNS cache and ping the host everything is fine. As soon as I try to access it with Safari I see in sniffer trace that Safari is insisting on doing a DNS 65 query to my pi hole which then redirects it to the public network where it is getting the dyn-dns provided IP as a response.
As mentioned, it seems to only be Safari that is causing the problem.
1. Connecting with the IP address works 100%.
2. Connecting from Chrome works 100%.
On Mac #2 (M1 Macbook pro) everything works.
I can't figure out what the discrepency is, since the settings on the two machines appear to be the same.
Any advice on resolving this would be appreciated.
I have an FQDN that exists on my local network with an RFC1918 IP address and also exists on the public network with an address that is learned via dynamic dns. For the local resolution I run a pair of pi-holes that have static entries for my local devices and simply return the IP address for those names when they get a query. Unknown names are forwarded to CloudFlare.
This, for years, has allowed me to access this host either locally on my network or when travelling using the same fully qualified domain name.
Now, after updating two Macs to Ventura I am seeing strange behavior.
Mac #1 is an iMac and appears to be randomly bypassing local DNS when resolving this host name. I've tried the following things;
1. Verify private relay turned off.
2. Verify ip privacy turned off both on the local network setting and in Safari.
3. Tried coding the entry in /etc/hosts (bypassing DNS completely).
If I flush DNS cache and ping the host everything is fine. As soon as I try to access it with Safari I see in sniffer trace that Safari is insisting on doing a DNS 65 query to my pi hole which then redirects it to the public network where it is getting the dyn-dns provided IP as a response.
As mentioned, it seems to only be Safari that is causing the problem.
1. Connecting with the IP address works 100%.
2. Connecting from Chrome works 100%.
On Mac #2 (M1 Macbook pro) everything works.
I can't figure out what the discrepency is, since the settings on the two machines appear to be the same.
Any advice on resolving this would be appreciated.
