[Touch-packages] [Bug 1810439] Re: DNS/systemd-resolve: host1.foo.local cannot resolve host2.bar.local
please reopen if this is still an issue ** Changed in: systemd (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1810439 Title: DNS/systemd-resolve: host1.foo.local cannot resolve host2.bar.local Status in systemd package in Ubuntu: Invalid Bug description: This is a fresh install of Ubuntu 18.04 (using the latest maas.io image). The system is in a DNS domain of "maas.local". There are other systems in this data center that are in the DNS domain "eng.local". Attempting to resolve the name of a system in the eng.local domain fails when run from the maas.local system (and vice versa, but we'll focus on the details of the former case). Details: ubuntu@kvm7246-vm009:~$ grep '^[^#]' /etc/resolv.conf nameserver 127.0.0.53 search maas.local tc82.local ubuntu@kvm7246-vm009:~$ systemd-resolve --status Global DNSSEC NTA: 10.in-addr.arpa 16.172.in-addr.arpa 168.192.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 23.172.in-addr.arpa 24.172.in-addr.arpa 25.172.in-addr.arpa 26.172.in-addr.arpa 27.172.in-addr.arpa 28.172.in-addr.arpa 29.172.in-addr.arpa 30.172.in-addr.arpa 31.172.in-addr.arpa corp d.f.ip6.arpa home internal intranet lan local private test Link 2 (ens6) Current Scopes: DNS LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no DNS Servers: 172.23.4.4 DNS Domain: maas.local tc82.local ubuntu@kvm7246-vm009:~$ host maas1.maas.local maas1.maas.local has address 172.23.4.4 ubuntu@kvm7246-vm009:~$ systemd-resolve maas1.maas.local maas1.maas.local: 172.23.4.4 -- Information acquired via protocol DNS in 2.3ms. -- Data is authenticated: no ubuntu@kvm7246-vm009:~$ host mirror1.eng.local Host mirror1.eng.local not found: 2(SERVFAIL) ubuntu@kvm7246-vm009:~$ systemd-resolve mirror1.eng.local mirror1.eng.local: resolve call failed: No appropriate name servers or networks for name found ubuntu@kvm7246-vm009:~$ host mirror1.eng.local 172.23.4.4 Using domain server: Name: 172.23.4.4 Address: 172.23.4.4#53 Aliases: mirror1.eng.local has address 172.21.0.66 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1810439/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1810439] Re: DNS/systemd-resolve: host1.foo.local cannot resolve host2.bar.local
please reopen if this is still an issue -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1810439 Title: DNS/systemd-resolve: host1.foo.local cannot resolve host2.bar.local Status in systemd package in Ubuntu: Invalid Bug description: This is a fresh install of Ubuntu 18.04 (using the latest maas.io image). The system is in a DNS domain of "maas.local". There are other systems in this data center that are in the DNS domain "eng.local". Attempting to resolve the name of a system in the eng.local domain fails when run from the maas.local system (and vice versa, but we'll focus on the details of the former case). Details: ubuntu@kvm7246-vm009:~$ grep '^[^#]' /etc/resolv.conf nameserver 127.0.0.53 search maas.local tc82.local ubuntu@kvm7246-vm009:~$ systemd-resolve --status Global DNSSEC NTA: 10.in-addr.arpa 16.172.in-addr.arpa 168.192.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 23.172.in-addr.arpa 24.172.in-addr.arpa 25.172.in-addr.arpa 26.172.in-addr.arpa 27.172.in-addr.arpa 28.172.in-addr.arpa 29.172.in-addr.arpa 30.172.in-addr.arpa 31.172.in-addr.arpa corp d.f.ip6.arpa home internal intranet lan local private test Link 2 (ens6) Current Scopes: DNS LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no DNS Servers: 172.23.4.4 DNS Domain: maas.local tc82.local ubuntu@kvm7246-vm009:~$ host maas1.maas.local maas1.maas.local has address 172.23.4.4 ubuntu@kvm7246-vm009:~$ systemd-resolve maas1.maas.local maas1.maas.local: 172.23.4.4 -- Information acquired via protocol DNS in 2.3ms. -- Data is authenticated: no ubuntu@kvm7246-vm009:~$ host mirror1.eng.local Host mirror1.eng.local not found: 2(SERVFAIL) ubuntu@kvm7246-vm009:~$ systemd-resolve mirror1.eng.local mirror1.eng.local: resolve call failed: No appropriate name servers or networks for name found ubuntu@kvm7246-vm009:~$ host mirror1.eng.local 172.23.4.4 Using domain server: Name: 172.23.4.4 Address: 172.23.4.4#53 Aliases: mirror1.eng.local has address 172.21.0.66 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1810439/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1810439] Re: DNS/systemd-resolve: host1.foo.local cannot resolve host2.bar.local
Why isn't systemd-resolved forwarding my query for mirror1.eng.local to the configured upstream DNS server? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1810439 Title: DNS/systemd-resolve: host1.foo.local cannot resolve host2.bar.local Status in systemd package in Ubuntu: New Bug description: This is a fresh install of Ubuntu 18.04 (using the latest maas.io image). The system is in a DNS domain of "maas.local". There are other systems in this data center that are in the DNS domain "eng.local". Attempting to resolve the name of a system in the eng.local domain fails when run from the maas.local system (and vice versa, but we'll focus on the details of the former case). Details: ubuntu@kvm7246-vm009:~$ grep '^[^#]' /etc/resolv.conf nameserver 127.0.0.53 search maas.local tc82.local ubuntu@kvm7246-vm009:~$ systemd-resolve --status Global DNSSEC NTA: 10.in-addr.arpa 16.172.in-addr.arpa 168.192.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 23.172.in-addr.arpa 24.172.in-addr.arpa 25.172.in-addr.arpa 26.172.in-addr.arpa 27.172.in-addr.arpa 28.172.in-addr.arpa 29.172.in-addr.arpa 30.172.in-addr.arpa 31.172.in-addr.arpa corp d.f.ip6.arpa home internal intranet lan local private test Link 2 (ens6) Current Scopes: DNS LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no DNS Servers: 172.23.4.4 DNS Domain: maas.local tc82.local ubuntu@kvm7246-vm009:~$ host maas1.maas.local maas1.maas.local has address 172.23.4.4 ubuntu@kvm7246-vm009:~$ systemd-resolve maas1.maas.local maas1.maas.local: 172.23.4.4 -- Information acquired via protocol DNS in 2.3ms. -- Data is authenticated: no ubuntu@kvm7246-vm009:~$ host mirror1.eng.local Host mirror1.eng.local not found: 2(SERVFAIL) ubuntu@kvm7246-vm009:~$ systemd-resolve mirror1.eng.local mirror1.eng.local: resolve call failed: No appropriate name servers or networks for name found ubuntu@kvm7246-vm009:~$ host mirror1.eng.local 172.23.4.4 Using domain server: Name: 172.23.4.4 Address: 172.23.4.4#53 Aliases: mirror1.eng.local has address 172.21.0.66 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1810439/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
