Ubuntu – Proper DNS suffix setup Ubuntu 17.04

dnsresolv.confsystemd-networkdUbuntu

I have trouble getting DNS suffix to work properly

Basically, I have jira.mycompany.local in the company DNS server mapped to 192.168.100.5

I want to be able to access it using both jira and jira.mycompany.local.

I have this in my /etc/systemd/resolvd.conf

[Resolve]
Domains=mycompany.local devnet.mycompany.nl

Restarting the Network manager & resolved:

systemctl restart NetworkManager.service
systemctl restart systemd-resolved.service

Results in this /etc/resolv.conf:

nameserver 192.168.10.1
nameserver 192.168.10.2
nameserver 127.0.0.53

search mycompany.local
search devnet.mycompany.nl

So this all looks good. Testing the DNS:

nslookup jira.mycompany.local
Server:     192.168.10.1
Address:    192.168.10.1#53

Name:   jira.mycompany.local
Address: 192.168.100.5

Ping to IP:

>ping 192.168.100.5
PING 192.168.100.5 (192.168.100.5) 56(84) bytes of data.
64 bytes from 192.168.100.5: icmp_seq=1 ttl=63 time=7.04 ms

Ping To hostname (with and without suffix):

>ping jira
ping: jira: Name or service not known

>ping jira.mycompany.local
ping: jira.mycompany.local: Name or service not known

Relevant line of /etc/nsswitch.conf:

hosts:          files [NOTFOUND=return] resolve [!UNAVAIL=return] dns myhostname

(I removed the avahi line so it won't interfere.)

Test using dig:

dig +short jira 
(empty)

dig +short jira.mycompany.local 
192.168.100.5

[EDIT]

I modified the hosts line in the etc/nsswitch.conf:

hosts:          files resolve dns

Now:

>ping jira.mycompany.local
PING jira.mycompany.local (192.168.100.5) 56(84) bytes of data.
64 bytes from 192.168.100.5: icmp_seq=1 ttl=63 time=7.04 ms

Works, but:

>ping jira
ping: jira: Temporary failure in name resolution

How can I debug this issue / or fix it?

Best Answer

Try using only on search line in you resolv.conf

search mycompany.local devnet.mycompany.nl

Secondly, your test with dig using only jira fails and that is a normal behavior! dig won't auto-complete your hostname with the domains specified in resolv.conf.

DNS Config Under Linux

DNS usage on linux is done over a set of routines in the C library that provide access to the Internet Domain Name System (DNS). The resolver configuration file (resolv.conf) contains information that is read by the resolver routines the first time they are invoked by a process. In short each process requesting DNS will read /etc/resolv.conf over library. The NSS is layered on top of this, and is configured by /etc/nsswitch.conf.

Linux DNS config are located in the file /etc/resolv.conf BUT there are a number of programs/services that wants to automatically manage and handle the DNS configuration file at /etc/resolv.conf. In some situations you may want to manage this file yourself. Each program/service managing DNS have its own configuration files like /etc/dnsmasq.conf (for dnsmasq service) and append the DNS config at connection change and/or on other events... a quick solution is to lock the DNS config file with chattr +i /etc/resolv.conf but this is not recommended in certain case, a better solution is to setup correctly all the program/services using the DNS like (dnsmasq/network-manager/resolvconf/etc.)

Getting Back The Control Of DNS

Here is an exhaustive list of setups to get back the control of resolv.conf and avoid having it overwritten (how to disable/setup DNS from other location other than resolv.conf) note that resolvconf is an independent program from resolv.conf, also depending on your system/config you may not have one or many of the programs listed here.

1. Resolvconf:

Config files

cat /etc/resolvconf/resolv.conf.d/head
nameserver 8.8.4.4
cat /etc/resolvconf/resolv.conf.d/base
nameserver 8.8.4.4

Update the config

sudo resolvconf -u

Disable resolvconf

systemctl disable --now resolvconf.service

2. Dnsmasq Service:

Config files

cat /etc/dnsmasq.conf
server=1.1.1.1
server=8.8.4.4

Update the config

sudo systemctl restart dnsmasq.service

3. Network Manager:

Config files

/etc/NetworkManager/*

Disable DNS

$ cat /etc/NetworkManager/conf.d/no-dns.conf
[main]
dns=none

Enable DNS

$ cat /etc/NetworkManager/conf.d/dns.conf
[main]
dns=default

[global-dns]
searches=example.com

[global-dns-domain-*]

Use resolved service

$ cat /usr/lib/NetworkManager/conf.d/resolved.conf 
[main]
dns=systemd-resolved

Use resolvconf

$ cat /usr/lib/NetworkManager/conf.d/resolvconf.conf 
[main]
rc-manager=resolvconf

Update the config

systemctl restart NetworkManager.service

4. Network Interfaces:

Config files

$ cat /etc/network/interfaces
#nameservers
# or dns-search like so
# dns-search x.y 
dns-nameservers 4.4.4.4 8.8.8.8

Update The Config

reboot

5. DHCP Client:

Config files

$ cat /etc/dhcp3/dhclient.conf
supersede domain-name-servers <dns_ip_address1>,<dns_ip_address2>;

Update The Config

reboot

6. Rdnssd Service:

Disable rdnssd

systemctl disable --now rdnssd.service

7. Resolved Service:

Disable resolved

systemctl disable --now systemd-resolved.service

8. Netconfig:

Config files

/etc/sysconfig/network/config

Disable netconfig

cat /etc/sysconfig/network/config
NETCONFIG_DNS_POLICY=""

Update The Config

reboot

Setting The DNS Server

Example of a /etc/resolv.conf configuration

#Cloudflare
nameserver 1.0.0.1

#Google
#nameserver 8.8.8.8
#nameserver 8.8.4.4

#Cloudflare 
#nameserver 1.1.1.1

#Classic Config
#nameserver 192.168.1.1
#search lan

Best Answer

Related Solutions

Shell – How to resolve a hostname via nsswitch

Debian – How to setup DNS manually on Linux

DNS Config Under Linux

Getting Back The Control Of DNS

1. Resolvconf:

2. Dnsmasq Service:

3. Network Manager:

4. Network Interfaces:

5. DHCP Client:

6. Rdnssd Service:

7. Resolved Service:

8. Netconfig:

Setting The DNS Server

Related Question