VLESS + TLS with the DNS resolver Direct

The DNS resolver looks up the name of each connection on the phone before routing. Direct asks the listed DNS server straight from the phone, outside the VPN, so our DNS test server must hear the questions from the phone's network.

VERIFIED — TESTED SUCCESSFULLY  Tested on 10 November 2026 on the current app build against WaterWall 1.5.42, the official release, unchanged.

Result

OutcomePassed: every check succeeded.
Test length96 seconds
Downloaded2,030 MB (169 Mbit/s on average)
Transfers121 downloads of 16 MiB; 4/4 streams finished at the end
Errorsnone
Timeouts0
DNS questionspassed: our DNS test server got 10, 10 from the phone's network and 0 from the WaterWall server; the test site's name was among them
Through the tunnelYes: the HTTPS test server saw these transfers come from <SERVER_IP>, and it would have seen the phone's own network if they had left outside the tunnel
HTTPS check through the tunnelPing: 223 ms; Ping: 133 ms
UDPpassed: 900 datagrams sent and 900 echoed back in 95 seconds; round trip 44 ms on average, 603 ms at most

Test setup

PhoneiPhone 12 with iOS 27.2 (build 24B119), on Wi-Fi
AppSRP VPN Connect 1.2.0 (build 41), a Release build of commit e69cb668, installed by Xcode for the test. TestFlight build 41 is commit e44cf11d, with the same app code: the commits after it change only the tests and the change log
Server machineUbuntu 24.04.5 LTS, VMware virtual machine with 2 vCPUs and 2 GB RAM
Server programThe official WaterWall 1.5.42 release program, unchanged, the same program as our permanent test server, run as a separate test copy for each case
Server DNS lookups5 tries, WaterWall 1.5.42's default; the test copy's core.json does not set it
Server port4097, opened in the firewall only for our office address while the case ran
TrafficAn HTTPS test server on the same machine, port 28483, that serves a 16 MiB file and checks each upload. On Raw IPv4 and native WireGuard chains the phone reaches it at the server's private address 10.44.0.1, because iOS sends traffic for the server's own public address outside the tunnel; the test then trusts its certificate by comparing it with a copy, since the name in it is not that address
NetworkOur office broadband line, over the public internet
UDP echoA UDP echo server on the same machine, port 28481. The GeoIP case, whose UDP leaves outside the tunnel, used the test harness's own echo on port 28482 instead, opened in the firewall only for our office address while the case ran
DNS test serverA DNS forwarder on the same machine, UDP port 28453, that answers each question by asking 8.8.8.8 and logs the address each question came from. The profile's DNS Servers row named it; it was opened in the firewall only for our office address while the cases ran
GeoIP referenceAn HTTPS server on the same machine, port 28480, that logs the address each download comes from
iPhone 12 with SRP VPN Connect
      |
      |  Wi-Fi, office broadband, internet
      v
Test server <SERVER_IP>
  WaterWall test copy, port 4097           the chain under test
      |
      |  inside the same machine
      v
  HTTPS test server, port 28483            download file
  UDP echo server, port 28481              UDP check
  HTTPS reference server, port 28480       GeoIP case
  DNS test server, UDP port 28453          where the resolver's questions come from

With GeoIP direct routing, downloads from the reference server go straight from the phone
to port 28480, without WaterWall.

Server configuration

The test harness wrote this file for the case and started our WaterWall program with it. It is shown as it ran; only the server address, the UUID and the passwords are replaced with placeholders. The certificate files are a self-signed test certificate made for the run. On your own server, use your own port, certificate and secrets, as described in Installation.

{
  "name": "dns-resolver-direct-peer",
  "nodes": [
    {
      "name": "listener",
      "type": "TcpListener",
      "settings": {
        "address": "<SERVER_IP>",
        "port": 4097
      },
      "next": "tls"
    },
    {
      "name": "tls",
      "type": "TlsServer",
      "settings": {
        "cert-file": "/tmp/srp-device-matrix/cert.pem",
        "key-file": "/tmp/srp-device-matrix/key.pem",
        "verbose": true,
        "select-alpns": [
          "http/1.1"
        ]
      },
      "next": "vless"
    },
    {
      "name": "vless",
      "type": "VlessServer",
      "settings": {
        "uuid": "<UUID>",
        "verbose": true
      },
      "next": "out"
    },
    {
      "name": "out",
      "type": "TcpUdpConnector",
      "settings": {
        "address": "dest_context->address",
        "port": "dest_context->port",
        "dns-behaviour": {
          "resolve": true,
          "strategy": "prefer-ipv4"
        },
        "nodelay": true
      }
    }
  ]
}
The test copy's core.json
{
  "misc": {
    "workers": 1,
    "ram-profile": "minimal",
    "splice": false,
    "try-enabling-bbr": false,
    "tcp-tune": false
  },
  "configs": [
    "/tmp/srp-device-matrix/peer.json"
  ]
}

