cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sheng Yang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-1481) IPV6 - When Vm is part of 1 dual network and 1 ipv6 network , name resolution using fqdn fails for the ipv6 network.
Date Sat, 02 Mar 2013 01:20:11 GMT

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-1481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13591185#comment-13591185
] 

Sheng Yang commented on CLOUDSTACK-1481:
----------------------------------------

According to Anthony, we would only pass DNS and domain name from default network, and ignore
all the setting from other networks.
                
> IPV6 - When Vm is part of 1 dual network and 1 ipv6 network , name resolution using fqdn
fails for the ipv6 network.
> --------------------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-1481
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1481
>             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
>         Environment: Latest build from newtorkrefactor branch.
>            Reporter: Sangeetha Hariharan
>            Assignee: Sheng Yang
>             Fix For: 4.1.0
>
>
> IPV6 - When Vm is part of 1 dual network and 1 ipv6 network , name resolution using fqdn
fails for the ipv6 network.
> Steps to reproduce the problem:
> create a dual stack network N1.
> create a ipv6 network N2.
> Deploy a 2 Vms in N1 and N2.
> From 1 VM, try to access other VM using its fully qualified domain name.
> It fails.
> I see the domain name of N2 is not being programmed  in /etc/resolv.conf. Only the domain
name of N1 is programmed.
> sangeetha@ubuntu-123:~$ cat /etc/resolv.conf
> # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
> #     DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
> nameserver 10.223.137.66
> nameserver fc00:3:1371::6a19:fed0:1932:3626
> nameserver fc00:3:1382::ff2b:1c9e:278c:48c7
> search hello1371
> sangeetha@ubuntu-123:~$ ssh tam-dual-ipv6-2.hello1382
> ssh: Could not resolve hostname tam-dual-ipv6-2.hello1382: Name or service not known
> sangeetha@ubuntu-123:~$ ssh tam-dual-ipv6-2.hello1371
> The authenticity of host 'tam-dual-ipv6-2.hello1371 (fc00:3:1371:0:2f17:d569:ae3b:c143)'
can't be established.
> ECDSA key fingerprint is 36:10:4b:27:e3:f2:18:df:85:26:f7:ab:c6:1a:72:01.
> Are you sure you want to continue connecting (yes/no)? no
> Host key verification 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

Mime
View raw message