I face similar issue with physical machines. Some hosts are returning two entries
installed: 3.3.4-13189-g.f88272d1e (28521) 138MB -
ubuntu@somecompany-infra-management-1:~/cpe-deployments$ juju ssh 21 'dig -x $(hostname -I)' | grep -A3 "ANSWER SECTION" ;; ANSWER SECTION: 13.129.169.10.in-addr.arpa. 8 IN PTR somecompany-compute-19.some-internal-dns.example 13.129.169.10.in-addr.arpa. 8 IN PTR enp68s0f0.somecompany-compute-19.some-internal-dns.example
Connection to 10.169.130.25 closed. ubuntu@somecompany-infra-management-1:~/cpe-deployments$ juju ssh 20 'dig -x $(hostname -I)' | grep -A3 "ANSWER SECTION" ;; ANSWER SECTION: 26.129.169.10.in-addr.arpa. 30 IN PTR somecompany-compute-11.some-internal-dns.example
;; Query time: 4 msec Connection to 10.169.130.24 closed.
I face similar issue with physical machines. Some hosts are returning two entries
installed: 3.3.4-13189- g.f88272d1e (28521) 138MB -
ubuntu@ somecompany- infra-managemen t-1:~/cpe- deployments$ juju ssh 21 'dig -x $(hostname -I)' | grep -A3 "ANSWER SECTION" 169.10. in-addr. arpa. 8 IN PTR somecompany- compute- 19.some- internal- dns.example 169.10. in-addr. arpa. 8 IN PTR enp68s0f0. somecompany- compute- 19.some- internal- dns.example
;; ANSWER SECTION:
13.129.
13.129.
Connection to 10.169.130.25 closed. somecompany- infra-managemen t-1:~/cpe- deployments$ juju ssh 20 'dig -x $(hostname -I)' | grep -A3 "ANSWER SECTION" 169.10. in-addr. arpa. 30 IN PTR somecompany- compute- 11.some- internal- dns.example
ubuntu@
;; ANSWER SECTION:
26.129.
;; Query time: 4 msec
Connection to 10.169.130.24 closed.