Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #262472 > unrolled thread
| Started by | Pocket <pocket@columbus.rr.com> |
|---|---|
| First post | 2023-10-21 18:40 +0200 |
| Last post | 2023-10-22 02:30 +0200 |
| Articles | 20 on this page of 246 — 32 participants |
Back to article view | Back to linux.debian.user
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
Page 6 of 13 — ← Prev page 1 … 4 5 [6] 7 8 … 13 Next page →
| From | David Wright <deblis@lionunicorn.co.uk> |
|---|---|
| Date | 2023-10-27 05:20 +0200 |
| Subject | Re: Domain name to use on home networks |
| Message-ID | <Htly9-18RF-1@gated-at.bofh.it> |
| In reply to | #262735 |
On Wed 25 Oct 2023 at 22:42:07 (-0400), Stefan Monnier wrote: > >> It's just such a shame that they chose a name which refers to "arpa" > >> in it, which is not only US-centric but even belongs to the US's war > >> department, which I find rather unpalatable. > >> I understand ARPA was closely related to the beginnings of the Internet, > >> but... couldn't they choose something a bit more neutral? It's hardly surprising that the TLD of the ARPA Internet's naming system was called arpa. It kinda chose itself. And hardly surprising that it was US-centric as the ARPA Internet was a US commission. At the time, there was no global Internet to be neutral about: the ARPA Internet was one of several networks in the US, let alone in the world. DNS was running by at least 1983 (see RFCs 882/3), and I'm looking at an email from December 1986 sent from (I've concealed the name) Foo%lpi.span@star.stanford.edu%stanford@uk.ac.rl.earn via Decnet, Arpanet and Bitnet, to Janet. I constructed a reverse address, and all went well for a few months, until I received an email: "During August messages were addressed to you from the Arpanet and came through the UCL Internet Gateway. Please take action to become a registered user of the Gateway as messages addressed to your address shown in the header may soon be blocked and thus will not get to you. No warning will be given." The guy at LPI had discovered he could send through a new gateway at UCL. Note that the backwards address "uk.ac.rl.earn" is not a DNS address but a Janet hierarchical name. Just as .arpa is a historical hangover from a long time ago, so is the .uk at the end of my address, which is a hangover from Janet's TLD "uk.", as seen above. > > It belongs to the Internet Architecture Board and is administered by > > IANA which is why they chose it. It stands for "Address and Routing > > Parameter Area” <https://www.iana.org/domains/arpa>. > > But that's a "backronym". > It originally referred to the US agency. > I totally understand the technical reasons why they decided to stick to > this naming, but it's still grating. I would have thought that techies understand its origins, and non-techies are fairly unlikely ever to encounter it. Cheers, David.
[toc] | [prev] | [next] | [standalone]
| From | Stefan Monnier <monnier@iro.umontreal.ca> |
|---|---|
| Date | 2023-10-27 06:50 +0200 |
| Subject | Re: Domain name to use on home networks |
| Message-ID | <HtmXf-19EG-1@gated-at.bofh.it> |
| In reply to | #262766 |
> I would have thought that techies understand its origins, and
> non-techies are fairly unlikely ever to encounter it.
That's the thing: if you use `home.arpa` for your home network, suddenly
it's exposed to non-techies, like your friends and family, contrary to
things like `in-addr.arpa`.
Stefan
[toc] | [prev] | [next] | [standalone]
| From | Michael Kjörling <2695bd53d63c@ewoof.net> |
|---|---|
| Date | 2023-10-27 12:10 +0200 |
| Subject | Re: Domain name to use on home networks |
| Message-ID | <HtrWV-1cIb-3@gated-at.bofh.it> |
| In reply to | #262770 |
On 27 Oct 2023 00:46 -0400, from monnier@iro.umontreal.ca (Stefan Monnier): >> I would have thought that techies understand its origins, and >> non-techies are fairly unlikely ever to encounter it. > > That's the thing: if you use `home.arpa` for your home network, suddenly > it's exposed to non-techies, like your friends and family, contrary to > things like `in-addr.arpa`. If the IETF Home Networking WG's choice of domain name bothers $you (for some value of $you), nothing prevents $you from registering a custom domain name for private internal use and using that instead. (Registering the domain name naturally ensures that there will be no naming conflicts at least for the duration of the domain registration period.) Technically, it is of course also entirely possible to just make something up. But making something up comes with clear risks of its own; both risks of technical and connectivity issues, as well as risks of confusion. It might be obvious to $you that $you's internal hosts are *.example.net, but that's _not_ going to be obvious to others. Using the reserved-for-purpose domain name for its intended purpose avoids that in situations where one doesn't see the value of actually paying for a globally unique domain name registration for the purpose. -- Michael Kjörling 🔗 https://michael.kjorling.se “Remember when, on the Internet, nobody cared that you were a dog?”
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2023-10-27 13:20 +0200 |
| Subject | Re: Domain name to use on home networks |
| Message-ID | <Htt2F-1djF-3@gated-at.bofh.it> |
| In reply to | #262770 |
On 10/27/23 00:47, Stefan Monnier wrote: >> I would have thought that techies understand its origins, and >> non-techies are fairly unlikely ever to encounter it. > > That's the thing: if you use `home.arpa` for your home network, suddenly > it's exposed to non-techies, like your friends and family, contrary to > things like `in-addr.arpa`. > > > Stefan > I tried to change just this machine to see how its done, and managed to get all the right answers, which did not affect my local network since I generally use the alias name for an ssh or sshfs login, but on a reboot its all gone. So how the heck do we do that so it survives a reboot? Thanks. Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis
[toc] | [prev] | [next] | [standalone]
| From | Pocket <pocket@columbus.rr.com> |
|---|---|
| Date | 2023-10-27 13:30 +0200 |
| Subject | Re: Domain name to use on home networks |
| Message-ID | <Httcm-1dmJ-3@gated-at.bofh.it> |
| In reply to | #262773 |
On 10/27/23 07:12, gene heskett wrote: > On 10/27/23 00:47, Stefan Monnier wrote: >>> I would have thought that techies understand its origins, and >>> non-techies are fairly unlikely ever to encounter it. >> >> That's the thing: if you use `home.arpa` for your home network, suddenly >> it's exposed to non-techies, like your friends and family, contrary to >> things like `in-addr.arpa`. >> >> >> Stefan >> > I tried to change just this machine to see how its done, and managed > to get all the right answers, which did not affect my local network > since I generally use the alias name for an ssh or sshfs login, but on > a reboot its all gone. So how the heck do we do that so it survives a > reboot? > > Thanks. > > > Cheers, Gene Heskett. /etc/hosts -- It's not easy to be me
[toc] | [prev] | [next] | [standalone]
| From | Pocket <pocket@columbus.rr.com> |
|---|---|
| Date | 2023-10-27 14:00 +0200 |
| Subject | Re: Domain name to use on home networks |
| Message-ID | <HttFn-1dw5-1@gated-at.bofh.it> |
| In reply to | #262774 |
On 10/27/23 07:50, Greg Wooledge wrote: > On Fri, Oct 27, 2023 at 07:29:20AM -0400, Pocket wrote: >> On 10/27/23 07:12, gene heskett wrote: >>> I tried to change just this machine to see how its done, and managed to >>> get all the right answers, which did not affect my local network since I >>> generally use the alias name for an ssh or sshfs login, but on a reboot >>> its all gone. So how the heck do we do that so it survives a reboot? > *What* is "all gone"? Show us commands and their output, and then explain > why the output is not what you expected. > >> /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. > > I use the short-form hostnames, so mine is simply: > > unicorn:~$ cat /etc/hostname > unicorn > > Couldn't be simpler, really. Are you referring to the domain name or FQDN? -- It's not easy to be me
[toc] | [prev] | [next] | [standalone]
| From | Greg Wooledge <greg@wooledge.org> |
|---|---|
| Date | 2023-10-27 15:10 +0200 |
| Subject | Re: Domain name to use on home networks |
| Message-ID | <HtuL7-1em9-13@gated-at.bofh.it> |
| In reply to | #262775 |
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. > > > > I use the short-form hostnames, so mine is simply: > > > > unicorn:~$ cat /etc/hostname > > unicorn > > > > Couldn't be simpler, really. > > Are you referring to the domain name or FQDN? Neither. I'm referring to the hostname, as printed by the hostname(1) command. There are two philosophies for how to set your hostname. You can either use the short form (no dots), or the long form (dots). I use the short form. My hostname is simply set to "unicorn", not to "unicorn.wooledge.org" or anything like that. That would be the long form. If you're a long form hostname person, then your hostname should be set to the FQDN of the system. For a setup like Gene's, where the domain name is unofficial and he simply hopes that nobody ever registers it, I strongly recommend using short form hostnames. In BOTH cases, the entry in /etc/hosts should contain both the FQDN (real or otherwise), and the short form alias. Thus: unicorn:~$ grep unicorn /etc/hosts 127.0.1.1 unicorn.wooledge.org unicorn This is independent of which way you set the hostname. The IP address could be 127.0.1.1, or it could be your LAN address, if you're using statically assigned IPs.
[toc] | [prev] | [next] | [standalone]
| From | Pocket <pocket@columbus.rr.com> |
|---|---|
| Date | 2023-10-27 15:40 +0200 |
| Subject | Re: Domain name to use on home networks |
| Message-ID | <Htvea-1evr-7@gated-at.bofh.it> |
| In reply to | #262777 |
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. >>> >>> I use the short-form hostnames, so mine is simply: >>> >>> unicorn:~$ cat /etc/hostname >>> unicorn >>> >>> Couldn't be simpler, really. >> >> Are you referring to the domain name or FQDN? > > Neither. I'm referring to the hostname, as printed by the hostname(1) > command. > > There are two philosophies for how to set your hostname. You can either > use the short form (no dots), or the long form (dots). > > I use the short form. My hostname is simply set to "unicorn", not to > "unicorn.wooledge.org" or anything like that. That would be the long form. > > If you're a long form hostname person, then your hostname should be set > to the FQDN of the system. > > For a setup like Gene's, where the domain name is unofficial and he > simply hopes that nobody ever registers it, I strongly recommend using > short form hostnames. > > In BOTH cases, the entry in /etc/hosts should contain both the FQDN (real > or otherwise), and the short form alias. Thus: > > unicorn:~$ grep unicorn /etc/hosts > 127.0.1.1 unicorn.wooledge.org unicorn > > This is independent of which way you set the hostname. The IP address > could be 127.0.1.1, or it could be your LAN address, if you're using > statically assigned IPs. > You have confused me. I started to use Debian about 4 months ago because I no longer want to build and update my custom built GNU/Linux systems, which I had been doing for 20 years. Upon moving to Debian I looked up how to set the host name and was instructed to set the host name as “host” with out any “domain” part and then set a FQDN in /etc/hosts. Upon further research I found out that is the proper what to set the host name since UNIX began. I had been setting the host name to FQDN and the docs I read stated that was incorrect. Can you point to the docs that have information about the “long host names” as I have not been able to find anything on that? Sorry about sending the reply directly to you but this iPad won’t let fix that!
[toc] | [prev] | [next] | [standalone]
| From | "Andrew M.A. Cater" <amacater@einval.com> |
|---|---|
| Date | 2023-10-27 16:10 +0200 |
| Subject | Re: Domain name to use on home networks |
| Message-ID | <HtvHb-1eUN-5@gated-at.bofh.it> |
| In reply to | #262778 |
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
[toc] | [prev] | [next] | [standalone]
| From | Pocket <pocket@columbus.rr.com> |
|---|---|
| Date | 2023-10-27 16:20 +0200 |
| Subject | Re: Domain name to use on home networks |
| Message-ID | <HtvQR-1eXS-3@gated-at.bofh.it> |
| In reply to | #262779 |
[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
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2023-10-27 17:50 +0200 |
| Subject | Re: Domain name to use on home networks |
| Message-ID | <HtxfX-1fG6-3@gated-at.bofh.it> |
| In reply to | #262782 |
On 10/27/23 10:11, Pocket wrote:
>
>
> 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.
This is I believe, the first time I've heard of this command, why the
big secrecy in all correspondence to to date in this thread.
W/o issueing any "modify it commands:
gene@coyote:/etc$ hostnamectl
Static hostname: coyote.home.arpa
Transient hostname: coyote
Icon name: computer-desktop
Chassis: desktop 🖥
Machine ID: 7e8cfc91c7f24faa835e71ef5583898c
Boot ID: 1c90524af6584a36b93398f51e7427fa
Operating System: Debian GNU/Linux 12 (bookworm)
Kernel: Linux 6.1.0-13-rt-amd64
Architecture: x86-64
Hardware Vendor: ASUSTeK COMPUTER INC.
Hardware Model: PRIME Z370-A II
Firmware Version: 0801
gene@coyote:/etc$ hostname
coyote.home.arpa
gene@coyote:/etc$ dnsdomainname
home.arpa
gene@coyote:/etc$
Which is all correct. But dnsdomainname WILL return (none) after the
next reboot. Why, what have I not dome correctly?
>> Andy
>>
> From the man page
>
>
> THE FQDN
>
> The FQDN (Fully Qualified Domain Name) of the system is the name that
> the *resolver <https://manpages.org/resolver/3>*(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
> <https://manpages.org/getaddrinfo/3>*(3) returns for the host name
> returned by*gethostname <https://manpages.org/gethostname/2>*(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.
>
Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
- Louis D. Brandeis
[toc] | [prev] | [next] | [standalone]
| From | Greg Wooledge <greg@wooledge.org> |
|---|---|
| Date | 2023-10-27 16:30 +0200 |
| Subject | Re: Domain name to use on home networks |
| Message-ID | <Htw0x-1f19-3@gated-at.bofh.it> |
| In reply to | #262779 |
On Fri, Oct 27, 2023 at 02:00:21PM +0000, Andrew M.A. Cater wrote:
> > > On Oct 27, 2023, at 9:05 AM, Greg Wooledge <greg@wooledge.org> wrote:
> > >>> If you're using short-form hostnames like this:
> > >>>
> > >>> unicorn:~$ hostname
> > >>> unicorn
> > >>>
> > >>> then yeah, [/etc/hosts is] 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.
"set-hostname" is not included in the list of COMMANDS in hostnamectl(1)
on Debian 12. The only occurrence of this string is in the OPTIONS
section:
--static, --transient, --pretty
If status is invoked (or no explicit command is given) and one of
these switches is specified, hostnamectl will print out just this
selected hostname.
If used with set-hostname, only the selected hostnames will be
updated. When more than one of these switches are specified, all
the specified hostnames will be updated.
which looks very much like "we removed this command from the COMMANDS
section but forgot to update the reference to it in OPTIONS".
What does "hostnamectl set-hostname" or "hostnamectl hostname NAME"
actually *do*? How does its action "survive a reboot"? Does it
modify the /etc/hostname file for you? Or does it use some other
systemd-specific information storage mechanism? If it's the latter,
then *where* is it, and how is a conflict between /etc/hostname and
the systemd-specific storage mechanism resolved?
More importantly, why on earth would this be recommended over editing
the /etc/hostname file, which is *much* simpler, and which appears to
be independent of the init system that's in use?
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2023-10-27 18:10 +0200 |
| Subject | Re: Domain name to use on home networks |
| Message-ID | <Htxzk-1g2b-3@gated-at.bofh.it> |
| In reply to | #262783 |
On 10/27/23 10:22, Greg Wooledge wrote: > On Fri, Oct 27, 2023 at 02:00:21PM +0000, Andrew M.A. Cater wrote: >>>> On Oct 27, 2023, at 9:05 AM, Greg Wooledge <greg@wooledge.org> wrote: >>>>>> If you're using short-form hostnames like this: >>>>>> >>>>>> unicorn:~$ hostname >>>>>> unicorn >>>>>> >>>>>> then yeah, [/etc/hosts is] 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. > > "set-hostname" is not included in the list of COMMANDS in hostnamectl(1) > on Debian 12. The only occurrence of this string is in the OPTIONS > section: > > --static, --transient, --pretty > If status is invoked (or no explicit command is given) and one of > these switches is specified, hostnamectl will print out just this > selected hostname. > > If used with set-hostname, only the selected hostnames will be > updated. When more than one of these switches are specified, all > the specified hostnames will be updated. > > which looks very much like "we removed this command from the COMMANDS > section but forgot to update the reference to it in OPTIONS". > > What does "hostnamectl set-hostname" or "hostnamectl hostname NAME" > actually *do*? How does its action "survive a reboot"? Does it > modify the /etc/hostname file for you? Or does it use some other > systemd-specific information storage mechanism? If it's the latter, > then *where* is it, and how is a conflict between /etc/hostname and > the systemd-specific storage mechanism resolved? > > More importantly, why on earth would this be recommended over editing > the /etc/hostname file, which is *much* simpler, and which appears to > be independent of the init system that's in use? > > . plus at least a 1000 Greg. That manpage is gibberish Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis
[toc] | [prev] | [next] | [standalone]
| From | Max Nikulin <manikulin@gmail.com> |
|---|---|
| Date | 2023-10-29 17:30 +0100 |
| Subject | Re: Domain name to use on home networks |
| Message-ID | <HugPL-1HOX-9@gated-at.bofh.it> |
| In reply to | #262783 |
On 27/10/2023 21:19, Greg Wooledge wrote: > More importantly, why on earth would this be recommended over editing > the /etc/hostname file, which is *much* simpler, and which appears to be > independent of the init system that's in use? hostnamectl tries to prevent split brain /etc/hostname vs. kernel structures in RAM. "hostnamectl hostname --transient NAME" does not work if /etc/hostname is present. Notice diverged static and transient names in Gene's message > Static hostname: coyote.home.arpa > Transient hostname: coyote "hostnamectl hostname NAME" besides changing /etc/hosts calls sethostname(2) (or what libc provided instead of it), so it is less chance that a user will get inconsistent settings by forgetting another command. I think, original intention was to provide D-Bus API for GUI and hostnamectl is just a CLI tool for that API.
[toc] | [prev] | [next] | [standalone]
| From | Jeffrey Walton <noloader@gmail.com> |
|---|---|
| Date | 2023-10-29 19:30 +0100 |
| Subject | Re: Domain name to use on home networks |
| Message-ID | <HuiHT-1IWE-3@gated-at.bofh.it> |
| In reply to | #262779 |
On Fri, Oct 27, 2023 at 3:14 PM Andrew M.A. Cater <amacater@einval.com> wrote: > > On Fri, Oct 27, 2023 at 09:30:09AM -0400, Pocket wrote: > > > > > 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. Also see <https://systemd-devel.freedesktop.narkive.com/W2bL081i/how-do-you-set-the-machine-s-domain-name-with-systemd>, where the systemd folks said to modify the hostname by hand because hostnamectl butchered the fully qualified hostname. I'm not sure if it still applies. I avoid hostnamectl. I don't care about mDNS. DNS is the source of truth on my networks. Jeff
[toc] | [prev] | [next] | [standalone]
| From | Max Nikulin <manikulin@gmail.com> |
|---|---|
| Date | 2023-10-30 03:30 +0100 |
| Subject | Re: Domain name to use on home networks |
| Message-ID | <Huqcp-1NxJ-1@gated-at.bofh.it> |
| In reply to | #262876 |
On 30/10/2023 01:21, Jeffrey Walton wrote: > Also see > <https://systemd-devel.freedesktop.narkive.com/W2bL081i/how-do-you-set-the-machine-s-domain-name-with-systemd>, > where the systemd folks said to modify the hostname by hand because > hostnamectl butchered the fully qualified hostname. Debian bookworm is not affected by this decade-old bug. I am however unsure concerning reasons behind the following suggestion in respect to /etc/hostname hostname(5) from systemd > It is recommended that this name contains only a single label, i.e. > without any dots.
[toc] | [prev] | [next] | [standalone]
| From | Michael Kjörling <2695bd53d63c@ewoof.net> |
|---|---|
| Date | 2023-10-27 16:20 +0200 |
| Subject | Re: Changing host name and domain name on Debian; was: Domain name to use on home networks |
| Message-ID | <HtvQR-1eXS-5@gated-at.bofh.it> |
| In reply to | #262778 |
On 27 Oct 2023 09:30 -0400, from pocket@columbus.rr.com (Pocket): >> If you're a long form hostname person, then your hostname should be set >> to the FQDN of the system. > > You have confused me. I started to use Debian about 4 months ago > because I no longer want to build and update my custom built > GNU/Linux systems, which I had been doing for 20 years. Upon moving > to Debian I looked up how to set the host name and was instructed to > set the host name as “host” with out any “domain” part and then set > a FQDN in /etc/hosts. Upon further research I found out that is the > proper what to set the host name since UNIX began. I believe what Gene refers to when saying "long form host name" is the fully qualified host name, which includes both the host name and the domain name within which the host name exists. An example of a fully qualified host name is debian.example.net, where the domain is example.net. Note that the domain isn't necessarily exactly the last two labels of the host name; for example, if you're using mDNS then the domain would be "local" (fully qualified host name perhaps "debian.local") or I might have used "debian.example" instead; and if you work for, say, a large broadcaster in the UK, the domain might be "bbc.co.uk" and the fully qualified host name might be "debian.bbc.co.uk". Running `sudo hostnamectl set-hostname hostname.example.net` will set the host name of the system persistently to the fully qualified host name you provide on the command line. Or you can edit /etc/hostname directly to contain the fully qualified (or single-label) host name you want to use. Then edit /etc/hosts such that it also reflects the changed hostname. -- Michael Kjörling 🔗 https://michael.kjorling.se “Remember when, on the Internet, nobody cared that you were a dog?”
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2023-10-27 18:10 +0200 |
| Subject | Re: Changing host name and domain name on Debian; was: Domain nameto use on home networks |
| Message-ID | <Htxzk-1g2b-11@gated-at.bofh.it> |
| In reply to | #262781 |
On 10/27/23 10:19, Michael Kjörling wrote:
> On 27 Oct 2023 09:30 -0400, from pocket@columbus.rr.com (Pocket):
>>> If you're a long form hostname person, then your hostname should be set
>>> to the FQDN of the system.
>>
>> You have confused me. I started to use Debian about 4 months ago
>> because I no longer want to build and update my custom built
>> GNU/Linux systems, which I had been doing for 20 years. Upon moving
>> to Debian I looked up how to set the host name and was instructed to
>> set the host name as “host” with out any “domain” part and then set
>> a FQDN in /etc/hosts. Upon further research I found out that is the
>> proper what to set the host name since UNIX began.
>
> I believe what Gene refers to when saying "long form host name" is the
> fully qualified host name, which includes both the host name and the
> domain name within which the host name exists. An example of a fully
> qualified host name is debian.example.net, where the domain is
> example.net. Note that the domain isn't necessarily exactly the last
> two labels of the host name; for example, if you're using mDNS then
> the domain would be "local" (fully qualified host name perhaps
> "debian.local") or I might have used "debian.example" instead; and if
> you work for, say, a large broadcaster in the UK, the domain might be
> "bbc.co.uk" and the fully qualified host name might be
> "debian.bbc.co.uk".
>
> Running `sudo hostnamectl set-hostname hostname.example.net` will set
> the host name of the system persistently to the fully qualified host
> name you provide on the command line. Or you can edit /etc/hostname
> directly to contain the fully qualified (or single-label) host name
> you want to use.
That set-hostname option is not addressed in the manpage I just read, only:
hostname [NAME]
If no argument is given, print the system hostname. If an
optional argument NAME is provided then the command changes the system
hostname to NAME. By default, this will alter the pretty, the static,
and the transient hostname alike; however, if one or more of
--static, --transient, --pretty are used, only the selected hostnames
are changed. If the pretty hostname is being set, and static or
transient are being set as well, the specified hostname will
be simplified in regards to the character set used before the latter are
updated. This is done by removing special characters and spaces.
This ensures that the pretty and the static hostname are
always closely related while still following the validity rules of the
specific name. This simplification of the hostname string is not done if
only the transient and/or static hostnames are set, and the
pretty hostname is left untouched.
The static and transient hostnames must each be either a
single DNS label (a string composed of 7-bit ASCII lower-case characters
and no spaces or dots, limited to the format allowed for DNS domain
name labels), or a sequence of such labels separated by
single dots that forms a valid DNS FQDN. The hostname must be at most 64
characters, which is a Linux limitation (DNS allows longer names).
I suggest you file a bug against this command to among other things,
clean up the language to refer to FQDN's or aliases which we are
familiar with, "static, transient or pretty" as so called choices. If
using new words for old, either define them so we do understand or
remove them in favor of names we are familiar with.
> Then edit /etc/hosts such that it also reflects the changed hostname.
>
Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
- Louis D. Brandeis
[toc] | [prev] | [next] | [standalone]
| From | Max Nikulin <manikulin@gmail.com> |
|---|---|
| Date | 2023-10-29 17:10 +0100 |
| Subject | Re: Changing host name and domain name on Debian; was: Domain nameto use on home networks |
| Message-ID | <Hugwp-1HIS-11@gated-at.bofh.it> |
| In reply to | #262797 |
On 27/10/2023 23:03, gene heskett wrote:
>
> I suggest you file a bug against this command to among other things,
> clean up the language to refer to FQDN's or aliases which we are
> familiar with, "static, transient or pretty" as so called choices. If
> using new words for old, either define them so we do understand or
> remove them in favor of names we are familiar with.
If you see a bug then why somebody else should report it?
It is not clear for me why hostnamectl(1) should discuss FQDN. The scope
of hostnamectl is host name as it is stored in kernel structures:
gethostname(2), sethostname(2), uts_namespaces(7); and persistence
across reboots (/etc/hostname). Another part is representation of the
host in GUI and in responses to multicast service discovery ("pretty").
FQDN as described in hostname(1) is related to name resolver (hosts
entry in /etc/nsswitch.conf). So hostname(1) deals with more features
than hostnamectl. nss-myhostname(8) affects "hostname --all-fqdns", but
I am unsure if it does it in the way expected by hostname(1).
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2023-10-29 18:10 +0100 |
| Subject | Re: Changing host name and domain name on Debian; was: Domain nametouse on home networks |
| Message-ID | <Huhst-1Ih9-3@gated-at.bofh.it> |
| In reply to | #262869 |
On 10/29/23 12:10, Max Nikulin wrote:
> On 27/10/2023 23:03, gene heskett wrote:
>>
>> I suggest you file a bug against this command to among other things,
>> clean up the language to refer to FQDN's or aliases which we are
>> familiar with, "static, transient or pretty" as so called choices. If
>> using new words for old, either define them so we do understand or
>> remove them in favor of names we are familiar with.
>
> If you see a bug then why somebody else should report it?
begin rant:
Somebody who /can/ report it. I changed ISP's over a decade back, so I
am not me to bugzilla, and because I am known also by name, I can't
re-register. I can't even get a pw reset cuz it (I'm guessing here) is
sending it to my earlier ISP's, could be iolinc.net or frontier.com I
was using when I first installed redhat5.0 in 1998. Messages to the
maintainer to wipe me out of the system so I can re-register have never
been replied to.
People DO CHANGE ISP's for good reasons, like no telephone for several
months because frontier refuses to lay new buried copper that is now 70
years old, paper insulated and full of water. I repeatedly filed with
the states P.U.C. and all that got me was a letter cussing me out for
filing with the WV PUC. Screw it.
I'd heard rumors the local cable people could do phone service so I
switched it all. We had a 112 mph direcho come thru in 2010, all the
system battery's eventually went down. Did $18,000 damage to this house
and the 35 foot pin oak in the front yard was the only tree that
survived in a path about 100 foot wide and 10 miles long. Those 2 days
while putting the neighborhood utilities back together 13 years ago has
been my only phone or net failure since.
So don't give me any more static about filing my own bugs, I can't and
you've just been told why. If you want /ME/ to file bugs, fix it so I
can AND TELL ME when its been fixed.
/end rant
>
> It is not clear for me why hostnamectl(1) should discuss FQDN. The scope
> of hostnamectl is host name as it is stored in kernel structures:
> gethostname(2), sethostname(2), uts_namespaces(7); and persistence
> across reboots (/etc/hostname). Another part is representation of the
> host in GUI and in responses to multicast service discovery ("pretty").
> FQDN as described in hostname(1) is related to name resolver (hosts
> entry in /etc/nsswitch.conf). So hostname(1) deals with more features
> than hostnamectl. nss-myhostname(8) affects "hostname --all-fqdns", but
> I am unsure if it does it in the way expected by hostname(1).
>
> .
Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
- Louis D. Brandeis
[toc] | [prev] | [next] | [standalone]
Page 6 of 13 — ← Prev page 1 … 4 5 [6] 7 8 … 13 Next page →
Back to top | Article view | linux.debian.user
csiph-web