Because of this, we have a tiered DNS system: if users try to access those internal tools, it first contacts the Private Route53 DNS, then it contacts
Code: Select all
1.1.1.1
For the vast majority of employees working here, this system seems to work. When we're connected to VPN & perform a request to, say:
Code: Select all
example.com/SpecialAdminTool
Code: Select all
192.192.192.192
However, two employees have been running into issues with this system for some reason--namely, they are unable to resolve the IPs in the private hosted zone only on their browsers (Chrome, Firefox, & Safari were tested). However, the weird part about this is when they perform an
Code: Select all
nslookup/dig example.com
We've tried clearing system cache, browser cache--everything, to no avail. We were wondering if anyone else has encountered the same issue and whether or not you've found a solution for this. This seems to be a client-side issue on the MacOS client, hence why I am posting it here.