System (local) domain name best practices?
-
What's the best practice for configuring the pfSense host and domain name? Can I include a subdomain in my domain name setting?
For example, if I own the public domain "example.com", I'd like to use an unused/fake subdomain ("home") for my home network with pfSense.
Therefore, my system domain-name would be "home.example.com" and my host name would be "router" so the FQDN would be "router.home.example.com" and my other clients would be "client-one.home.example.com".
Is this a best practice or are there any other ideas?
Thanks!
-
For example, if I own the public domain "example.com", I'd like to use an unused/fake subdomain ("home") for my home network with pfSense.
Therefore, my system domain-name would be "home.example.com" and my host name would be "router" so the FQDN would be "router.home.example.com" and my other clients would be "client-one.home.example.com".
I do this exact setup with my domain name (though different hostnames). Some people might just make the domain "home" or "local"… it doesn't need to be a real domain, but there's no harm in using a real domain.
-
If you own "example.com" you can certain use whatever subdomains however you like.
If not using a real domain name for a home or interior AD domain, I like ".loc". I can't recall the details, but ".local" is used for something else (Bonjour? mDNS?)
-
Yeah, Bonjour/mDNS uses the TLD .local so that definitely can't be used.
-
-
Thanks so much!