Re: [D] External DNS servers provided with use.external.dns disabled [cloudstack]
GitHub user weizhouapache added a comment to the discussion: External DNS servers provided with use.external.dns disabled @phsm the solution depends on your requirements if you want to have setting globally or per zone, a configkey is better solution if you want to have setting in network offering level, it is also good. GitHub link: https://github.com/apache/cloudstack/discussions/9030#discussioncomment-9305365 This is an automatically sent email for users@cloudstack.apache.org. To unsubscribe, please send an email to: users-unsubscr...@cloudstack.apache.org
Re: [D] External DNS servers provided with use.external.dns disabled [cloudstack]
GitHub user phsm added a comment to the discussion: External DNS servers provided with use.external.dns disabled > As a workaround you can configure your internal DNS server as external DNS > server as well, or not configure an external DNS for this network. This particular workaround won't work as the only DNS resolver that keeps VM name -> VM address records is the DNS server running on the Virtual router. There could be 3 scenario, lets consider the use case for each of them: **Instances use only VR IP as a resolver**. It is needed in case of Isolated networks and VPCs. The instances there are expected to be able to reach another instance within the same network by its name. **Instances use only External DNS IPs as resolvers** This is mostly suitable for Shared networks. Shared network instances typically have public IPs on them, they don't rely on the Virtual Router to reach the Internet. Thus, there is no need to bind them to a VR that can go offline for some reason. **Instances use both VR IP and External DNS IPs as resolvers (current behavior)** No specific use case for it which makes it a good default value. I think the best approach to give flexibility to the CS users while also keeping the backwards compatibility would be to implement it as a Network Offering setting, e.g.: ``` Setting name: DHCP DNS servers policy Possible values (select one): Virtual Router address, External DNS servers, Both (default) ``` This way the Cloudstack admins will decide what is best for their users on the Network Offering level, without having to set it per individual network. GitHub link: https://github.com/apache/cloudstack/discussions/9030#discussioncomment-9296519 This is an automatically sent email for users@cloudstack.apache.org. To unsubscribe, please send an email to: users-unsubscr...@cloudstack.apache.org
Re: [D] External DNS servers provided with use.external.dns disabled [cloudstack]
GitHub user hrak added a comment to the discussion: External DNS servers provided with use.external.dns disabled 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) 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. GitHub link: https://github.com/apache/cloudstack/discussions/9030#discussioncomment-9295133 This is an automatically sent email for users@cloudstack.apache.org. To unsubscribe, please send an email to: users-unsubscr...@cloudstack.apache.org
Re: [D] External DNS servers provided with use.external.dns disabled [cloudstack]
GitHub user DaanHoogland added a comment to the discussion: External DNS servers provided with use.external.dns disabled To me it looks like you either want - an extra setting `use.internal.dns` to be able to switch off the `` addition. - an extra setting `bypass.external.dns` to be able to switch off the `,` additions. The current behaviour is actually as intended but documentation can always improve. ;) GitHub link: https://github.com/apache/cloudstack/discussions/9030#discussioncomment-9295132 This is an automatically sent email for users@cloudstack.apache.org. To unsubscribe, please send an email to: users-unsubscr...@cloudstack.apache.org
Re: [D] External DNS servers provided with use.external.dns disabled [cloudstack]
GitHub user kriegsmanj added a comment to the discussion: External DNS servers provided with use.external.dns disabled > @kriegsmanj the description of the global setting is: `Bypass internal dns, > use external dns1 and dns2` it looks like the global setting is used to > determine if internal dns is bypassed. external dns1/dns2 are always used. To me this means: dns is not going "instance -> vr -> external dns", but bypasses internal, "instance -> external dns" Using both internal + external at the same time, where the internal also has a host-file with all entries of instances in that network makes no sense. Some app use the resolvers in random and not just the first configured. This causes lookup errors for these hostnames when it randomly uses the external resolver to resolve an internal hostname GitHub link: https://github.com/apache/cloudstack/discussions/9030#discussioncomment-9295127 This is an automatically sent email for users@cloudstack.apache.org. To unsubscribe, please send an email to: users-unsubscr...@cloudstack.apache.org
Re: [D] External DNS servers provided with use.external.dns disabled [cloudstack]
GitHub user weizhouapache added a comment to the discussion: External DNS servers provided with use.external.dns disabled > 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. Is it possible to enforce the order of DNS servers in systemd-resolved ? 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. GitHub link: https://github.com/apache/cloudstack/discussions/9030#discussioncomment-9295134 This is an automatically sent email for users@cloudstack.apache.org. To unsubscribe, please send an email to: users-unsubscr...@cloudstack.apache.org
Re: [D] External DNS servers provided with use.external.dns disabled [cloudstack]
GitHub user kriegsmanj added a comment to the discussion: External DNS servers provided with use.external.dns disabled In case of an isolated network, the resolvers configured are the Virtual Router IP and external dns1/dns2 in zone setting. In our environment we have no internal dns1/dns2 configured, so cannot say if those are added if those are set. The DHCP should give only the Virtual Router IP as DNS servers in case of isolated network / vpc. Else the hostname entires in the VR make no sense if it cannot used by the virtual machines. GitHub link: https://github.com/apache/cloudstack/discussions/9030#discussioncomment-9295129 This is an automatically sent email for users@cloudstack.apache.org. To unsubscribe, please send an email to: users-unsubscr...@cloudstack.apache.org
Re: [D] External DNS servers provided with use.external.dns disabled [cloudstack]
GitHub user DaanHoogland added a comment to the discussion: External DNS servers provided with use.external.dns disabled @kriegsmanj , @hrak , very sorry that it doesn't behave as you would expect, and we can certainly change it, but we'll have to do that in a backwards compatible way as it is working for lots of other installations. As a workaround you can configure your internal DNS server as external DNS server as well, or not configure an external DNS for this network. As for a changed functionality, I would suggest a threesome of settings: `dns.enable.external` `dns.enable.internal` `dns.enable.vr` (which is basically the function of the current setting) and mark `use.external.dns` as obsolete, or rename it as the description suggests; `dns.bypass.internal` . GitHub link: https://github.com/apache/cloudstack/discussions/9030#discussioncomment-9295135 This is an automatically sent email for users@cloudstack.apache.org. To unsubscribe, please send an email to: users-unsubscr...@cloudstack.apache.org
Re: [D] External DNS servers provided with use.external.dns disabled [cloudstack]
GitHub user hrak added a comment to the discussion: External DNS servers provided with use.external.dns disabled I think the problem lies in [the logic here](https://github.com/apache/cloudstack/blob/f41c934c94ad50e0bb3e51c26e52ac78196acd69/server/src/main/java/com/cloud/network/router/VirtualNetworkApplianceManagerImpl.java#L2055C1-L2060C43). Based on the description in the comment, that should be either `!dnsProvided && dhcpProvided` or `dnsProvided != dhcpProvided` (former probably better match). In the current state its causing the external DNS to be appended even when dnsProvided and dhcpProvided are both true. GitHub link: https://github.com/apache/cloudstack/discussions/9030#discussioncomment-9295131 This is an automatically sent email for users@cloudstack.apache.org. To unsubscribe, please send an email to: users-unsubscr...@cloudstack.apache.org
Re: [D] External DNS servers provided with use.external.dns disabled [cloudstack]
GitHub user weizhouapache added a comment to the discussion: External DNS servers provided with use.external.dns disabled > > @kriegsmanj the description of the global setting is: `Bypass internal dns, > > use external dns1 and dns2` it looks like the global setting is used to > > determine if internal dns is bypassed. external dns1/dns2 are always used. > > To me this means: dns is not going "instance -> vr -> external dns", but > bypasses internal, "instance -> external dns" > > Using both internal + external at the same time, where the internal also has > a host-file with all entries of instances in that network makes no sense. > Some app use the resolvers in random and not just the first configured. This > causes lookup errors for these hostnames when it randomly uses the external > resolver to resolve an internal hostname if I understand correctly, internal dns means the internal dns1/dns2 in zone setting. >From what @kriegsmanj described, it seems internal dns also include the >cloudstack VR GitHub link: https://github.com/apache/cloudstack/discussions/9030#discussioncomment-9295128 This is an automatically sent email for users@cloudstack.apache.org. To unsubscribe, please send an email to: users-unsubscr...@cloudstack.apache.org
Re: [D] External DNS servers provided with use.external.dns disabled [cloudstack]
GitHub user weizhouapache added a comment to the discussion: External DNS servers provided with use.external.dns disabled @kriegsmanj the description of the global setting is: `Bypass internal dns, use external dns1 and dns2` it looks like the global setting is used to determine if internal dns is bypassed. external dns1/dns2 are always used. GitHub link: https://github.com/apache/cloudstack/discussions/9030#discussioncomment-9295126 This is an automatically sent email for users@cloudstack.apache.org. To unsubscribe, please send an email to: users-unsubscr...@cloudstack.apache.org
Re: [D] External DNS servers provided with use.external.dns disabled [cloudstack]
GitHub user weizhouapache added a comment to the discussion: External DNS servers provided with use.external.dns disabled > In case of an isolated network, the resolvers configured are the Virtual > Router IP and external dns1/dns2 in zone setting. In our environment we have > no internal dns1/dns2 configured, so cannot say if those are added if those > are set. > > The DHCP should give only the Virtual Router IP as DNS servers in case of > isolated network / vpc. Else the hostname entires in the VR make no sense if > it cannot used by the virtual machines. I got same result as @kriegsmanj described, even if internal dns1/dns2 are set. ``` With setting on true: External DNS provided by DHCP (file /etc/dnsmasq.conf on VR) dhcp-option=6,, With setting on false: Internal + External DNS provided by DHCP (file /etc/dnsmasq.conf on VR) dhcp-option=6,,, ``` GitHub link: https://github.com/apache/cloudstack/discussions/9030#discussioncomment-9295130 This is an automatically sent email for users@cloudstack.apache.org. To unsubscribe, please send an email to: users-unsubscr...@cloudstack.apache.org
Re: External DNS
Andrija, thank you for your answer, but we are looking how to DELETE internal DNS :) Andrija Panic писал 2018-02-01 23:25: Hi, you didn't write what kind of networking you have, are VMs supposed to use VR (advanced networking) for DNS (as deafult) or not. In zone settings, we have set public DNS to google's also, and some internal ones. SSVM and CPVM are assinged both 2 internal, and then 2 external servers (in that order) inside resolv.conf. VRs are assigned only public DNS in resolv.conf all VMs are inside VPC and use VR as it's own DNS server, which furhter proxy to internet etc... Best On 23 January 2018 at 10:48, <m...@cloude.ru> wrote: Hello guys, After installation and configuration cloudstack we got lil problem. We can't use external DNS in our VM's. Every VM's is going up with our internal DNS and Google Public. We are interested to start VM's only with GP DNS. We change settings: use.external.dnsBypass internal dns, use external dns1 and dns2 true We restart management server, VR and all other systems, but do not having effect. It's still using our internal DNS and GP.It's very laggy with our DNS, internet speed only 10Mbps CloudStack: 4.8.0 XenServer 6.5 Anyone have solution?
Re: External DNS
in our VMs in reslolv.conf we have internal IP address of VR as first nameserver, then the public ones... ( use.external.dns set to false on Zone level - zone level settings) On 1 February 2018 at 21:16, <m...@cloude.ru> wrote: > Hello, > > we are using advanced networking > > > > Andrija Panic писал 2018-02-01 23:25: > > Hi, >> >> you didn't write what kind of networking you have, are VMs supposed to use >> VR (advanced networking) for DNS (as deafult) or not. >> >> In zone settings, we have set public DNS to google's also, and some >> internal ones. >> SSVM and CPVM are assinged both 2 internal, and then 2 external servers >> (in >> that order) inside resolv.conf. >> VRs are assigned only public DNS in resolv.conf >> all VMs are inside VPC and use VR as it's own DNS server, which furhter >> proxy to internet etc... >> >> Best >> >> On 23 January 2018 at 10:48, <m...@cloude.ru> wrote: >> >> Hello guys, >>> >>> After installation and configuration cloudstack we got lil problem. >>> >>> We can't use external DNS in our VM's. Every VM's is going up with our >>> internal DNS and Google Public. We are interested to start VM's only with >>> GP DNS. >>> >>> We change settings: use.external.dnsBypass internal dns, use external >>> dns1 and dns2 true >>> We restart management server, VR and all other systems, but do not having >>> effect. It's still using our internal DNS and GP.It's very laggy with >>> our DNS, internet speed only 10Mbps >>> >>> CloudStack: 4.8.0 >>> XenServer 6.5 >>> >>> Anyone have solution? >>> >>> >>> >>> > -- Andrija Panić
Re: External DNS
Hello, we are using advanced networking Andrija Panic писал 2018-02-01 23:25: Hi, you didn't write what kind of networking you have, are VMs supposed to use VR (advanced networking) for DNS (as deafult) or not. In zone settings, we have set public DNS to google's also, and some internal ones. SSVM and CPVM are assinged both 2 internal, and then 2 external servers (in that order) inside resolv.conf. VRs are assigned only public DNS in resolv.conf all VMs are inside VPC and use VR as it's own DNS server, which furhter proxy to internet etc... Best On 23 January 2018 at 10:48, <m...@cloude.ru> wrote: Hello guys, After installation and configuration cloudstack we got lil problem. We can't use external DNS in our VM's. Every VM's is going up with our internal DNS and Google Public. We are interested to start VM's only with GP DNS. We change settings: use.external.dnsBypass internal dns, use external dns1 and dns2 true We restart management server, VR and all other systems, but do not having effect. It's still using our internal DNS and GP.It's very laggy with our DNS, internet speed only 10Mbps CloudStack: 4.8.0 XenServer 6.5 Anyone have solution?
Re: External DNS
Hi, you didn't write what kind of networking you have, are VMs supposed to use VR (advanced networking) for DNS (as deafult) or not. In zone settings, we have set public DNS to google's also, and some internal ones. SSVM and CPVM are assinged both 2 internal, and then 2 external servers (in that order) inside resolv.conf. VRs are assigned only public DNS in resolv.conf all VMs are inside VPC and use VR as it's own DNS server, which furhter proxy to internet etc... Best On 23 January 2018 at 10:48, <m...@cloude.ru> wrote: > Hello guys, > > After installation and configuration cloudstack we got lil problem. > > We can't use external DNS in our VM's. Every VM's is going up with our > internal DNS and Google Public. We are interested to start VM's only with > GP DNS. > > We change settings: use.external.dnsBypass internal dns, use external > dns1 and dns2 true > We restart management server, VR and all other systems, but do not having > effect. It's still using our internal DNS and GP.It's very laggy with > our DNS, internet speed only 10Mbps > > CloudStack: 4.8.0 > XenServer 6.5 > > Anyone have solution? > > > -- Andrija Panić
External DNS
Hello guys, After installation and configuration cloudstack we got lil problem. We can't use external DNS in our VM's. Every VM's is going up with our internal DNS and Google Public. We are interested to start VM's only with GP DNS. We change settings: use.external.dns Bypass internal dns, use external dns1 and dns2 true We restart management server, VR and all other systems, but do not having effect. It's still using our internal DNS and GP.It's very laggy with our DNS, internet speed only 10Mbps CloudStack: 4.8.0 XenServer 6.5 Anyone have solution?
