Private DNS

Name resolution for your internal services

Siovos includes a private DNS server that resolves your service names when you're connected to the VPN.

How it works#

When you deploy, Siovos creates DNS entries for each enabled service:

  • rancher.internal - Kubernetes interface
  • registry.internal - Docker registry
  • grafana.internal - Monitoring dashboards
  • mailpit.internal - Test mail server
  • analytics.internal - Web analytics

The suffix (.internal by default) and each service's subdomain are configurable during deployment. For example, you can replace rancher.internal with k8s.internal.

Service subdomains are set during deployment. Changing them afterwards requires updating both the DNS entry and the service configuration (Kubernetes ingress).

View configuration#

  1. Go to My Infrastructures
  2. Click on the infrastructure of your choice
  3. Open the DNS tab

You'll see two sections:

  • System entries - Automatically created for services
  • Custom entries - Added by you

Add custom entries#

To point a domain to a specific IP:

  1. In the DNS tab, click Add entry
  2. Enter the hostname (e.g., myapp)
  3. Enter the target IP address
  4. Click Save

The entry is immediately available on all devices connected to the VPN.

Usage examples#

HostnameIPUsage
api10.8.0.1Internal API
staging10.8.0.5Staging environment
db-replica10.8.0.10Secondary database

Wildcard DNS for apps#

Siovos automatically configures wildcard DNS per environment for your apps deployed via CI/CD:

*.dev.internal     - Development environment
*.staging.internal - Staging environment
*.preview.internal - Preview environments

When you deploy an application, it's automatically accessible via its subdomain name. For example, an app myapp deployed in dev will be accessible at https://myapp.dev.internal without any additional DNS configuration.

Delete an entry#

For custom entries only:

  1. Find the entry in the list
  2. Click the delete icon
  3. Confirm

System entries cannot be deleted.

Configure the DNS suffix#

During deployment, you can change the default suffix (.internal):

  • .home - Good choice for personal use
  • .corp - For corporate use
  • Your own domain - e.g., .mycompany.lan

Avoid .local as it may conflict with mDNS/Bonjour on macOS.

The suffix cannot be changed after deployment. Choose it carefully from the start.

Common issues#

"Host not found" - Check that you're connected to the VPN. Private DNS only works through the VPN connection.

DNS changes not applied - Flush your system's DNS cache:

  • macOS: sudo dscacheutil -flushcache && sudo killall -HUP mDNSResponder
  • Windows: ipconfig /flushdns
  • Linux: sudo systemd-resolve --flush-caches

Conflict with local DNS - If you chose .local as suffix, change it or disable mDNS on your machine.

Was this page helpful?