Overview
Private Connect’s DNS integration enables you to access services using friendly.connect domains instead of localhost:port URLs.
Quick Start
Installation
*.connect domains to 127.0.0.1:
Usage
Once installed, access services by name:Platform Support
macOS
Linux (systemd-resolved)
Linux (dnsmasq)
For systems without systemd-resolved:Linux (manual /etc/hosts)
Fallback option:DNS Server
How It Works
Query Processing
Query Processing
Service Resolution
Service Resolution
All The proxy/reach handles routing to the actual service.
.connect domains resolve to 127.0.0.1:DNS Protocol
DNS Protocol
Implements minimal DNS server:
- Listens on UDP port 15353 (non-privileged)
- Responds with A records (IPv4)
- TTL: 60 seconds
- NXDOMAIN for non-
.connectqueries
Server Management
Background Process
DNS server runs as a detached process:Custom Domains
Using a Different TLD
Multiple Domain Support
Install separate resolvers:Testing
DNS Resolution Test
Manual Testing
Application Testing
Integration with Proxy
Combined Setup
DNS + Proxy for seamless subdomain routing:HTTP(S) Access
With HTTPS proxy:Caching
Service Cache
DNS server caches service metadata:DNS Cache Flushing
Uninstallation
- Stops the DNS server
- Removes resolver configuration
- Cleans up background processes
Troubleshooting
DNS Not Resolving
Service Not Found
Permission Issues
Best Practices
Use Descriptive Names
Daemon Mode
Install daemon for automatic startup:DNS server starts with daemon.
Environment Variables
Use
.connect in configs:Testing
Always test DNS after installation: