Split DNS feature in Norton VPN service

[bjm]

@HEITOR

I have the need to use Norton VPN with my company VPN simultaneously.
The problem is that Norton forwards all DNS resolution requests to its own VPN DNS server, which is a problem because it does not know the internal server names of my company and cannot resolve them.
The solution, from what I have found, is to implement split DNS in Norton VPN or allow the client to set which DNS server they want to use as primary.
So I am creating this topic to suggest that Norton implement this, please.

Hello @HEITOR
Welcome to the Norton Community!

• We’d love your feedback!
• Product Suggestions

Respectfully, may I inquire – Why you have the need to use Norton VPN with your company VPN simultaneously?

++++++++++++++++++++++++++++++++++++++++++++++
fwiw ~ as per AI:

Feature Request: Split DNS / Running Norton VPN with Corporate VPN

You have accurately diagnosed the exact symptom of this problem. You are 100% correct that Norton intercepts all DNS resolution requests and forwards them to its own public servers, which naturally have zero visibility into your company’s private internal network layout.

However, while your diagnosis of the DNS roadblock is flawless, implementing Split DNS or allowing a custom primary DNS within Norton will not fix the underlying issue. DNS is just the phone book; once you bypass that hurdle, you will immediately crash into the structural limitations of running nested tunnels (“a tunnel inside a tunnel”) on a standard operating system:

• It’s a Routing War, Not Just a DNS Issue: Operating systems like Windows and macOS are built to handle exactly one primary network gateway. When you run Norton VPN and a corporate VPN simultaneously, both software clients aggressively fight for absolute control over your system’s routing table. Even if Norton allowed you to look up the correct corporate IP address via Split DNS, the two VPN protocols would still conflict when trying to route the actual data packets. This inevitably results in dropped connections, massive latency, or severe data loss.
• Conflicting Security Designs: Norton VPN is a consumer tool built on an “all-or-nothing” privacy rule, while your corporate VPN (such as Cisco Secure Client/AnyConnect or Palo Alto GlobalProtect) is a highly sophisticated enterprise security suite built on a “total control” rule. Enterprise clients are intentionally designed by IT administrators to enforce strict network monopolies. They actively scan your system’s memory and active network adapters. The moment they detect a commercial VPN like Norton attempting to manipulate network sockets or run an unauthorized secondary tunnel, they will flag the device as non-compliant and shut down the connection to prevent data leaks.
• Specialized Tools are Required: Successfully nesting or chaining VPN tunnels is possible, but it cannot be achieved by stacking automated applications on top of each other. It requires advanced, open-source networking tools (like raw OpenVPN or WireGuard configurations managed through custom virtual machines or specialized routers) where routing metrics and MTU sizes can be manually adjusted. Consumer-grade security suites simply aren’t built for this.

If your primary goal is to keep personal browsing private from your company’s network monitoring, the only reliable solution is physical separation: use your corporate VPN exclusively for work tasks, and handle personal browsing (using Norton VPN) on a separate personal device. Trying to force both clients to coexist on the same OS will inevitably lead to an unstable connection.

Running any two VPNs simultaneously is a recipe for chaos, regardless of the brand.

When you activate a single VPN, it fundamentally rewrites how your operating system talks to the outside world. It creates a virtual network adapter, changes your default internet gateway, and overrides your DNS settings.

If you introduce a second VPN, it tries to do the exact same thing to the exact same files. They end up in an immediate tug-of-war:

• The Packet Loop: Traffic gets sucked into VPN A, which tries to route it through VPN B, which then tries to push it back into VPN A. The computer gets confused, and data packets just end up spinning in a loop until they expire.
• The Disconnect Race: As each VPN client detects the other one trying to change the computer’s network settings, their built-in security features (“kill switches”) trip, causing both connections to repeatedly drop and reconnect.

Unless you are a network engineer manually configuring raw protocols (like WireGuard or OpenVPN) line-by-line inside virtual machines or specialized hardware routers, trying to run two commercial VPN apps at the same time will always be a frustrating, unstable mess!

AI sourced content may make mistakes