RDNSS Option should be included in ICMPv6 Router Advertisements
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Low
|
Sridhar Gaddam | ||
Bug Description
The ICMPv6 Router Advertisements on an IPv6 subnet handled by Neutron does not contain the Recursive DNS Server Option, even though the subnet has been created with an appropriate "dns_nameservers" parameter. This means that instances on a subnet using SLAAC does not learn any DNS servers, and thus cannot resolve any hostnames after being provisioned. That is likely to break lots of things, such as further provisioning of applications to the instance.
The RDNSS option is documented in RFC 6106. It can be configured in radvd.conf using the following syntax:
interface qr-foo {
RDNSS server1 [server2 ...] {
# this is optional, but prevents problems noted in the second bullet of
# https:/
AdvRDNSSLif
};
};
Observed on OpenStack Kilo.
Note: It might be that using DHCPv6 in some capacity would work around this issue. I have not yet tested this, though.
Changed in neutron: | |
assignee: | nobody → Sridhar Gaddam (sridhargaddam) |
Changed in neutron: | |
importance: | Medium → Low |
Changed in neutron: | |
status: | Fix Committed → Fix Released |
Confirming this - I think this is something we need to add to our radvd orchestration code.