Accessing Intranet Domains Over VPN

Notes on accessing intranet DNS/services over VPN: DNS split, hosts overrides, and resolver behavior.

Sep 22, 2019 · 2 min read · 314 Words · -Views -Comments · Software & Tools
Network Tools 🇨🇳 阅读中文版
Read with AI

Choose an AI assistant

ChatGPT Open in a new tab with the article link and prompt
Claude Copy the prompt, then open Claude

Open Claude
Trouble reading the article?

If the prompt is missing, copy the full prompt below into your AI assistant. If the AI cannot read the article, paste the visible passage you want to discuss and add your question.

Recently my SS proxy stopped working, so I switched to the company VPN. But intranet domain services stopped working.

So I started investigating.

Why intranet domains fail over VPN

To solve it, we must understand why intranet domains fail under VPN.

Take Google as an example. We send a request to the proxy, the proxy resolves the domain to an IP, then requests Google and returns the response. The problem is the proxy cannot resolve our intranet domain IP. So the key is: how do we prevent those requests from going through the VPN proxy?

The answer is the hosts file.

hosts file

The hosts file is a system file that maps hostnames to IP addresses. It can supplement or replace DNS. Unlike DNS, users can control the hosts file directly.

Open hosts and you will see a record like:

127.0.0.1 localhost

Developers know this well. We often access local web projects via localhost, which is a domain. If DNS cannot resolve it, why does it work? Because this record exists. That implies hosts has higher priority than DNS - yes.

hosts vs DNS priority

The hosts file is still kept in operating systems, and its priority is higher than DNS. The OS checks hosts first; if not found, it queries DNS.

Solution

Now we can add intranet domain IPs to hosts. I recommend the app iHosts. For me, I only need these host entries when VPN is on, so I use an app to group and toggle them.

Find domain IP

Run ping in terminal. The screenshot shows baidu’s public IP.

Private IP ranges

TCP/IP reserves three private address ranges:

  • 10.0.0.0/8: 10.0.0.0-10.255.255.255
  • 172.16.0.0/12: 172.16.0.0-172.31.255.255
  • 192.168.0.0/16: 192.168.0.0-192.168.255.255

Final Thoughts

Even without SS, the company’s stable VPN still allows me to use Google, so normal work and life are not affected.

References

Authors
Developer, digital product enthusiast, tinkerer, sharer, open source lover