[15:36] <MarvinTheMArtian> Hello everyone. I'm trying to setup a homelab/intranet Ubuntu server. First, I'm doing it in a VM, but as soon as the Raspberry PI 4 8GB is finally delivered, I'll use that. But reading Ubuntu Server Guide, I'm left with a few questions. When setting up intranet, what would be the practice for a hostname? I don't want to register a domain, this will not be a publicly available server.
[15:40] <tomreyn> MarvinTheMArtian: you can pick any, ideally one that's not publically available. so pick something unique that's not likely going to be registered for public use anytime soon.
[15:41] <tomreyn> some sites may suggest using .lan or .local, but those actually have specific purposes in some contexts
[16:00] <MarvinTheMArtian> tomreyn: I was thinking of using .home
[16:05] <tomreyn> apparently that's safe in regard to public use https://en.wikipedia.org/wiki/.home
[16:06] <MarvinTheMArtian> stupid question, do I name my server "ubuntu-intranet-serv" or "ubuntu-intranet-serv.home"?
[16:06] <MarvinTheMArtian> as a hostname
[16:43] <MarvinTheMArtian> Also, a nOOb question, if I want to have subdomains per service, like mail.ubuntu-intranet-serv.home, xmpp.ubuntu-intranet-serv.home and so on, I need to setup a DNS server on the server as well? I'm not going to be able to use the Router's DNS?
[17:34] <tomreyn> MarvinTheMArtian: some home routers would actually define a domain name, so you could just go with that
[17:35] <tomreyn> alternatively, yes, you'd need to configure the domain name and hostnames either centrally, and hand it out to computers on the network, or configure it on each of the computers in the network.
[18:37] <MarvinTheMArtian> @tomreyn: bind9 being the dns server of choice?
[18:47] <tomreyn> MarvinTheMArtian: it's one of them, there are others, i can't make a recommendation.
[19:45] <mason> MarvinTheMArtian: I'm comfortable saying "yes, use BIND 9" as it's got a decent support community and is probably the purest example of how DNS works. To add to other ideas, you can also get a domain name and have your home stuff use an internal subdomain off of the public domain. If you don't ever envision needing this, it'd indeed be extra complexity, but depending on what you want to learn it 
[19:45] <mason> could be useful.
[19:52] <tomreyn> but keep in mind that this could get you in serious trouble if that domain name was ever to expire while it's still being used for this purpose
[20:10] <mason> Interesting. Yeah, funny things could happen potentially.