https://preview.redd.it/moomqy2xhfhh1.png?width=406&format=png&auto=webp&s=290290172fd54594b3702658500eba41c2df516d

Hi everyone,

I'm currently using the DPN App on Linux with Smart Route enabled.

I'm running version 3.0.5.260730. I believe this is the current version, although the download/update link shown on the website currently returns a 404.

I'm experiencing an intermittent issue that seems to be related to how Smart Route handles domain names and DNS resolution.

What I'm seeing

When I start the DPN App, sometimes everything works correctly. For example, if I access:

https://google.com

the Log Viewer shows something like:

google.com routed by DIRECT, actually via local direct link

In this case, the domain name is preserved and everything works as expected.

However, approximately 90% of the time, I see a different behavior.

For example, I'm trying to access a website behind Cloudflare:

http://atmxxx.pro:8080/

When DPN App/Smart Route handles the request, it appears to resolve the domain first and then route the request directly to the Cloudflare IP:

172.67.201.87:8080 routed by DIRECT, actually via local direct link

The problem is that the request is now being made against the Cloudflare IP address, rather than the original hostname.

As a result, the server returns:

[http @ 0x62e0feb72680] HTTP error 403 Forbidden

This makes sense from the Cloudflare side, because the request is effectively going to the Cloudflare IP instead of the original hostname, so the expected Host/SNI information may not be preserved correctly.

Interesting part

If I completely disable the DPN App, the exact same URL works normally:

http://atmxxx.pro:8080/

So the problem appears to occur only when DPN App is enabled with Smart Route or Full Route.

The behavior is also intermittent. Sometimes after restarting the DPN App, domain-based routing works correctly and I get:

google.com routed by DIRECT, actually via local direct link

But most of the time, Smart Route appears to resolve the hostname to an IP and then route the connection using that IP.

My questions

Could this be a bug in the Linux DPN App / Smart Route implementation, particularly related to DNS resolution or hostname preservation?

Or could there be something misconfigured on my side (DNS, routing, etc.) that is causing this behavior?

I have already submitted the application logs through the DPN App, but I haven't received a response yet.

If anyone has experienced something similar, or if someone from Deeper Network support can clarify how Smart Route is supposed to handle domain-based routing when the destination is behind Cloudflare, I'd really appreciate it.

Thanks!