You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Sheng Yang (JIRA)" <ji...@apache.org> on 2013/06/08 02:26:20 UTC
[jira] [Resolved] (CLOUDSTACK-1752) IPV6 - Router of a ipv6 network
has external ipv4 dns entries programmed in /etc/resolv.conf
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sheng Yang resolved CLOUDSTACK-1752.
------------------------------------
Resolution: Won't Fix
The control nic is assigned ipv4 addresses(though we won't expect it can go internet), so keep the ipv4 dns is somehow reasonable.
As long as guest won't get ipv4 dns for pure ipv6 IP, it should be fine.
Decide not to fix it.
> IPV6 - Router of a ipv6 network has external ipv4 dns entries programmed in /etc/resolv.conf
> ---------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-1752
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1752
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Components: Management Server
> Affects Versions: 4.1.0, 4.2.0
> Environment: Build from 4.1
> Reporter: Sangeetha Hariharan
> Assignee: Sheng Yang
> Fix For: 4.2.0
>
>
> IPV6 - Router of a ipv6 network , has external ipv4 dns entries programmed in /etc/resolv.conf .
> Steps to reproduce the problem:
> Create a IPV6 network.
> Deploy a VM in this network.
> Router that gets created for this network has external ipv4 dns entries programmed in /etc/resolv.conf in addition to the external ipv6 dns entries.
> root@r-8-VM:~# cat /etc/resolv.conf
> # Generated by NetworkManager
> domain citrite.net
> search citrite.net
> nameserver 72.52.126.11
> nameserver 72.52.126.12
> nameserver FC00:3:1333::1
> nameserver FC00:3:1333::ffff
> There is no need for ipv4 dns entries to be programmed in /etc/resolv.conf.
--
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