Temporary failure in name resolution/ 22.04.2 LTS

user89978

3/18/24, 6:30 PM

I have configured a windows VM as my DNS server and configured all my ubuntu VM's to use it.

netplan from my ubuntu VM

$ cat /etc/netplan/00-installer-config.yaml
# This is the network config written by 'subiquity'
network:
  ethernets:
    ens160:
      addresses:
      - 172.0.1.51/24
      nameservers:
        addresses:
        - 172.0.1.34
        search: []
      routes:
      - to: default
        via: 172.0.1.29
  version: 2

Name resolution/DNS lookup works fine for external internet connectivity.

$ ping google.com
PING google.com 56(84) bytes of data.
64 bytes from seu35a21-eu-g67.2e345.net: icmp_seq=1 ttl=107 time=27.4 ms
64 bytes from seu35a21-eu-g67.2e345.net: icmp_seq=2 ttl=107 time=26.6 ms
64 bytes from seu35a21-eu-g67.2e345.net: icmp_seq=3 ttl=107 time=26.7 ms

However I added a manual DNS A Record in my windows DNS server in the configured zone(home.local) 172.0.1.45 nginx.home.local
From my windows VM, ping to the local FQDN works fine.

C:\Users\JCGHDX>ping nginx.home.local

Pinging nginx.home.local [172.0.1.45] with 32 bytes of data:
Reply from 172.0.1.45: bytes=32 time<1ms TTL=128
Reply from 172.0.1.45: bytes=32 time<1ms TTL=128
Reply from 172.0.1.45: bytes=32 time<1ms TTL=128

However on my ubuntu VM

$ ping nginx.home.local
ping: nginx.home.local: Temporary failure in name resolution

$ resolvectl status
Global
       Protocols: -LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
resolv.conf mode: stub

Link 2 (ens160)
    Current Scopes: DNS
         Protocols: +DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
Current DNS Server: 172.0.1.34
       DNS Servers: 172.0.1.34

Any pointers why DNS lookup fails for local domain ?

278

1 + 2

networking

dns

FedKad

3/18/24, 7:09 PM

Just a thought. Can you try putting a dot at the end? Like this: `ping nginx.home.local.`

user89978

3/19/24, 7:47 AM

@FedKad Tried it. Same issue: `ping: nginx.home.local.: Temporary failure in name resolution`. One interesting thing is reverse lookup is able to identify FQDN `nslookup 172.0.1.45 45.1.0.172.in-addr.arpa name = nginx.home.local.`

Score:0

Ubuntu

user89978

3/19/24, 8:16 AM

For anyone looking for detailed explanation: Ubuntu 18.04 .local domain dns lookup not working

TLDR; /etc/resolv.conf points nameserver to 127.0.0.1#53 which rejects DNS lookups for .local domain. Fix is provided in that answer. However it requires config change in all my ubuntu VM's.

Easy alternate would be configure a new zone in my windows DNS without ending with .local and add manual A records to that zone. Then finally used the FQDN obtained from the zone which works!

+ 0

Elon Musk

I sit in a Tesla and translated this thread with Ai:

EN: Temporary failure in name resolution/ 22.04.2 LTS

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.