[IPv6] ipv6-only machine has region's ipv4 address in resolv.conf

[LaMont Jones]

I deployed a node with only ipv6, and this happened. The IPv4 address in resolv.conf just means that address lookups experience a 3 second delay.

The subnet involved specifies the second DNS server found in resolv.conf.

ubuntu@hoste:~$ ip addr list
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: ens3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 40:98:e4:96:81:b3 brd ff:ff:ff:ff:ff:ff
    inet6 2601:282:8100:3580:0:1:0:2/64 scope global
       valid_lft forever preferred_lft forever
    inet6 fe80::4298:e4ff:fe96:81b3/64 scope link
       valid_lft forever preferred_lft forever
3: ens4: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 40:98:e4:ef:e3:52 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::4298:e4ff:feef:e352/64 scope link
       valid_lft forever preferred_lft forever
ubuntu@hoste:~$ 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 172.18.0.2
nameserver 2601:282:8100:3580::2
search maas
ubuntu@hoste:~$

[LaMont Jones (lamont)]

specifically, the curtin config for the node has this for the network, even though there is no ipv4 connectivity on the machine:
network:
  config:
  - id: ens3
    mac_address: 40:98:e4:96:81:b3
    mtu: 1500
    name: ens3
    subnets:
    - address: 2601:282:8100:3580:0:1:0:2/64
      dns_nameservers:
      - 2601:282:8100:3580::2
      gateway: fe80::1
      type: static
    type: physical
  - id: ens4
    mac_address: 40:98:e4:ef:e3:52
    mtu: 1500
    name: ens4
    subnets:
    - type: manual
    type: physical
  - address:
    - 172.18.0.2
    search:
    - maas
    type: nameserver
  version: 1

[Andres Rodriguez (andreserl)]

Right, so what I think shoudl be happening is that since the machine interface was told to configure IPv6 e/n/i, it should be grabbing the correct DNS on IPv6.

[Adam Collard (adam-collard)]

This bug has not seen any activity in the last 6 months, so it is being automatically closed.

If you are still experiencing this issue, please feel free to re-open.

MAAS Team