On 10/14/14 12:19, bruce wrote:
so essentially,
the process would have each system in the sub net, report it's
address/name to the external dyndns service, where it would be
managed/returned as a subname, which would then populate the
local/internal resolv.conf (or whatever is required) to allow the
local services/users of the subnet the ability to access the boxes by
the "subnames"...
could work..
First, it may or may not be a subdomain.... But it would be a unique FQDN (Fully
Qualified Domain Name).
Second, there is no need to alter any resolv.conf since the hostname is held in the
standard DNS.
Just do some common name lookups....
host
roger.dnsdynamic.com
host
maria.dnsdynamic.com
host
sam.dnsdynamic.com
You'll find the IP addresses associated with the hosts are not within the range owned
by
dnsdynamic.com.
Typically, this method is used for allowing for name resolution to route-able IP addresses
so folks on the internet can assess you systems.
But, there is nothing wrong with sending internal non-route-able addresses so you could
access internal systems by name without too much hassle.
--
If you can't laugh at yourself, others will gladly oblige.