Jeremy Nicoll wrote:
> On Thu, 15 Feb 2018, at 16:21, Dan Purgert wrote:
>> > Later, once you understand how a local network works, you can come
>> > up with a theme.  Or some convention that lets you identify the
>> > computer by its name.  The name that you have chosen.
> Machine-naming makes sense to me - having done that with a variety
> of (blush) Windows machines in my LAN.  I've toyed with versions of 
> Linux, and used a few live-CD ones over the years, and I'm fairly sure
> that as well as being asked to supply a hostname I've also been asked 
> to supply a domain value.
> What, on a home LAN, is that used for?

In general terms, supplying domain information at setup time adds a
"helper" record to /etc/resolv.conf (or whatever RH, Windows, etc.
uses).  Note that if you use DHCP, this step is usually skipped, as the
DHCP server provides the information.

In short, the "helper" record appends the domain name to a hostname, so
you don't have to type out a FQDN when you're trying to get to a remote

For example, you can use "scp file you@target:/path" instead of "scp
file you@target.somedomain.sometld:/path".

In addition, there is the special TLD ".local", which is reserved for
bonjour / avahi (zeroconf service discovery, apple uses it a lot).

|_|O|_| Registered Linux user #585947
|_|_|O| Github:
|O|O|O| PGP: 05CA 9A50 3F2E 1335 4DC5  4AEE 8E11 DDF3 1279 A281

Reply via email to