[
https://issues.apache.org/jira/browse/CLOUDSTACK-3357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13724401#comment-13724401
]
Sheng Yang commented on CLOUDSTACK-3357:
----------------------------------------
This bug need QA to verify.
> 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: Sheng Yang
> Priority: Critical
> 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.
> Reproduce steps:
> 1. Create VPC with domain "testdomain.internal"
> 2. Create a network inside VPC.
> 3. Create 2 VMs, named vm1 and vm2 in the network.
> Two guest VMs are not able to ping each other using name, e.g. "ping vm1" in
> vm2 failed.
> Two guest VMs are not able to ping each other using name.domain, e.g. "ping
> vm1.testdomain.internal" in vm2 failed.
--
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
