name resolution

[Tom H]

On Fri, Nov 24, 2017 at 8:39 AM, Gene Heskett <gheskett at shentel.net> wrote:
> On Friday 24 November 2017 02:07:26 Nils Kassube wrote:
>>
>> 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.

As long as you're running an internal dns server, you can use almost
any domain name in an internal network; almost.