If you're going to use the host file then you'll have to copy it to every machine you have every time you update it.
As far as the domain name goes, you can use anything you want, .com .gov .myown The only problem you'll have is if it is already being used which would cause a conflict. 
As long as it's an internal network you can call it anything you want. 
I'm not sure what you mean by non- routable domain, you set up the routing so that's what determines if a network is routable or not
Using an internal IP 10. 192.168. is what prevents people on the outside from getting in.

Setting up the DNS is not that hard and then just pointing your DHCP server to it simplifies the whole thing.


On Wed, Nov 23, 2022, 9:26 AM Keith Smith via PLUG-discuss <plug-discuss@lists.phxlinux.org> wrote:


Hi,

As you know I am building a "home office" lab for PHP development and
testing.  I was not satisfied with the research I completed on
"non-routeable" domains for a private network made up of "non-routeable"
domains.

In the distant past I used to use .dev for the TLD.  From what I am
reading this is not a good idea.

According to https://www.rfc-editor.org/rfc/rfc8375.html one should use
"home.arpa.".  They add a period to the end which I assume is the DNS
domain name stop character when used in zone files.  Any thoughts?

I will not be using DNS.  My needs are so simple I will be adding the IP
and domain name in my host file, at least for now.

I've read a lot about this subject.  Some say to use a registered domain
with a subdomain that is on a private IP. I really do not want to
commingle public and private assets on the same domain.

Any feedback is much appreciated!!

Thanks!!
Keith


---------------------------------------------------
PLUG-discuss mailing list: PLUG-discuss@lists.phxlinux.org
To subscribe, unsubscribe, or to change your mail settings:
https://lists.phxlinux.org/mailman/listinfo/plug-discuss