weizhouapache commented on issue #9003: URL: https://github.com/apache/cloudstack/issues/9003#issuecomment-2088401114
> Even if this is considered intended behavior, it still seems wrong. Adding external DNS's that don't know anything about the instances in the isolated network to the list of resolvers returned by DHCP results in a broken DNS config for the instances in the isolated network. > > Any attempt to resolve another instance in the isolated network (say, a webserver looking for a mysql server) would randomly fail if systemd-resolved decides to pick another resolver than the primary (which it seems to randomly do quite frequently) > I have no idea how systemd-resolved works. Have you seen the issue in the VMs without systemd-resolved ? > And the existence of [this logic](https://github.com/apache/cloudstack/blob/f41c934c94ad50e0bb3e51c26e52ac78196acd69/server/src/main/java/com/cloud/network/router/VirtualNetworkApplianceManagerImpl.java#L2055C1-L2060C43) and the comment above it seem to suggest that this is not working as intended, as the code is not doing what the comment describes. the comment means, the VR will not be used as DNS resolver, if - VR does not provide DNS service, OR - the setting use.external.dns is set to true I agree with Daan that this probably needs a new setting. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
