solution for a quick/robust/secure broadcast issue

[bruce]

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..


On Mon, Oct 13, 2014 at 11:49 PM, Ed Greshko <ed.greshko at greshko.com> wrote:
> On 10/14/14 11:39, Tim wrote:
>> Allegedly, on or about 14 October 2014, Ed Greshko sent:
>>> It may be easier for him to use a Dynamic DNS service, such as
>>> http://www.dnsdynamic.org/,  and ddclient on the Fedora side.
>> Wouldn't that just return the public facing address of the network,
>> rather than the individual client addresses?
>>
>
> No.....
>
> You would request sign-up for the service and use their internal domain of dnsdynamic.com and request a subdomain of that.  Then you'd give you systems hostname.mysub.dnsdynamic.com.  Then you'd configure ddclient to send you system's IP address to dnsdynamic.com when it changes.
>
> Typically, you'd then send it your internal, non-routeable IP address such as 192.168.0.12.  You'd do this for all of your systems and then have them address the other systems by these assigned names.
>
>
> --
> If you can't laugh at yourself, others will gladly oblige.
>
> --
> users mailing list
> users at lists.fedoraproject.org
> To unsubscribe or change subscription options:
> https://admin.fedoraproject.org/mailman/listinfo/users
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
> Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
> Have a question? Ask away: http://ask.fedoraproject.org