Preface
Streaming services do not all use the same regional catalog, authentication system, or content delivery network. That is why a general-purpose Clash profile may open Netflix successfully but fail to load Disney+, play videos at reduced quality, or repeatedly ask you to verify your household. Sending every application through one proxy node is also inefficient: local websites, banking apps, software updates, and domestic services usually work faster through a direct connection.
A better approach is to build a dedicated streaming setup with targeted rules. Netflix and Disney+ traffic can be sent to a suitable proxy group, while local services remain DIRECT. With sensible DNS handling, stable node selection, and a clear rule order, you can reduce unnecessary latency and avoid accidentally routing unrelated traffic through an overseas server.
Configuration Goal
Route Netflix and Disney+ through an appropriate streaming group, keep local traffic direct, and make DNS behavior consistent with your selected proxy path.
1How Split Tunneling Works for Streaming
Clash split tunneling is rule-based traffic routing. When an application creates a connection, Clash examines the requested domain or destination IP and compares it with the rules in your profile. The first matching rule decides whether the request uses a proxy group, goes directly to the internet, or is rejected. This makes the order of rules just as important as the rules themselves.
For streaming, the practical objective is not to proxy everything. It is to identify the domains that control sign-in, catalog access, playback, subtitles, artwork, and telemetry. A streaming service may use several domain families, and its video files may come from a content delivery network rather than its main website. If only the homepage is proxied, the page may load while the actual video request fails.
Direct, proxy, and fallback behavior
- DIRECT: The connection uses your normal network. This is usually best for local websites, domestic applications, printers, operating-system mirrors, and services that do not require a foreign route.
- STREAMING: A dedicated policy group selects a node intended for Netflix or Disney+. Keeping this group separate makes testing and switching easier.
- PROXY: A general-purpose group for other international traffic. It should not automatically replace the streaming group because a fast browsing node may have an unsuitable region or blocked IP reputation.
- FINAL: The last rule catches traffic not matched earlier. Many users set this to
DIRECT, while others use a general proxy. Choose deliberately rather than relying on an inherited profile default.
Important Principle
A node that is fast for ordinary websites is not necessarily a good streaming node. Region, IP reputation, bandwidth, and support for long video sessions all matter.
2Designing Reliable Proxy Groups
Before writing domain rules, create a policy group that can hold several candidate nodes. In Clash Verge Rev or another Mihomo-based client, you can usually select the group from the proxy management screen. A group named STREAMING is easier to understand than placing individual server names directly in every rule.
The group should contain nodes from the regions supported by your account and the service you intend to use. Avoid assuming that a node labeled “US” or “Japan” will always provide the same catalog. Providers may move users between exit addresses, and streaming platforms can classify hosting-provider IPs differently from residential or ISP-assigned addresses.
Manual selection versus automatic testing
Manual selection is useful when you know which node has a stable history. It also lets you keep one node for Netflix and another for Disney+ if their regional requirements differ. Automatic URL testing is convenient, but a low latency result does not prove that a node can authenticate, load the catalog, or sustain a high-bitrate video.
Use health checks as a starting point, then verify the actual service. A practical group might look like this:
The exact node names are provider-specific, so replace the examples with names from your subscription. Keeping PROXY as a fallback can be useful, but placing DIRECT in the group should be intentional. Direct access may help with services that are available locally, but it will not solve a region restriction or an unavailable catalog.
Do Not Chase Speed Alone
A node can pass a generic speed test and still be blocked by Netflix or Disney+. Test sign-in and playback from the same device and network after selecting it.
3Writing Netflix and Disney+ Rules
Place specific streaming rules above broad rules such as GEOIP, RULE-SET, or MATCH. If a broad rule appears first, the request may be sent to the wrong group before Clash reaches your streaming entries. Keep the rules grouped by purpose so that future troubleshooting is straightforward.
Example domain rules
The following example demonstrates the structure rather than promising a permanent list of service domains. Streaming providers can change hostnames, and third-party rule providers may maintain more complete lists. Review your profile and update domain sets when a service changes its delivery infrastructure.
Do not add an overly broad rule such as DOMAIN-KEYWORD,video,STREAMING. It may capture unrelated video sites, advertising endpoints, meeting platforms, or software downloads. Similarly, routing every domain owned by a large technology company through the streaming group can create unnecessary delays because the same parent company may host unrelated services.
Rule providers and rule sets
If your client supports remote rule providers, a maintained streaming rule set can reduce manual work. Confirm that the syntax matches your core, whether the provider uses RULE-SET or a newer behavior-based format, and whether the list contains both domain and IP behavior. A rule set that is too broad can be worse than a short, transparent local list.
After changing rules, reload the profile instead of assuming that the editor saved every change. Then inspect the connection or request log. Look for the domain, the selected policy group, and the final node. This confirms whether the rule matched and prevents you from troubleshooting DNS when the real problem is rule order.
4Choosing DNS Settings That Match the Route
DNS is the step that converts a hostname into an IP address. Streaming services often use geographically distributed endpoints, so inconsistent DNS can send your request to a location that does not match your proxy exit. It can also expose local resolver behavior, produce stale results, or make a working node appear broken.
On a Mihomo-based profile, fake-ip mode is commonly convenient for rule-based routing because Clash can associate the requested hostname with an internal address and apply domain rules before the connection is established. Some devices, games, corporate networks, and special applications work better with redir-host, so treat fake IP as a useful option rather than a universal requirement.
This is a starting point, not a copy-and-forget solution. If your provider supplies DNS guidance, compare it with the profile. Some networks block encrypted DNS endpoints, while some applications use their own resolver or encrypted DNS settings and therefore bypass the behavior you expect from Clash.
- Use one consistent DNS strategy across the active profile and the operating system where possible.
- Disable browser secure DNS temporarily during diagnosis if it prevents Clash from seeing hostname requests.
- Clear browser and application DNS caches after changing the profile.
- Test IPv6 separately. If IPv6 is enabled locally but the proxy path does not support it correctly, playback may fail intermittently.
- Use the client log to check whether a request is resolved through Clash or directly by the operating system.
DNS Is Not a Catalog Switch
DNS can improve consistency and prevent mismatched resolution, but it cannot legitimately change an account’s licensing, payment region, household policy, or service availability.
5Hands-On Setup and Verification
Work through the configuration in small steps. Making several changes at once makes it difficult to identify whether the issue came from the node, DNS, rules, or the application cache.
- Back up the active YAML profile or duplicate it before editing. This gives you a known-good version to restore.
- Create or identify the
STREAMINGpolicy group, then add two or three candidate nodes with different routes. - Add the Netflix and Disney+ domain rules above general proxy, geographic, and final-match rules.
- Apply the DNS settings and reload the profile. Restart the Clash service if the client indicates that a core restart is required.
- Open the connection log, launch one service, and confirm that its requests match
STREAMINGrather thanDIRECTor a general group. - Test account sign-in, catalog loading, video start, subtitles, audio selection, and several minutes of playback.
- Switch to a second node and repeat the test. Record which node works reliably instead of judging only by a speed-test number.
For desktop clients, check both system proxy mode and TUN mode. System proxy mode covers applications that respect the operating system proxy settings. TUN mode can capture applications that ignore those settings, but it also affects more traffic and may require administrator permission. Enable only the mode you need, and verify that local printers, file shares, games, and corporate software still work afterward.
On mobile devices, background restrictions can stop the Clash service or disconnect it when the screen is locked. Allow the client to run in the background, exclude it from battery optimization when appropriate, and confirm that the operating system has not silently disabled the VPN profile. A streaming failure that occurs only after several minutes may be a power-management issue rather than a bad rule.
6Troubleshooting Playback and Region Problems
When the homepage loads but playback fails, first inspect the log for the video delivery domain. If it uses DIRECT, your rule set may be incomplete. If it uses STREAMING but still fails, change the node and clear the application session. Some platforms cache the result of an earlier connection, so testing in a private browser window can provide a cleaner comparison.
- Sign-in loops: Check that authentication, account, and content domains use the same intended route. Mixing direct login traffic with proxied playback can create inconsistent location signals.
- Proxy error messages: Try another node in the same region. The exit IP may be rate-limited, blocked, or shared by too many users.
- Low quality or buffering: Measure sustained throughput during playback, not only initial latency. A node with low ping may have limited evening bandwidth.
- Subtitles or artwork missing: Inspect related CDN requests and add narrowly scoped domain rules rather than routing every image or media domain through the proxy.
- Local sites become slow: Check the final rule and the position of
GEOIPentries. A broad proxy rule may be catching traffic that should remain direct. - Only one browser fails: Clear cookies, disable browser secure DNS for testing, and review extensions that provide their own VPN or DNS function.
Avoid repeatedly switching regions in a short period. Services may treat rapid changes as suspicious, and frequent account-session changes make troubleshooting less reliable. Select one suitable node, test methodically, and keep notes about the date, application, node, and result.
Frequently Asked Questions
Should Netflix and Disney+ use the same proxy group?
They can share a group when the same nodes consistently work for both services. However, separate groups may be better when the services require different regions or when one node is reliable for Netflix but blocked by Disney+. Start with one group for simplicity and split it only when testing shows a real difference.
Why does Netflix work while Disney+ does not?
The services maintain different domain lists, regional policies, and IP reputation systems. Check whether Disney+ requests are actually matching the streaming rules, then test another supported node. Also verify that your account, device region, and service availability are compatible with the route you selected.
Is fake-IP DNS required for streaming?
No. Fake-IP can make domain-based routing predictable, but redir-host or another DNS mode may be more compatible with a particular device or application. Use the mode recommended by your client and switch only after checking logs and reproducing the problem.
Can a Clash rule guarantee a specific catalog?
No. A rule controls how traffic is routed; it does not guarantee licensing, account eligibility, payment-region compliance, or a permanent catalog. Node availability and service policies can change, so use Clash for organized routing and verify that your usage follows the provider’s terms.
7Final Checklist for a Stable Profile
Before considering the setup complete, confirm that the active profile has a clearly named streaming group, rules placed above broad matches, and a final rule that reflects your real preference. Test both services from the same device, inspect the connection log, and confirm that ordinary local browsing remains direct. Keep a backup of the working YAML and document which nodes passed playback tests.
Streaming performance is a combination of routing accuracy, DNS consistency, node quality, application behavior, and service-side policy. A focused configuration is usually more stable than an oversized rule list that proxies every domain. Review it occasionally as services add new CDNs or your provider changes its node inventory.