Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #262782

Re: Domain name to use on home networks

From Pocket <pocket@columbus.rr.com>
Newsgroups linux.debian.user
Subject Re: Domain name to use on home networks
Date 2023-10-27 16:20 +0200
Message-ID <HtvQR-1eXS-3@gated-at.bofh.it> (permalink)
References <HtvHb-1eUN-5@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw

[Converted from HTML] - view raw


Sent from my iPad


> On Oct 27, 2023, at 10:00 AM, Andrew M.A. Cater <amacater@einval.com> wrote:
> 

> On Fri, Oct 27, 2023 at 09:30:09AM -0400, Pocket wrote:
> 
> > 
> 
> > 
> 
> > Sent from my iPad
> 
> > 
> 
> > > On Oct 27, 2023, at 9:05 AM, Greg Wooledge <greg@wooledge.org> wrote:
> 
> > > 
> 
> > > On Fri, Oct 27, 2023 at 07:59:00AM -0400, Pocket wrote:
> 
> > > > > On 10/27/23 07:50, Greg Wooledge wrote:
> 
> > > > > On Fri, Oct 27, 2023 at 07:29:20AM -0400, Pocket wrote:
> 
> > > > > > /etc/hosts
> 
> > > > > If you're using short-form hostnames like this:
> 
> > > > > 
> 
> > > > > unicorn:~$ hostname
> 
> > > > > unicorn
> 
> > > > > 
> 
> > > > > then yeah, that's all you need.  If you're using long-form hostnames
> 
> > > > > (with dots in them), then you also need to configure /etc/hostname.
> 
> > > > > 
> 
> hostnamectl set-hostname is the command to do it - and will survive a
> reboot.
> 
> Andy
> 

From the man page

## THE FQDN

The FQDN (Fully Qualified Domain Name) of the system is the name that
the **[resolver][1]**(3) returns for the host name, such
as, ursula.example.com. It is usually the hostname followed by the DNS domain
name (the part after the first dot). You can check the FQDN using **hostname
--fqdn** or the domain name using **dnsdomainname**.

You cannot change the FQDN with **hostname** or **dnsdomainname**.

The recommended method of setting the FQDN is to make the hostname be an alias
for the fully qualified name using /etc/hosts, DNS, or NIS. For example, if
the hostname was "ursula", one might have a line in /etc/hosts which reads

**
  127.0.1.1 ursula.example.com ursula

Technically: The FQDN is the name **[getaddrinfo][2]**(3) returns for the host
name returned by**[gethostname][3]**(2). The DNS domain name is the part after
the first dot.

Therefore it depends on the configuration of the resolver (usually
in /etc/host.conf) how you can change it. Usually the hosts file is parsed
before DNS or NIS, so it is most common to change the FQDN in /etc/hosts.

If a machine has multiple network interfaces/addresses or is used in a mobile
environment, then it may either have multiple FQDNs/domain names or none at
all. Therefore avoid using**hostname --fqdn**, **hostname
--domain** and **dnsdomainname**. **hostname --ip-address** is subject to the
same limitations so it should be avoided as well.

[1]: https://manpages.org/resolver/3
[2]: https://manpages.org/getaddrinfo/3
[3]: https://manpages.org/gethostname/2

Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

