I've had this issue for the past few weeks on my phone (could have been the OS update, but my life's been hectic), and just started on the Mac with the update to Ventura, so I'm guessing someone in Cupertino had a brilliant ideal.
this worked for years on both iOS and MacOS before the current versions.
I've got a PF sense router, a web server box on my network, and a dynamicDNS service (no-ip.com)
I set up Split DNS on the the PFsense, with a host override, so if I was on my internal network, my DDNS name would just send me to the internal IP of my server. Also use this for SSHing into the server.
that's all broken now
I can use dig or nslookup on my dynamicDNS name, and it returns the internal IP as it's supposed to
if I try to ping my DDNS name, it uses the external. When I use Safari or try to ssh into the server, it just hangs, so I'm assuming it's trying the external
dscacheutil -q host -a name ____ returns the external IP
And just for fun... For several years, I've been using a web app made with fluid app. (just an app that runs a single site browser) and that works like it's supposed to.
I've tried flushing the dnscache repeatedly (sudo killall -HUP mDNSResponder;sudo killall mDNSResponderHelper;sudo dscacheutil -flushcache) with no success.
I've also fooled around with DNS settings in pfsense, and no luck there either.
so either safari and ping among others are using some new "improved" system for DNS, or it's not really flushing, or something.
this worked for years on both iOS and MacOS before the current versions.
I've got a PF sense router, a web server box on my network, and a dynamicDNS service (no-ip.com)
I set up Split DNS on the the PFsense, with a host override, so if I was on my internal network, my DDNS name would just send me to the internal IP of my server. Also use this for SSHing into the server.
that's all broken now
I can use dig or nslookup on my dynamicDNS name, and it returns the internal IP as it's supposed to
if I try to ping my DDNS name, it uses the external. When I use Safari or try to ssh into the server, it just hangs, so I'm assuming it's trying the external
dscacheutil -q host -a name ____ returns the external IP
And just for fun... For several years, I've been using a web app made with fluid app. (just an app that runs a single site browser) and that works like it's supposed to.
I've tried flushing the dnscache repeatedly (sudo killall -HUP mDNSResponder;sudo killall mDNSResponderHelper;sudo dscacheutil -flushcache) with no success.
I've also fooled around with DNS settings in pfsense, and no luck there either.
so either safari and ping among others are using some new "improved" system for DNS, or it's not really flushing, or something.