Prime DNS Logo

Dual-Node Hosts & Cluster Health

Real-time monitoring for Iran Relay and International Exit machines (reporting every 10s)

Active Route:🇮🇷 Iran Relay
Public Mode
🇮🇷

Iran Relay Host

85.9.106.152
NO DATA
Node ID / Role
ir-01 (Relay Node)
Health Score
—
Active Cluster Route
—
Version
—
Service Port Status
Port 53 (DNS UDP/TCP)Unknown
Port 18080 (Health / Ready)Unknown
Port 18081 (Cluster Peering)Unknown
Port 18082 (Admin API)Unknown
🌐

International Exit Host

155.103.69.182
NO DATA
Node ID / Role
int-01 (Exit Node)
Health Score
—
Peering Connection
—
Last Heartbeat
—
Service Port Status
Port 53 (DNS UDP/TCP)Unknown
Port 18080 (Health / Ready)Unknown
Port 18081 (Cluster Peering)Unknown
Port 18082 (Admin API)Unknown

Infrastructure Status & Cross-Border Tunnel

Iran Server (85.9.106.152) ⟷ International Exit Server (155.103.69.182)
TUNNEL UNKNOWN
Tunnel Interconnect
—
Cross-border path not fully verified
Measured Round-Trip Latency
—
Low-latency direct carrier transit
Packet Loss Rate
—
Zero dropped packets across audit
Transport & Protocol
SNI + PROXY Proto
Client Real-IP header pass-through
Cross-Border Pipeline Architecture
SNI Pre-read Proxy (443)
Unknown
PROXY Protocol Pass-through
Unknown
DNS UDP/TCP Dual-Stack (53)
Unknown
Cluster State Sync (18081)
Unknown

Cluster Peering & Connection Diagnostics

Cluster Sync Port: 18081

If the International Exit Node shows UNREACHABLE, ensure that port 18081 is allowed on your firewall and both machines share the identical cluster token. Run this diagnostic command directly on either server:

sudo ufw allow 53/udp && sudo ufw allow 53/tcp && sudo ufw allow 18081/tcp && sudo systemctl restart PrimeDNS-engine

Cluster Audit & Synchronization Log

TimestampNode IDEvent TypeTrigger / ReasonStatus
No events recorded yet. Cluster is functioning nominally.