You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "dsclose (JIRA)" <ji...@apache.org> on 2016/06/01 16:01:01 UTC
[jira] [Commented] (CLOUDSTACK-9400) RvR should present virtual IP
for name resolution
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15310535#comment-15310535 ]
dsclose commented on CLOUDSTACK-9400:
-------------------------------------
I was preparing a PR for this but after pulling upstream i see that this was addressed in commit c269097a278b9bdf5b9ded457172ce3bf7b707ad, by Nuno Tavares.
Case closed.
> RvR should present virtual IP for name resolution
> -------------------------------------------------
>
> Key: CLOUDSTACK-9400
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9400
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Affects Versions: 4.8.0
> Reporter: dsclose
> Priority: Minor
> Labels: easyfix
>
> Virtual routers are assigned name servers via the kernel arguments. These name servers are also presented via DHCP to guest VMs - but the virtual router prepends these name servers with it's own guest IP. This allows the virtual router to act as a name resolver for guest VMs.
> With redundant virtual routers, the router's guest IP is not the same as the virtual gateway IP. This means that after a failover or a network restart, guest VMs will not be able to find the name server assigned via DHCP and this causes delays whenever name resolution is needed.
> Redundant virtual routers should provide the guest gateway IP to guest VMs instead of their own guest IP. This will allow name resolver functionality to continue after failover or network restart events.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)