App settings

On the WaterWall configuration screen:

RowValue
ModeChain
InputConnections
ApplicationVLESS
MUXOff
ObfuscatorOff
HTTPOff
BGP4 FramingOff
OuterTLS
CarrierTCP
ResolverDirect
AddressesDefault (IPv4 First)
DNS Servers<SERVER_IP>:28453

In the profile editor:

Server<SERVER_IP>, the test server's address
Port4097
SNI (optional)localhost, for chains with TLS, Reality or QUIC
TLS Server VerificationOff, because the test certificate is self-signed
UUID or Password<UUID>, a test value
Reality or AEAD Password<OUTER_PASSWORD>, a test value, when the chain uses one
Auto ReconnectOff, so that a reconnect cannot hide a failure
On SleepStay
Log LevelNormal
Remote DNS (Fake IP)On
Direct LAN RoutingOn
The client chain the app built (for reference)
{
  "name": "VLESS + TLS",
  "nodes": [
    {
      "settings": {},
      "name": "ne",
      "type": "NEPacketDevice",
      "next": "ptc"
    },
    {
      "settings": {
        "max-total-pending-bytes": 16777216,
        "mtu": 1420,
        "fake-dns": {
          "address": "198.18.0.2",
          "netmask": "255.192.0.0",
          "enabled": true,
          "port": 53,
          "ttl": 60,
          "cache-size": 10000,
          "network": "100.64.0.0"
        },
        "max-pending-bytes": 65536
      },
      "name": "ptc",
      "type": "PacketsToConnection",
      "next": "resolver"
    },
    {
      "settings": {
        "port": "dest_context->port",
        "address": "dest_context->address",
        "protocol": "dest_context->protocol",
        "uuid": "<UUID>"
      },
      "name": "vless",
      "type": "VlessClient",
      "next": "tls"
    },
    {
      "settings": {},
      "name": "router",
      "type": "Router",
      "next": "vless"
    },
    {
      "settings": {
        "mode": "direct",
        "servers": [
          "<SERVER_IP>:28453"
        ]
      },
      "name": "resolver",
      "type": "DomainResolver",
      "next": "router"
    },
    {
      "settings": {
        "sni": "localhost",
        "verify": false,
        "alpns": [
          "http/1.1"
        ]
      },
      "name": "tls",
      "type": "TlsClient",
      "next": "connector"
    },
    {
      "name": "connector",
      "type": "TcpUdpConnector",
      "settings": {
        "address": "127.0.0.1",
        "nodelay": true,
        "port": 4097
      }
    }
  ]
}

How it was tested

  1. Xcode installed the app's test build on the phone, and the test created the profile shown above in memory. It was not added to the app's profile list.
  2. The test connected the VPN and ran the app's own HTTPS check through the tunnel: a request to https://gstatic.com/generate_204, which must answer 204.
  3. For at least 90 seconds it ran 4 downloads of 16 MiB at the same time, over and over. They used the test server's name, so each new connection made the DNS resolver look it up. The GeoIP case downloaded from the reference server on port 28480; the others from the HTTPS test server.
  4. It then sent small UDP datagrams to the echo server for 90 seconds, at least 10 a second, and waited for each one to come back.
  5. It ran the HTTPS check again and disconnected.
  6. The harness then read the DNS test server's log for the time of the case: Native must leave no question there, Direct must leave questions from our office address only, and Through the VPN questions from the WaterWall server only. For Direct and Through the VPN, the test server's name must be among them. For the GeoIP case it also read the reference server's log, as in the GeoIP routing cases.

A case passes only if the VPN stayed connected, the downloads ran the full 90 seconds with no errors or timeouts, both HTTPS checks succeeded, every UDP datagram came back, the DNS questions came from where the resolver's setting sends them, and, for the GeoIP case, every download went straight from the phone. The cases without GeoIP were also checked to arrive through the tunnel.

Gaps and limits

Evidence

Test casedns-resolver-direct
Run2026-11-10T10:21:58Z to 2026-11-10T10:31:55Z (UTC)
Case log times2026-11-10 13:25:46 to 2026-11-10 13:27:25 (phone time, UTC+3)
App sourcecommit e69cb668
Server programWaterWall 1.5.42, the official release, unchanged, SHA-256 38631081bd10347d…
Evidence filewaterwall-dns-resolver-20261110T1021Z.json