Some hosts on AD are host.company.local, but my Linux machine only resolves as host.local not host.company.local. Why?

This is just for curiosity, no work issues or needing to fix this.

I thought that all hosts on a LAN should be able to resolve to that FQDN of host.company.local. My resolve.conf on my Linux box shows 127.0.0.53 and does have "search company.local".

The most likely explanation I can think of is that my Linux box needs to be added to the local DNS somehow?

Ideas?

Posted Oct 30, 2019, 2:03 PM UTC

04
eri-•

Because you are not domain joined?

3
pdp10802.3by && 20mA current loop•

Sounds like mDNS (Avahi on Linux, Bonjour on Mac), as mDNS uses .local. Which is the capstone on the plethora of reasons why one should never use .local or other invalid TLDs on a production network.

Stopping the Avahi service is likely to fix it. You may also be interested in /etc/nsswitch.conf which usually defaults thus:

hosts:          files mdns4_minimal [NOTFOUND=return] dns

Lastly, you should be using FQDNs almost all of the time, and not relying on domain or search directives. Those break with HTTPS/TLS, amongst other fragilities.

3
gex80Studying Cisco Cert•

If the entry isn't in DNS or host file, the server won't know about it. Hostname resolution is a DNS/WINS/Netbios/etc type deal. Either add them to /etc/hosts or create a DNS zone with those entries in and point the linux server to the DNS server.

Anything 127.0.0.x means localhost. If you're setting your nameservers to resolve to itself but the nameserver isn't running DNS, then how do you expect it to resolve anything?

1
NexusT•

You have potentially bigger fish to fry, noone should be using .local domains anymore, its been a part of mDNS since RFC 6762 in 2013.

1