Docksal runs a system service called
This service is responsible for the wildcard
*.docksal domain resolution to the Docksal IP (
It also forwards all other DNS requests to the upstream DNS server, which is Google's Public DNS (
220.127.116.11) by default.
Project containers are configured to use
docksal-dns as their DNS server by default.
Docksal configures network settings on Linux, Mac and Windows to tell the host machine to use
docksal-dns as well.
On Mac only
*.docksal DNS queries are routed through
On Linux and Windows DNS all DNS queries are routed through
docksal-dns, as there is no way to configure this
selectively (like on Mac).
In cases when the Docksal VM is stopped or the
docksal-dns service is down, the OS picks the next available DNS server
configured on the host (which would be you LAN/WiFi connection). This way there is always a fallback.
Disabling the resolver
If you run into issues with DNS resolution, try disabling the automatic resolver.
- Stop the VM with
fin vm stop
- Start the VM again
fin vm start
Without the automatic resolver, you can use
fin hosts command to manage name resolution via the
Override the default upstream DNS settings
Some restricted network environments (e.g. corp networks) may be blocking direct access to external DNS services,
18.104.22.168 inaccessible. In such cases Docksal will output a warning with the instructions to override the
default upstream DNS settings.
DOCKSAL_DNS_UPSTREAMto your local network DNS server
fin system reset dns
Inspect you LAN or WiFi interface settings and connection status to figure out the DNS server your network is using.
Enable DNS query logging (for debugging)
DOCKSAL_DNS_DEBUG=true fin system reset dns
fin docker logs docksal-dns