Answer the question
In order to leave comments, you need to log in
Why can't I reach the AD server by FQDN in debian 9.1?
Installed on a Debian client machine
As a result of the configuration, I found out that I can not access services on the network by their FQDN name
For example:
$ ping ServiceDC.domain.local
$ ping: ServiceDC.domain.local: The name or service is not known
$ ping ServiceDC
PING ServiceDC .domain.local (10.110.x.y1) 56(84) bytes of data.
64 bytes from ServiceDC.domain.local (10.110.x.y1): icmp_seq=1 ttl=64 time=0.295 ms
64 bytes from ServiceDC.domain.local (10.110.x.y1): icmp_seq=2 ttl=64 time= 0.419 ms
^C
--- ServiceDC.domain.local ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1001ms
rtt min/avg/max/mdev = 0.295/0.357/0.419/0.062 ms
where domain.local is the domain suffix
Tell me what the problem might be related to I am attaching a
couple of configs to make it clearer
/$ cat /etc/NetworkManager/NetworkManager.conf
[main]
plugins=ifupdown,keyfile
[ifupdown]
managed=false
/$ cat / etc/resolv.conf
# Generated by NetworkManager
search domain.local
nameserver 10.110.x.y1
nameserver 10.110.x.y2
/$ cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
source /etc/network/interfaces.d/*
# The loopback network interface
auto lo
iface lo inet loopback
Answer the question
In order to leave comments, you need to log in
I found out that in more modern versions of linux (with Version 2 GNU standard library on board) the nsswitch.conf configuration file is used instead of the old host.conf. Here a problem was found. In the default configuration, the hostname lookup settings look like this:
~$ cat /etc/nsswitch.conf | grep hosts
hosts: files mdns4_minimal [NOTFOUND=return]
dns avahi-daemon first uses the traditional /etc/hosts and /etc/network to find the associated address, then calls mdns4_minimal, finds nothing and returns: Name or service not known. DNS is not involved in any way. Avahi doesn't even look into resolv.conf. To solve this problem, remove [NOTFOUND=return] or move to the end.
Ps As it turned out, the problem has been around for ten years. And my Google skills leave a lot to be desired.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question