On Sun, 2016-01-31 at 12:57 -0500, bruce wrote:
As far as I can tell, most of the sites say you need to already have
a
"name" from a domain name provider. That can't be right, can it!! One
can have a dns process internal to an org, providing dns names to
machines all over the place. Granted, those machines/names might be
internal/private.
If it's wholly internal (i.e. any lookups are from machines within the
network), you don't need an globally recognized name. You can use
/etc/hosts or dnsmasq.
So, does one need an "actual" real name for an externally
facing
server in order to process the DNS so one can do a "ssh test(a)foo.com"
or can you use something like "ssh test(a)foo.example.com"
Even if your home network is hidden behind an ISP NAT router, getting
your own domain is quite simple. Providers such as DynDNS (
www.dyn.com)
or NO-IP (
www.noip.com) offer DNS registration (either paid or free
with restrictions). You also need a dynamic DNS client to keep them up
to date, but most modern routers can do that for you.
poc