|
my sql created JENKINS-12141:
-------------------------------- Summary: domain can't find Key: JENKINS-12141 URL: https://issues.jenkins-ci.org/browse/JENKINS-12141 Project: Jenkins Issue Type: Bug Components: ec2 Affects Versions: current Environment: local eucalyptus Reporter: my sql Assignee: Kohsuke Kawaguchi C:\>ssh euca-10-135-236-221.eucalyptus.beclos60.china.nsn-net.net ssh: Could not resolve hostname euca-10-135-236-221.eucalyptus.beclos60.china.nsn-net.net: hostname nor servname I tested the EC2 plugin in my local eucalyptus server, hostname can't find due to ip 10.135.236.221 can't get by DNS automatically. Could you private a way to ssh connect by ip than full public domain DNS? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
[ https://issues.jenkins-ci.org/browse/JENKINS-12141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] francis Upton updated JENKINS-12141: ------------------------------------ Summary: Allow connecting to an instance using an IP address instead of the domain name (was: domain can't find) > Allow connecting to an instance using an IP address instead of the domain name > ------------------------------------------------------------------------------ > > Key: JENKINS-12141 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12141 > Project: Jenkins > Issue Type: Bug > Components: ec2 > Affects Versions: current > Environment: local eucalyptus > Reporter: my sql > Assignee: Kohsuke Kawaguchi > > C:\>ssh euca-10-135-236-221.eucalyptus.beclos60.china.nsn-net.net > ssh: Could not resolve hostname euca-10-135-236-221.eucalyptus.beclos60.china.nsn-net.net: hostname nor servname > I tested the EC2 plugin in my local eucalyptus server, hostname can't find due to ip 10.135.236.221 can't get by DNS automatically. > Could you private a way to ssh connect by ip than full public domain DNS? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
In reply to this post by JIRA noreply@jenkins-ci.org
[ https://issues.jenkins-ci.org/browse/JENKINS-12141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] francis Upton updated JENKINS-12141: ------------------------------------ Issue Type: New Feature (was: Bug) > Allow connecting to an instance using an IP address instead of the domain name > ------------------------------------------------------------------------------ > > Key: JENKINS-12141 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12141 > Project: Jenkins > Issue Type: New Feature > Components: ec2 > Affects Versions: current > Environment: local eucalyptus > Reporter: my sql > Assignee: Kohsuke Kawaguchi > > C:\>ssh euca-10-135-236-221.eucalyptus.beclos60.china.nsn-net.net > ssh: Could not resolve hostname euca-10-135-236-221.eucalyptus.beclos60.china.nsn-net.net: hostname nor servname > I tested the EC2 plugin in my local eucalyptus server, hostname can't find due to ip 10.135.236.221 can't get by DNS automatically. > Could you private a way to ssh connect by ip than full public domain DNS? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira |
| Powered by Nabble | See how NAML generates this page |
