name resolution

Gene Heskett gheskett at shentel.net
Fri Nov 24 13:39:57 UTC 2017


On Friday 24 November 2017 02:07:26 Nils Kassube wrote:

> Xen wrote:
> > So by all extents and purposes, you should put mDNS AFTER DNS,
> > unless of course
> >
> > YOU WANT TO EXTINGUISH THE USE OF THE LOCAL DOMAIN BY FORCIBLE
> > MEASURES.
> >
> > Which they are doing.
> >
> > Not practical necessity.
> >
> > Politics.
>
> As I understand it, you are not supposed to use any private domain
> names.

Thats BS, the warm, squishy stuff usually found on the ground behind the 
male bovine.

> Otherwise ICANN would have reserved a specific domain name for 
> private use, just like there are private IP adresses. So if you use an
> unregistered domain name you are on your own and have to live with the
> consequences if it gets assigned for something else. If you want to
> avoid that the domain name of your LAN is in use or gets "stolen" by
> someone else, you should register a domain.

I have, see my sig, thats actually this machine, but it is NOT my local 
domain name and never will be.

ICANN does not, cannot, control what I use for a domain name on my side 
of a router doing NAT for you to gain access to my web pages via my 
registered domain name, in fact that lack of a dns resolution is part of 
my security model.  And its worked well, only one person has gained 
access to my local network system in a decade+, and I had to give him 
the passwords to get past every layer of that security. dd-wrt is very 
good at what it does.

> Nils


Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>




More information about the ubuntu-users mailing list