nassh: underscores in DNS names now invalid character
Reported by
brandon....@gmail.com,
Sep 19 2017
|
|
Issue description
Chrome Version : <Copy from: 'about:version'>
URLs (if applicable) :
Other browsers tested:
Add OK or FAIL, along with the version, after other browsers where you
have tested this issue:
Safari:
Firefox:
IE:
What steps will reproduce the problem?
(1) using DNS names with underscores field validation turns the text red and will not allow you to press Connect, change to IP works
(2)
(3)
What is the expected result?
underscores worked previously
What happens instead?
Please provide any additional information below. Attach a screenshot if
possible.
,
Sep 19 2017
Thank you for responding. The mandate must be why it changed. I'll either find an alternate or change all my aliases. Thanks, Brandon
,
Sep 19 2017
usually people just change all the _ to - and that's good enough. and you don't have to hold shift while typing - vs _ :). is the _ an alias you're using in your ssh_config or something ?
,
Sep 19 2017
I use Secure Shell to manage SSH devices on my LAN. Internal DNS is resolving all the names/aliases and underscores are "ok", but as a practice I should probably change them all eventually anyway. Thank you for your time and keep up the good work. |
|
►
Sign in to add a comment |
|
Comment 1 by vapier@chromium.org
, Sep 19 2017Summary: nassh: underscores in DNS names now invalid character (was: underscores in DNS names now invalid character)