# fly ssh console fails with \`Error host unavailable: host was not found in DNS\`

**URL:** <https://community.fly.io/t/fly-ssh-console-fails-with-error-host-unavailable-host-was-not-found-in-dns/5781>\
**Category:** Questions / Help\
**Created:** [June 26, 2022, 6:53pm UTC](https://community.fly.io/t/fly-ssh-console-fails-with-error-host-unavailable-host-was-not-found-in-dns/5781 "2022-06-26T18:53:44Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![ignoramous](https://avatars.discourse-cdn.com/v4/letter/i/a9adbd/32.png) [@ignoramous](https://community.fly.io/u/ignoramous)\
**Post date:** [June 28, 2022, 12:45pm UTC](https://community.fly.io/t/fly-ssh-console-fails-with-error-host-unavailable-host-was-not-found-in-dns/5781/5 "2022-06-28T12:45:44Z")

</div>

Neat! Fly’s internal DNS has been going through quite a few road bumps, of late.

Btw, I almost sent a pull-request for flyctl to let its users `ssh` into a vm using private ip and as fate would have it, this is already supported ([code](https://github.com/superfly/flyctl/blob/44ea4881ae7d52c894d224aabb8a66a086ea66e9/cmd/ssh_terminal.go#L127)).

For future:

```auto
$ flyctl ips private
  ID | REGION | IP                                
-----------*--------*-----------------------------------
  ddddeeee | aws | fdaa:0:aaaa:bbb:cccc:dddd:eeee:2  

$ flyctl ssh console "[fdaa:0:aaaa:bbb:cccc:dddd:eeee:2]"

```

---

_[View the full topic](https://community.fly.io/t/fly-ssh-console-fails-with-error-host-unavailable-host-was-not-found-in-dns/5781)._