Network Requests Failing
If you notice that your API logs show failed requests to services like GitHub or SteamCMD, it may be caused by a search domain set by your DHCP server.
Confirming Search Domains
To check if your DHCP server is setting a search domain, review your /etc/resolv.conf
file. Look for any search
or domain
entries - if there's anything other than standard DNS servers, you may have this issue.
Change Search Domain
Important: Do not directly edit /etc/resolv.conf
as it will be overwritten on reboot by your system's network management service.
Method 1: Using systemd-resolved (Ubuntu 18.04+, most modern Linux)
Create or edit the systemd-resolved configuration:
bashsudo nano /etc/systemd/resolved.conf
Add or modify these lines:
[Resolve] Domains=~.
Restart systemd-resolved:
bashsystemctl restart systemd-resolved
Method 2: Using Netplan (Ubuntu with Netplan)
Find your netplan configuration file:
bashls /etc/netplan/
Edit the configuration file (usually
50-cloud-init.yaml
or similar):bashnano /etc/netplan/50-cloud-init.yaml
Update the search to be an empty array
yamlsearch: []
Apply the changes:
bashnetplan apply
Method 3: Using NetworkManager
Edit the connection configuration:
bashnmcli connection modify "connection-name" ipv4.dns-search ""
Restart NetworkManager:
bashsudo systemctl restart NetworkManager
Method 4: DHCP Client Configuration
Edit the DHCP client configuration:
bashsudo nano /etc/dhcp/dhclient.conf
Add these lines to override DHCP-provided DNS:
supersede domain-search "";
Restart networking:
bashsudo systemctl restart networking
Verification
After applying any method, verify your changes:
Check the current resolv.conf:
bashcat /etc/resolv.conf
Test DNS resolution:
bashnslookup github.com
Reboot and verify the changes persist:
bashsudo reboot