The network config in the previous bug used DHCP on v4 and v6; it appears this instance has a different network config injected. Can you attach the network configuration?
As a workaround, you can include a nameserver configuration
- type: nameserver:
address:
- 8.8.8.8
- 8.8.8.3
Or also include the dns-nameservers attribute in the second subnet configuration.
This will render dns-nameservers entry under lo
which will get picked up.
Given the above config, it looks like the ifupdown resolveconf hooks are not multi-iface-stanza aware.
The network config in the previous bug used DHCP on v4 and v6; it appears this instance has a different network config injected. Can you attach the network configuration?
As a workaround, you can include a nameserver configuration
- type: nameserver:
address:
- 8.8.8.8
- 8.8.8.3
Or also include the dns-nameservers attribute in the second subnet configuration.
This will render dns-nameservers entry under lo
which will get picked up.
Given the above config, it looks like the ifupdown resolveconf hooks are not multi-iface-stanza aware.