[
https://issues.apache.org/jira/browse/CLOUDSTACK-3357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13722828#comment-13722828
]
Sheng Yang commented on CLOUDSTACK-3357:
----------------------------------------
Hi Daan,
I am looking into it. But it's better to have some test cases for it, e.g.
ping vm1 doesn't work in vm2, or ping vm1.domain.com doesn't work in vm2.
The description for the issue is too ambiguous. I think before we determining
what cause the trouble, we need to know the troubled scenario first.
Thank you!
> network domain for a vpc is not propagated to the virtual router
> ----------------------------------------------------------------
>
> Key: CLOUDSTACK-3357
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3357
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Affects Versions: 4.0.2, 4.1.0
> Reporter: Daan Hoogland
> Assignee: Daan Hoogland
> Labels: integration-test
> Fix For: 4.2.0
>
>
> network domain for a vpc is propagated to the database but not to the virtual
> routers.
> When creating a new VPC, a network domain is given .This domain would be
> expected to be used in the dns resolution for hosts and be programmed into
> /etc/dnsmasq.conf on the virtual router (containing the dns for that
> network). That file is not touched at all, however.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