Bookworm: NetworkManager Pocket <pocket@columbus.rr.com> - 2023-10-21 18:40 +0200
  Re: Bookworm: NetworkManager Greg Wooledge <greg@wooledge.org> - 2023-10-21 18:50 +0200
    Re: Bookworm: NetworkManager Pocket <pocket@columbus.rr.com> - 2023-10-21 19:10 +0200
      Re: Bookworm: NetworkManager Greg Wooledge <greg@wooledge.org> - 2023-10-21 19:30 +0200
        Re: Bookworm: NetworkManager Pocket <pocket@columbus.rr.com> - 2023-10-21 19:40 +0200
          Re: Bookworm: NetworkManager Greg Wooledge <greg@wooledge.org> - 2023-10-21 20:00 +0200
            Re: Bookworm: NetworkManager Pocket <pocket@columbus.rr.com> - 2023-10-21 20:10 +0200
        Re: Bookworm: NetworkManager Max Nikulin <manikulin@gmail.com> - 2023-10-22 10:10 +0200
          Re: Bookworm: NetworkManager Pocket <pocket@columbus.rr.com> - 2023-10-22 14:30 +0200
            Re: Bookworm: NetworkManager Pocket <pocket@columbus.rr.com> - 2023-10-22 14:50 +0200
            Re: Bookworm: NetworkManager Michael Kjörling <2695bd53d63c@ewoof.net> - 2023-10-22 15:20 +0200
            Re: Bookworm: NetworkManager Max Nikulin <manikulin@gmail.com> - 2023-10-22 18:50 +0200
              Re: Bookworm: NetworkManager Pocket <pocket@columbus.rr.com> - 2023-10-22 19:50 +0200
            Re: Bookworm: NetworkManager Andy Smith <andy@strugglers.net> - 2023-10-22 19:40 +0200
              Re: Bookworm: NetworkManager Pocket <pocket@columbus.rr.com> - 2023-10-22 20:00 +0200
        Re: Bookworm: NetworkManager Henning Follmann <hfollmann@itcfollmann.com> - 2023-10-22 17:10 +0200
          Re: Bookworm: NetworkManager gene heskett <gheskett@shentel.net> - 2023-10-22 18:30 +0200
            Re: Bookworm: NetworkManager Dan Ritter <dsr@randomstring.org> - 2023-10-22 20:40 +0200
            Re: Bookworm: NetworkManager Max Nikulin <manikulin@gmail.com> - 2023-10-24 18:50 +0200
              Re: Bookworm: NetworkManager Pocket <pocket@columbus.rr.com> - 2023-10-24 19:30 +0200
                Re: Bookworm: NetworkManager "Andrew M.A. Cater" <amacater@einval.com> - 2023-10-24 19:40 +0200
                Re: Bookworm: NetworkManager gene heskett <gheskett@shentel.net> - 2023-10-25 03:10 +0200
                Re: Bookworm: NetworkManager David Wright <deblis@lionunicorn.co.uk> - 2023-10-25 03:50 +0200
                link-local 169.254.x.y addresses Max Nikulin <manikulin@gmail.com> - 2023-10-25 18:50 +0200
              Re: Bookworm: NetworkManager Andy Smith <andy@strugglers.net> - 2023-10-25 01:40 +0200
        Alternative to NetworkManager on Debian 12 Alessandro Baggi <alessandro.baggi@gmail.com> - 2023-11-01 11:50 +0100
          Re: Alternative to NetworkManager on Debian 12 Greg Wooledge <greg@wooledge.org> - 2023-11-01 12:20 +0100
            Re: Alternative to NetworkManager on Debian 12 Nicolas George <george@nsup.org> - 2023-11-01 12:40 +0100
              Re: Alternative to NetworkManager on Debian 12 Max Nikulin <manikulin@gmail.com> - 2023-11-01 17:10 +0100
                Re: Alternative to NetworkManager on Debian 12 Nicolas George <george@nsup.org> - 2023-11-01 17:20 +0100
          Re: Alternative to NetworkManager on Debian 12 yxcv@vienna.at - 2023-11-01 12:20 +0100
            Re: Alternative to NetworkManager on Debian 12 <tomas@tuxteam.de> - 2023-11-01 12:20 +0100
          Re: Alternative to NetworkManager on Debian 12 <tomas@tuxteam.de> - 2023-11-01 12:20 +0100
            Re: Alternative to NetworkManager on Debian 12 Felix Miata <mrmazda@earthlink.net> - 2023-11-01 15:20 +0100
              Re: Alternative to NetworkManager on Debian 12 <tomas@tuxteam.de> - 2023-11-01 15:40 +0100
                Re: Alternative to NetworkManager on Debian 12 Alessandro Baggi <alessandro.baggi@gmail.com> - 2023-11-01 15:50 +0100
                Re: Alternative to NetworkManager on Debian 12 Max Nikulin <manikulin@gmail.com> - 2023-11-01 16:10 +0100
                Re: Alternative to NetworkManager on Debian 12 <tomas@tuxteam.de> - 2023-11-01 18:50 +0100
                Re: Alternative to NetworkManager on Debian 12 Max Nikulin <manikulin@gmail.com> - 2023-11-02 16:50 +0100
                Re: Alternative to NetworkManager on Debian 12 Jeffrey Walton <noloader@gmail.com> - 2023-11-02 18:00 +0100
                Re: Alternative to NetworkManager on Debian 12 <tomas@tuxteam.de> - 2023-11-02 19:00 +0100
                Re: Alternative to NetworkManager on Debian 12 Max Nikulin <manikulin@gmail.com> - 2023-11-03 16:50 +0100
                Re: Alternative to NetworkManager on Debian 12 debian-user@howorth.org.uk - 2023-11-01 21:00 +0100
          Re: Alternative to NetworkManager on Debian 12 "Marco M." <mm@dorfdsl.de> - 2023-11-01 12:30 +0100
            Re: Alternative to NetworkManager on Debian 12 Joe <joe@jretrading.com> - 2023-11-01 13:20 +0100
      Making resolv.conf immutable [was: Bookworm: NetworkManager] <tomas@tuxteam.de> - 2023-10-22 07:20 +0200
  Re: Bookworm: NetworkManager Felix Miata <mrmazda@earthlink.net> - 2023-10-21 20:00 +0200
    Re: Bookworm: NetworkManager Pocket <pocket@columbus.rr.com> - 2023-10-21 20:20 +0200
      Re: Bookworm: NetworkManager Stefan Monnier <monnier@iro.umontreal.ca> - 2023-10-21 20:40 +0200
        Re: Bookworm: NetworkManager Pocket <pocket@columbus.rr.com> - 2023-10-21 20:50 +0200
          Re: Bookworm: NetworkManager Christoph Brinkhaus <c.brinkhaus@t-online.de> - 2023-10-21 21:00 +0200
            Re: Bookworm: NetworkManager Pocket <pocket@columbus.rr.com> - 2023-10-21 21:20 +0200
          Re: Bookworm: NetworkManager Stefan Monnier <monnier@iro.umontreal.ca> - 2023-10-21 21:10 +0200
            Re: Bookworm: NetworkManager Pocket <pocket@columbus.rr.com> - 2023-10-21 21:40 +0200
              Re: Bookworm: NetworkManager Greg Wooledge <greg@wooledge.org> - 2023-10-21 21:50 +0200
                Re: Bookworm: NetworkManager Pocket <pocket@columbus.rr.com> - 2023-10-21 22:00 +0200
                Re: Bookworm: NetworkManager Stefan Monnier <monnier@iro.umontreal.ca> - 2023-10-21 23:40 +0200
              Re: Bookworm: NetworkManager <tomas@tuxteam.de> - 2023-10-22 07:30 +0200
                Re: Bookworm: NetworkManager Pocket <pocket@columbus.rr.com> - 2023-10-22 14:40 +0200
          Re: Bookworm: NetworkManager Charles Curley <charlescurley@charlescurley.com> - 2023-10-21 22:50 +0200
            Re: Bookworm: NetworkManager Greg Wooledge <greg@wooledge.org> - 2023-10-21 23:00 +0200
              Re: Bookworm: NetworkManager Pocket <pocket@columbus.rr.com> - 2023-10-21 23:20 +0200
            Re: Bookworm: NetworkManager Pocket <pocket@columbus.rr.com> - 2023-10-21 23:20 +0200
              Re: Domain name to use on home networks; was: Bookworm:  NetworkManager Michael Kjörling <2695bd53d63c@ewoof.net> - 2023-10-22 13:20 +0200
                Re: Domain name to use on home networks; was: Bookworm:  NetworkManager Pocket <pocket@columbus.rr.com> - 2023-10-22 14:30 +0200
                Re: Domain name to use on home networks; was: Bookworm: NetworkManager Jeffrey Walton <noloader@gmail.com> - 2023-10-22 17:20 +0200
                Re: Domain name to use on home networks; was: Bookworm:  NetworkManager gene heskett <gheskett@shentel.net> - 2023-10-22 19:00 +0200
                Re: Domain name to use on home networks; was: Bookworm: NetworkManager John Hasler <john@sugarbit.com> - 2023-10-22 20:20 +0200
                Re: Domain name to use on home networks Michael Kjörling <2695bd53d63c@ewoof.net> - 2023-10-22 20:40 +0200
                Re: Domain name to use on home networks; was: Bookworm:  NetworkManager gene heskett <gheskett@shentel.net> - 2023-10-23 00:10 +0200
                Re: Domain name to use on home networks; was: Bookworm: NetworkManager John Hasler <john@sugarbit.com> - 2023-10-23 00:50 +0200
                Re: Domain name to use on home networks; was: Bookworm:  NetworkManager gene heskett <gheskett@shentel.net> - 2023-10-23 02:40 +0200
                Re: Domain name to use on home networks; was: Bookworm:  NetworkManager Greg Wooledge <greg@wooledge.org> - 2023-10-23 02:50 +0200
                Re: Domain name to use on home networks; was: Bookworm:NetworkManager John Hasler <john@sugarbit.com> - 2023-10-23 04:40 +0200
                Re: Domain name to use on home networks; was: Bookworm:NetworkManager Stefan Monnier <monnier@iro.umontreal.ca> - 2023-10-23 05:10 +0200
                Re: Domain name to use on home networks; was: Bookworm:NetworkManager Max Nikulin <manikulin@gmail.com> - 2023-10-23 09:20 +0200
                Re: Domain name to use on home networks; was: Bookworm:NetworkManager gene heskett <gheskett@shentel.net> - 2023-10-23 17:20 +0200
                Re: Domain name to use on home networks; was: Bookworm:NetworkManager gene heskett <gheskett@shentel.net> - 2023-10-23 18:00 +0200
                Re: Domain name to use on home networks; was: Bookworm:NetworkManager gene heskett <gheskett@shentel.net> - 2023-10-23 04:40 +0200
                Re: Domain name to use on home networks; was: Bookworm:NetworkManager Andy Smith <andy@strugglers.net> - 2023-10-23 22:40 +0200
                Re: Domain name to use on home networks; was: Bookworm:NetworkManager gene heskett <gheskett@shentel.net> - 2023-10-24 02:00 +0200
                Re: Domain name to use on home networks; was: Bookworm:  NetworkManager Dan Ritter <dsr@randomstring.org> - 2023-10-22 20:40 +0200
                Re: Domain name to use on home networks; was: Bookworm: NetworkManager Jeffrey Walton <noloader@gmail.com> - 2023-10-22 21:10 +0200
                Re: Domain name to use on home networks; was: Bookworm:NetworkManager gene heskett <gheskett@shentel.net> - 2023-10-22 23:50 +0200
                Re: Domain name to use on home networks; was: Bookworm:NetworkManager ghe2001 <ghe2001@protonmail.com> - 2023-10-23 02:00 +0200
                Re: Domain name to use on home networks; was: Bookworm:NetworkManager Jeffrey Walton <noloader@gmail.com> - 2023-10-23 07:40 +0200
                Re: Domain name to use on home networks; was: Bookworm:NetworkManager Christian Groessler <chris@groessler.org> - 2023-10-23 12:40 +0200
                Re: Domain name to use on home networks; was: Bookworm:NetworkManager David Wright <deblis@lionunicorn.co.uk> - 2023-10-25 03:50 +0200
                Re: Domain name to use on home networks; was: Bookworm:NetworkManager ghe2001 <ghe2001@protonmail.com> - 2023-10-25 05:50 +0200
                Re: Domain name to use on home networks; was:  Bookworm:NetworkManager "Marco M." <mm@dorfdsl.de> - 2023-10-25 07:40 +0200
                Re: Domain name to use on home networks Michael Kjörling <2695bd53d63c@ewoof.net> - 2023-10-25 11:10 +0200
                Re: Domain name to use on home networks Joe <joe@jretrading.com> - 2023-10-25 13:20 +0200
                Re: Domain name to use on home networks "Marco M." <mm@dorfdsl.de> - 2023-10-25 14:20 +0200
                Re: Domain name to use on home networks Pocket <pocket@columbus.rr.com> - 2023-10-25 16:50 +0200
                Re: Domain name to use on home networks gene heskett <gheskett@shentel.net> - 2023-10-25 13:30 +0200
                Re: Domain name to use on home networks "Marco M." <mm@dorfdsl.de> - 2023-10-25 14:20 +0200
                Re: Domain name to use on home networks Jeffrey Walton <noloader@gmail.com> - 2023-10-25 18:30 +0200
                Re: Domain name to use on home networks Stefan Monnier <monnier@iro.umontreal.ca> - 2023-10-26 03:30 +0200
                Re: Domain name to use on home networks John Hasler <john@sugarbit.com> - 2023-10-26 03:50 +0200
                Re: Domain name to use on home networks Stefan Monnier <monnier@iro.umontreal.ca> - 2023-10-26 04:50 +0200
                Re: Domain name to use on home networks David Wright <deblis@lionunicorn.co.uk> - 2023-10-27 05:20 +0200
                Re: Domain name to use on home networks Stefan Monnier <monnier@iro.umontreal.ca> - 2023-10-27 06:50 +0200
                Re: Domain name to use on home networks Michael Kjörling <2695bd53d63c@ewoof.net> - 2023-10-27 12:10 +0200
                Re: Domain name to use on home networks gene heskett <gheskett@shentel.net> - 2023-10-27 13:20 +0200
                Re: Domain name to use on home networks Pocket <pocket@columbus.rr.com> - 2023-10-27 13:30 +0200
                Re: Domain name to use on home networks Pocket <pocket@columbus.rr.com> - 2023-10-27 14:00 +0200
                Re: Domain name to use on home networks Greg Wooledge <greg@wooledge.org> - 2023-10-27 15:10 +0200
                Re: Domain name to use on home networks Pocket <pocket@columbus.rr.com> - 2023-10-27 15:40 +0200
                Re: Domain name to use on home networks "Andrew M.A. Cater" <amacater@einval.com> - 2023-10-27 16:10 +0200
                Re: Domain name to use on home networks Pocket <pocket@columbus.rr.com> - 2023-10-27 16:20 +0200
                Re: Domain name to use on home networks gene heskett <gheskett@shentel.net> - 2023-10-27 17:50 +0200
                Re: Domain name to use on home networks Greg Wooledge <greg@wooledge.org> - 2023-10-27 16:30 +0200
                Re: Domain name to use on home networks gene heskett <gheskett@shentel.net> - 2023-10-27 18:10 +0200
                Re: Domain name to use on home networks Max Nikulin <manikulin@gmail.com> - 2023-10-29 17:30 +0100
                Re: Domain name to use on home networks Jeffrey Walton <noloader@gmail.com> - 2023-10-29 19:30 +0100
                Re: Domain name to use on home networks Max Nikulin <manikulin@gmail.com> - 2023-10-30 03:30 +0100
                Re: Changing host name and domain name on Debian; was: Domain name  to use on home networks Michael Kjörling <2695bd53d63c@ewoof.net> - 2023-10-27 16:20 +0200
                Re: Changing host name and domain name on Debian; was: Domain nameto  use on home networks gene heskett <gheskett@shentel.net> - 2023-10-27 18:10 +0200
                Re: Changing host name and domain name on Debian; was: Domain nameto  use on home networks Max Nikulin <manikulin@gmail.com> - 2023-10-29 17:10 +0100
                Re: Changing host name and domain name on Debian; was: Domain  nametouse on home networks gene heskett <gheskett@shentel.net> - 2023-10-29 18:10 +0100
                Re: Changing host name and domain name on Debian; was: Domain  nametouse on home networks Max Nikulin <manikulin@gmail.com> - 2023-10-31 04:20 +0100
                Re: Changing host name and domain name on Debian; was: Domain nametouse  on home networks The Wanderer <wanderer@fastmail.fm> - 2023-10-31 10:20 +0100
                Re: Changing host name and domain name on Debian; was: Domain  nametouseon home networks gene heskett <gheskett@shentel.net> - 2023-10-31 15:30 +0100
                Re: Changing host name and domain name on Debian; was:  Domainnametouse on home networks gene heskett <gheskett@shentel.net> - 2023-10-31 15:30 +0100
                Re: Changing host name and domain name on Debian; was:  Domainnametouse on home networks John Hasler <john@sugarbit.com> - 2023-10-31 17:40 +0100
                Re: Changing host name and domain name on Debian; was:  Domainnametouse on home networks Felix Miata <mrmazda@earthlink.net> - 2023-11-01 22:10 +0100
                Re: Changing host name and domain name on Debian; was:Domainnametouse  on home networks gene heskett <gheskett@shentel.net> - 2023-11-02 00:30 +0100
                Re: Changing host name and domain name on Debian;  was:Domainnametouse on home networks Greg Wooledge <greg@wooledge.org> - 2023-11-02 00:40 +0100
                Re: Changing host name and domain name on Debian;was:Domainnametouse  on home networks gene heskett <gheskett@shentel.net> - 2023-11-02 01:20 +0100
                Re: Changing host name and domain name on Debian;was:Domainnametouse  on home networks Greg Wooledge <greg@wooledge.org> - 2023-11-02 01:40 +0100
                Re: Changing host name and domain name on Debian;was:Domainnametouse  on home networks Jeffrey Walton <noloader@gmail.com> - 2023-11-02 02:20 +0100
                Re: Changing host name and domain name on Debian;  was:Domainnametouse on home networks John Hasler <john@sugarbit.com> - 2023-11-02 00:40 +0100
                Re: report a Debian bug (was: Changing host name and dom...) Felix Miata <mrmazda@earthlink.net> - 2023-11-02 01:00 +0100
                Re: report a Debian bug gene heskett <gheskett@shentel.net> - 2023-11-02 02:40 +0100
                Re: report a Debian bug David Christensen <dpchrist@holgerdanske.com> - 2023-11-02 06:50 +0100
                Re: report a Debian bug gene heskett <gheskett@shentel.net> - 2023-11-02 09:10 +0100
                Re: report a Debian bug David Christensen <dpchrist@holgerdanske.com> - 2023-11-02 22:20 +0100
                Re: Domain name to use on home networks gene heskett <gheskett@shentel.net> - 2023-10-27 17:30 +0200
                Re: Domain name to use on home networks Greg Wooledge <greg@wooledge.org> - 2023-10-27 17:50 +0200
                Re: Domain name to use on home networks gene heskett <gheskett@shentel.net> - 2023-10-27 18:40 +0200
                Re: Domain name to use on home networks John Hasler <john@sugarbit.com> - 2023-10-27 18:50 +0200
                Re: Domain name to use on home networks Michael Kjörling <2695bd53d63c@ewoof.net> - 2023-10-27 19:10 +0200
                Re: Domain name to use on home networks Michael Kjörling <2695bd53d63c@ewoof.net> - 2023-10-27 19:20 +0200
                Re: Domain name to use on home networks Greg Wooledge <greg@wooledge.org> - 2023-10-27 14:00 +0200
                Re: Domain name to use on home networks gene heskett <gheskett@shentel.net> - 2023-10-27 17:20 +0200
                Re: Domain name to use on home networks Greg Wooledge <greg@wooledge.org> - 2023-10-27 17:50 +0200
                Re: Domain name to use on home networks gene heskett <gheskett@shentel.net> - 2023-10-27 18:30 +0200
                Re: Domain name to use on home networks gene heskett <gheskett@shentel.net> - 2023-10-27 18:50 +0200
                Re: Domain name to use on home networks Greg Wooledge <greg@wooledge.org> - 2023-10-27 19:30 +0200
                Re: Domain name to use on home networks David Wright <deblis@lionunicorn.co.uk> - 2023-10-29 15:30 +0100
                Re: Domain name to use on home networks Greg Wooledge <greg@wooledge.org> - 2023-10-29 16:30 +0100
                Re: Domain name to use on home networks John Hasler <john@sugarbit.com> - 2023-10-29 17:00 +0100
                Re: Domain name to use on home networks gene heskett <gheskett@shentel.net> - 2023-10-29 17:30 +0100
                Re: Domain name to use on home networks Pocket <pocket@columbus.rr.com> - 2023-10-29 18:10 +0100
                Re: Domain name to use on home networks gene heskett <gheskett@shentel.net> - 2023-10-29 19:20 +0100
                Re: Domain name to use on home networks John Hasler <john@sugarbit.com> - 2023-10-29 19:40 +0100
                Re: Domain name to use on home networks Max Nikulin <manikulin@gmail.com> - 2023-10-30 03:20 +0100
                Re: Domain name to use on home networks gene heskett <gheskett@shentel.net> - 2023-10-30 09:00 +0100
                Re: Domain name to use on home networks Timothy M Butterworth <timothy.m.butterworth@gmail.com> - 2023-10-30 10:20 +0100
                Re: Domain name to use on home networks gene heskett <gheskett@shentel.net> - 2023-10-30 17:10 +0100
                Re: Domain name to use on home networks John Hasler <john@sugarbit.com> - 2023-10-30 17:20 +0100
                Re: Domain name to use on home networks Pocket <pocket@columbus.rr.com> - 2023-10-30 17:50 +0100
                Re: Domain name to use on home networks gene heskett <gheskett@shentel.net> - 2023-10-30 18:30 +0100
                Re: Domain name to use on home networks Pocket <pocket@columbus.rr.com> - 2023-10-30 18:40 +0100
                Re: Domain name to use on home networks Pocket <pocket@columbus.rr.com> - 2023-10-30 17:50 +0100
                Re: Domain name to use on home networks gene heskett <gheskett@shentel.net> - 2023-10-30 18:10 +0100
                Re: Domain name to use on home networks Pocket <pocket@columbus.rr.com> - 2023-10-30 18:30 +0100
                Re: Domain name to use on home networks gene heskett <gheskett@shentel.net> - 2023-10-30 18:40 +0100
                Re: Domain name to use on home networks Pocket <pocket@columbus.rr.com> - 2023-10-30 18:30 +0100
                Re: Domain name to use on home networks gene heskett <gheskett@shentel.net> - 2023-10-30 18:40 +0100
                Re: Domain name to use on home networks gene heskett <gheskett@shentel.net> - 2023-10-30 17:50 +0100
                Re: Domain name to use on home networks John Hasler <john@sugarbit.com> - 2023-10-30 18:40 +0100
                Re: Domain name to use on home networks gene heskett <gheskett@shentel.net> - 2023-10-30 19:40 +0100
                Re: Domain name to use on home networks "Andrew M.A. Cater" <amacater@einval.com> - 2023-10-30 19:40 +0100
                Re: Domain name to use on home networks Greg Wooledge <greg@wooledge.org> - 2023-10-30 19:50 +0100
                Re: Domain name to use on home networks Pocket <pocket@columbus.rr.com> - 2023-10-30 22:10 +0100
                Re: Domain name to use on home networks gene heskett <gheskett@shentel.net> - 2023-10-30 22:40 +0100
                Re: Domain name to use on home networks Charles Curley <charlescurley@charlescurley.com> - 2023-10-31 02:40 +0100
                Re: Domain name to use on home networks gene heskett <gheskett@shentel.net> - 2023-10-31 15:10 +0100
                Re: Domain name to use on home networks Max Nikulin <manikulin@gmail.com> - 2023-10-31 04:10 +0100
                Re: Domain name to use on home networks gene heskett <gheskett@shentel.net> - 2023-10-30 19:50 +0100
                Re: Domain name to use on home networks Max Nikulin <manikulin@gmail.com> - 2023-10-31 04:00 +0100
                Re: Domain name to use on home networks Pocket <pocket@columbus.rr.com> - 2023-10-30 13:20 +0100
                Re: Domain name to use on home networks Pocket <pocket@columbus.rr.com> - 2023-10-30 13:30 +0100
                Re: Domain name to use on home networks Greg Wooledge <greg@wooledge.org> - 2023-10-30 13:30 +0100
                Re: Domain name to use on home networks Pocket <pocket@columbus.rr.com> - 2023-10-30 13:40 +0100
                Re: Domain name to use on home networks gene heskett <gheskett@shentel.net> - 2023-10-30 17:40 +0100
                Re: Domain name to use on home networks gene heskett <gheskett@shentel.net> - 2023-10-30 17:20 +0100
                Re: Domain name to use on home networks Max Nikulin <manikulin@gmail.com> - 2023-10-30 16:00 +0100
                Re: Domain name to use on home networks gene heskett <gheskett@shentel.net> - 2023-10-30 17:40 +0100
                Re: Domain name to use on home networks gene heskett <gheskett@shentel.net> - 2023-10-27 16:40 +0200
                Re: Domain name to use on home networks "Marco M." <mm@dorfdsl.de> - 2023-10-27 16:50 +0200
                Re: Domain name to use on home networks gene heskett <gheskett@shentel.net> - 2023-10-27 18:10 +0200
                Re: Domain name to use on home networks "Marco M." <mm@dorfdsl.de> - 2023-10-27 21:30 +0200
                Re: Domain name to use on home networks Greg Wooledge <greg@wooledge.org> - 2023-10-27 16:50 +0200
                Re: Domain name to use on home networks gene heskett <gheskett@shentel.net> - 2023-10-27 18:20 +0200
                Re: Domain name to use on home networks John Hasler <john@sugarbit.com> - 2023-10-27 18:30 +0200
                Re: Domain name to use on home networks Greg Wooledge <greg@wooledge.org> - 2023-10-27 19:20 +0200
                Re: Domain name to use on home networks John Hasler <john@sugarbit.com> - 2023-10-27 20:00 +0200
                Re: Domain name to use on home networks Greg Wooledge <greg@wooledge.org> - 2023-10-27 20:10 +0200
                Re: Domain name to use on home networks John Hasler <john@sugarbit.com> - 2023-10-27 21:00 +0200
                Re: Domain name to use on home networks The Wanderer <wanderer@fastmail.fm> - 2023-10-27 21:10 +0200
                Re: Domain name to use on home networks Jeffrey Walton <noloader@gmail.com> - 2023-10-28 00:50 +0200
                Re: Domain name to use on home networks Max Nikulin <manikulin@gmail.com> - 2023-10-28 07:40 +0200
                Re: Domain name to use on home networks David Wright <deblis@lionunicorn.co.uk> - 2023-10-27 16:40 +0200
                Re: Domain name to use on home networks Michael Kjörling <2695bd53d63c@ewoof.net> - 2023-10-26 10:20 +0200
                Re: Domain name to use on home networks "Marco M." <mm@dorfdsl.de> - 2023-10-26 10:40 +0200
                Re: Domain name to use on home networks Michael Kjörling <2695bd53d63c@ewoof.net> - 2023-10-26 11:20 +0200
                Re: Domain name to use on home networks Jeffrey Walton <noloader@gmail.com> - 2023-10-26 11:10 +0200
                Re: Domain name to use on home networks Michael Kjörling <2695bd53d63c@ewoof.net> - 2023-10-26 11:20 +0200
                Re: Domain name to use on home networks Michael Kjörling <2695bd53d63c@ewoof.net> - 2023-10-27 17:30 +0200
                Re: Domain name to use on home networks "Marco M." <mm@dorfdsl.de> - 2023-10-26 10:30 +0200
                Re: Domain name to use on home networks; was: Bookworm:NetworkManager Jeffrey Walton <noloader@gmail.com> - 2023-10-25 22:10 +0200
                Re: Domain name to use on home networks; was: Bookworm:NetworkManager David Wright <deblis@lionunicorn.co.uk> - 2023-10-26 01:30 +0200
                Re: Domain name to use on home networks; was: Bookworm:NetworkManager jeremy ardley <jeremy.ardley@gmail.com> - 2023-10-26 02:00 +0200
                Re: Domain name to use on home networks; was: Bookworm:NetworkManager Dan Purgert <dan@djph.net> - 2023-10-26 02:20 +0200
                Re: Domain name to use on home networks; was: Bookworm:NetworkManager David Wright <deblis@lionunicorn.co.uk> - 2023-10-27 05:30 +0200
                Re: Domain name to use on home networks; was: Bookworm:NetworkManager ghe2001 <ghe2001@protonmail.com> - 2023-10-23 18:00 +0200
                Re: Domain name to use on home networks; was: Bookworm:NetworkManager Max Nikulin <manikulin@gmail.com> - 2023-10-23 04:50 +0200
                Re: Domain name to use on home networks; was: Bookworm:NetworkManager gene heskett <gheskett@shentel.net> - 2023-10-23 18:20 +0200
                Re: Domain name to use on home networks; was: Bookworm:NetworkManager Greg Wooledge <greg@wooledge.org> - 2023-10-23 20:10 +0200
                Re: Domain name to use on home networks; was: Bookworm:NetworkManager "Andrew M.A. Cater" <amacater@einval.com> - 2023-10-23 20:30 +0200
                Re: Domain name to use on home networks; was: Bookworm:NetworkManager gene heskett <gheskett@shentel.net> - 2023-10-23 23:40 +0200
              Re: Bookworm: NetworkManager Dan Ritter <dsr@randomstring.org> - 2023-10-22 14:50 +0200
                Re: Bookworm: NetworkManager Pocket <pocket@columbus.rr.com> - 2023-10-22 14:50 +0200
                Re: example.org and other RFC 2606 domains; was: Bookworm:  NetworkManager Michael Kjörling <2695bd53d63c@ewoof.net> - 2023-10-22 15:20 +0200
                Re: Bookworm: NetworkManager Dan Ritter <dsr@randomstring.org> - 2023-10-22 17:00 +0200
              Re: Bookworm: NetworkManager Tixy <tixy@yxit.co.uk> - 2023-10-22 18:20 +0200
                Re: Bookworm: NetworkManager Pocket <pocket@columbus.rr.com> - 2023-10-22 19:50 +0200
      Re: Bookworm: NetworkManager Greg Wooledge <greg@wooledge.org> - 2023-10-21 20:40 +0200
        Re: Bookworm: NetworkManager Pocket <pocket@columbus.rr.com> - 2023-10-21 20:50 +0200
  Re: Bookworm: NetworkManager Pocket <pocket@columbus.rr.com> - 2023-10-21 22:30 +0200
    Re: Bookworm: NetworkManager "Andrew M.A. Cater" <amacater@einval.com> - 2023-10-21 22:40 +0200
    Re: Bookworm: NetworkManager Lee <ler762@gmail.com> - 2023-10-22 17:30 +0200
      Re: Bookworm: NetworkManager <tomas@tuxteam.de> - 2023-10-22 17:30 +0200
        Re: Bookworm: NetworkManager Lee <ler762@gmail.com> - 2023-10-22 17:50 +0200
          Re: Bookworm: NetworkManager Max Nikulin <manikulin@gmail.com> - 2023-10-25 19:00 +0200
        Re: Bookworm: NetworkManager Pocket <pocket@columbus.rr.com> - 2023-10-22 19:40 +0200
      Re: Bookworm: NetworkManager Greg Wooledge <greg@wooledge.org> - 2023-10-22 19:20 +0200
        Re: Bookworm: NetworkManager Pocket <pocket@columbus.rr.com> - 2023-10-22 19:50 +0200
        Re: Bookworm: NetworkManager Lee <ler762@gmail.com> - 2023-10-23 00:40 +0200
          Re: Bookworm: NetworkManager Pocket <pocket@columbus.rr.com> - 2023-10-23 01:20 +0200
            Re: Bookworm: NetworkManager Lee <ler762@gmail.com> - 2023-10-23 19:10 +0200
          Re: Bookworm: NetworkManager Andy Smith <andy@strugglers.net> - 2023-10-23 22:30 +0200
            Re: Bookworm: NetworkManager Lee <ler762@gmail.com> - 2023-10-27 21:40 +0200
  Re: Bookworm: NetworkManager Pocket <pocket@columbus.rr.com> - 2023-10-22 02:30 +0200

csiph-web