You can connect to your VPN, but you can’t load internal resources by their fully...

If the VPN tunnel successfully connects but internal resources cannot be reached by their fully qualified domain names, DNS configuration is the most relevant area to examine. DNS translates hostnames and FQDNs into IP addresses. Apple’s VPN configuration documentation supports DNS server addresses, DNS search domains, domain names, and supplemental match domains for VPN connections, including split-DNS configurations. An incorrect DNS server, missing internal search domain, or incorrect match-domain configuration can allow the VPN itself to establish successfully while preventing internal hostnames from resolving. QoS affects traffic prioritization rather than hostname resolution. Screen Time has no role in corporate DNS resolution, and Fastlane restrictions do not address this symptom. Therefore, the DNS settings associated with the VPN connection should be reviewed first.

================