In the existing deployment, the DNS config in the LXD container (nova-cloud-controller) looks as follows:
ubuntu@juju-d1a6e2-2-lxd-2:~$ cat /etc/resolv.conf │······························································
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) │······························································
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN │······························································
nameserver 10.245.168.6 │······························································
search maas
in the 'broken' one, it is using a local resolver and therefore presumably doesnt forward queries to the MAAS dns server which would respond to the hostname of the nova-compute machine.
/etc/resolv.conf on broken instance only contains:
nameserver 127.0.0.53
---
host and ping both fail to resolve the hostname, but dig succeeds partially:
ubuntu@juju-6406ff-2-lxd-2:/etc$ host node-jaeger
Host node-jaeger not found: 2(SERVFAIL)
ubuntu@juju-6406ff-2-lxd-2:/etc$ ping node-jaeger
ping: node-jaeger: Temporary failure in name resolution
ubuntu@juju-6406ff-2-lxd-2:/etc$ dig node-jaeger
In the existing deployment, the DNS config in the LXD container (nova-cloud- controller) looks as follows:
ubuntu@ juju-d1a6e2- 2-lxd-2: ~$ cat /etc/resolv.conf │······ ······· ······· ······· ······· ······· ······· ······· ······· ······· ······· ······· ······· ······· ······· ······· ······· ······· ······· ······· ······· ······· ······· ······· ······· ······· ······· ······· ······· ······· ······· ······· ·······
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) │······
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN │······
nameserver 10.245.168.6 │······
search maas
in the 'broken' one, it is using a local resolver and therefore presumably doesnt forward queries to the MAAS dns server which would respond to the hostname of the nova-compute machine.
/etc/resolv.conf on broken instance only contains:
nameserver 127.0.0.53
---
host and ping both fail to resolve the hostname, but dig succeeds partially:
ubuntu@ juju-6406ff- 2-lxd-2: /etc$ host node-jaeger juju-6406ff- 2-lxd-2: /etc$ ping node-jaeger juju-6406ff- 2-lxd-2: /etc$ dig node-jaeger
Host node-jaeger not found: 2(SERVFAIL)
ubuntu@
ping: node-jaeger: Temporary failure in name resolution
ubuntu@
; <<>> DiG 9.11.3- 1ubuntu1- Ubuntu <<>> node-jaeger
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 13450
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;node-jaeger. IN A
;; Query time: 0 msec 53#53(127. 0.0.53)
;; SERVER: 127.0.0.
;; WHEN: Thu May 17 19:49:05 UTC 2018
;; MSG SIZE rcvd: 40
dig node-jaeger.maas succeeds:
ubuntu@ juju-6406ff- 2-lxd-2: /etc$ dig node-jaeger.maas
; <<>> DiG 9.11.3- 1ubuntu1- Ubuntu <<>> node-jaeger.maas
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 58641
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;node-jaeger.maas. IN A
;; ANSWER SECTION:
node-jaeger.maas. 30 IN A 10.245.168.44
;; Query time: 0 msec 53#53(127. 0.0.53)
;; SERVER: 127.0.0.
;; WHEN: Thu May 17 19:50:56 UTC 2018
;; MSG SIZE rcvd: 61