DNS Forwarding keeps a DNS A record pointed at your machine's current public IP address, so a domain you own resolves to your Slash Socket server instead of clients needing your raw IP. It's dynamic DNS, not a tunnel — it does not do NAT traversal or expose your server without port forwarding. You're still responsible for forwarding the chosen port on your router if clients need to reach you from outside your LAN.
Records are managed through Vercel, so the domain must use Vercel's DNS. You connect Vercel once on your slash.tools dashboard — the access stays there, and Slash Socket never holds a Vercel token.
- In Slash Socket, open the Domain tab and press Sign in with Slash. Your browser signs you in with GitHub — the same account as slash.tools and Slash for Mac.
- On slash.tools, open Dashboard → Socket and press Connect Vercel, then install the integration on your personal account or a team.
- Pick a subdomain and one of your Vercel domains (e.g. ws + example.com for ws.example.com), choose which Mac it points at, and press Save & publish.
- Slash Socket checks in when its server starts or stops and every 5 minutes. Whenever your public IP changes, slash.tools updates the A record, and the Domain tab shows where you're published.
Your public IP is read from a third-party IP lookup service (ipify) at each check-in.