This is the expected behaviour for OVN, as documented here [1]. When building the DHCP options, the DNS servers option is populated first with the subnet "dns_nameservers". If empty, the "OVN.dns_servers" option will be used. If empty, the OVN mech driver will use the local DNS resolver (reading from "/etc/resolv.conf") [2].
Admin/user can always provide a valid DNS nameserver if needed.
Hello Jens:
This is the expected behaviour for OVN, as documented here [1]. When building the DHCP options, the DNS servers option is populated first with the subnet "dns_nameservers". If empty, the "OVN.dns_servers" option will be used. If empty, the OVN mech driver will use the local DNS resolver (reading from "/etc/resolv.conf") [2].
Admin/user can always provide a valid DNS nameserver if needed.
Regards.
[1]https:/ /github. com/openstack/ neutron/ blob/90b5456b8c 11011c41f2fcd53 a8943cb45fb6479 /neutron/ conf/plugins/ ml2/drivers/ ovn/ovn_ conf.py# L158-L164 /github. com/openstack/ neutron/ blob/90b5456b8c 11011c41f2fcd53 a8943cb45fb6479 /neutron/ plugins/ ml2/drivers/ ovn/mech_ driver/ ovsdb/ovn_ client. py#L1916- L1918
[2]https:/