I have my own domain, so I use a subdomain that is not on my public dns servers for internal use. You can use anything in the domain part but you really don't want there to ever be a possibility of a collision with a real world domain. .lan is a common default, .localdomain was also frequently used and ive seen .home used as well. If you do have your own domain just make up a subdomain that works for you. in my case I am using .ad.(mydomain).net because I am playing with samba-ad-dc On Tue, Jan 21, 2020, 13:29 o1bigtenor <o1bigtenor at gmail.com> wrote: > Greetings > > I would like to setup a server that is for in house use only. This is > not for outside use. > > So I'm trying to understand what is a good way to setup the hostname > for the server. > Do I use localhost? > Do I use example.com? > > Is there some other way to refer to something like a communication/info > server? > For this thinking maybe something like using the lan NAT address > for the machine. > > I'm not even sure I'm asking the question 'right' and the 'web' is > being singularly unhelpful! > > TIA > _______________________________________________ > TCLUG Mailing List - Minneapolis/St. Paul, Minnesota > tclug-list at mn-linux.org > http://mailman.mn-linux.org/mailman/listinfo/tclug-list > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mailman.mn-linux.org/pipermail/tclug-list/attachments/20200121/38c6322d/attachment.htm>