What is DNS resolver
The DNS resolver is a critical component of your SlipStream VPN setup. It determines which DNS server will be used to resolve domain names while the VPN is active.The DNS resolver setting should point to a DNS server that can properly resolve your SlipStream server domain and route traffic through the VPN tunnel.
Default setting
By default, SlipStream GUI uses:Custom DNS resolver
You can specify any DNS server in the format:1.1.1.1:53(Cloudflare DNS)YOUR_SERVER_IP:53(Your SlipStream server’s DNS)9.9.9.9:53(Quad9 DNS)
DNS Checker feature
The DNS Checker is a powerful tool that tests multiple DNS servers concurrently to help you find the fastest and most reliable option.Key capabilities
Concurrent testing
Tests up to 100 DNS servers simultaneously for fast results
Real-time results
Shows response times and resolution status for each server
One-click apply
Apply any working DNS server with a single click
Status validation
Verifies that each DNS server can properly resolve your test domain
How to use DNS Checker
Open DNS Checker
Click the “DNS Check” button in the header, or click the “DNS Checker” button in the settings panel.
Enter test domain
In the modal that appears, enter a domain to test (e.g.,
google.com).Use a well-known domain that should always be resolvable for accurate testing.
Enter DNS servers
Paste your list of DNS server IPs in the text area. You can:
- Enter one IP per line
- Paste large lists (up to 100 servers)
- Mix formats (the tool will extract valid IPs)
Understanding DNS Checker results
Status indicators:- OK (Green)
- WARN (Yellow)
- BAD (Red)
- Testing (Gray)
The DNS server successfully resolved the test domain.
- Response time is shown in milliseconds
- Safe to use as your DNS resolver
- Click “Use” to apply immediately
Applying DNS results
When you find a DNS server that works:Automatic configuration
The DNS Checker will:
- Set the DNS Resolver field to
IP_ADDRESS:53 - Force port 53 (standard DNS port)
- Save the setting automatically
- Close the DNS Checker modal
The DNS Checker automatically appends port
:53 to the selected IP address, as this is the standard DNS port.Troubleshooting DNS issues
All DNS servers show BAD status
Possible causes:- No internet connection
- Firewall blocking DNS queries (port 53)
- Network restrictions on DNS
- Test domain is invalid or blocked
- Try a different test domain (e.g.,
google.com,cloudflare.com) - Check your firewall settings
- Ensure you’re not behind a restrictive corporate proxy
DNS resolution works but VPN doesn’t connect
Possible causes:- DNS resolver can’t access your SlipStream server
- Domain configuration is incorrect
- Server is down or unreachable
- Use your SlipStream server’s IP as the DNS resolver (e.g.,
YOUR_SERVER_IP:53) - Verify your Domain setting matches your server configuration
- Check your server deployment and DNS records
Slow DNS resolution
Symptoms:- Websites load slowly
- Initial connection takes a long time
- High response times in DNS Checker
- Choose a DNS server with lower response time (< 50ms is ideal)
- Use a geographically closer DNS server
- Try public DNS services:
- Cloudflare:
1.1.1.1:53 - Google:
8.8.8.8:53 - Quad9:
9.9.9.9:53
- Cloudflare:
DNS Checker timeout
The DNS Checker tests up to 100 servers concurrently, which may take 5-30 seconds depending on network conditions.
- Wait up to 30 seconds for all tests to complete
- Close and reopen the DNS Checker modal
- Test fewer servers at once (10-20 at a time)
Manual DNS configuration
If you prefer to manually configure DNS:- Find a reliable DNS server IP
- Enter it in the DNS Resolver field in this format:
IP:PORT - Use port
53for standard DNS - Click outside the field or press Enter to save
- Restart the VPN to apply changes
The DNS resolver setting is stored in
settings.json along with your other configuration. It persists between application restarts.Best practices
Test regularly
DNS server performance can change. Run the DNS Checker periodically to ensure optimal performance.
Use your server's DNS
For best results with SlipStream, use your own server’s DNS resolver if available.
Save working configs
Use workspace presets to save different DNS configurations for different networks.
Monitor logs
Enable verbose logging to see DNS resolution activity and diagnose issues.