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

Groups > linux.debian.user > #232044

Re: Got a machine name problem

Show all headers | View raw

Gene Heskett (gheskett@shentel.net) wrote:
> > What *exactly* are you trying to do?

(crickets chirping)

> > How does that work?
> 
> By looking its alias up in /etc/hosts.

I was using rhetorical devices.  If you're truly using a pre-DNS
local network, then a lot of what I said simply does not apply to you.

> > In the file /etc/resolv.conf there are several different kinds of
> > lines that may be present.  One of them is the "search" line.
> 2 lines in that real file.
> 
> search coyote.den
> dnsserver ipv4 address

Your first line is valid.  Your second line is not.  There is no
keyword "dnsserver" in resolv.conf(5).  DNS resolvers are listed here
using the keyword "nameserver".

> It hasn't existed since Pottering came on the scene...

DHCP client daemons overwriting resolv.conf predate systemd by a lot.
This is not a thing that systemd can be blamed for.

> avahi and nm may be solutions a lappy user might need. Damned little is 
> portable here without a multi-ton gantry crane. They are both just 
> problems waiting to bite me, and to be emasculated by whatever means it 
> takes.

If you don't need them, delete them.

> My network was built by me, nothing portable about it, and I don't 
> understand why a dirt simple, static, /etc/hosts based local network, is 
> so damned hard to actually make work.

It's not!

Is that what you want?  A local network defined entirely by hosts files?
You can do that.  It's easy.  Just edit your /etc/hosts files to contain
the names and addresses of your machines.

In this scenario, your resolv.conf file will be used only to look up
hosts that live outside of your local network ("in the cloud").  You
won't CARE what the default DNS domain name is, because you aren't using
it.  Your local host lookups will be done by matching the strings that
you put in your hosts files.

Since you don't care what your resolv.conf file contains, you don't need
to jump through all the hoops involved in trying to prevent daemons from
overwriting it.  Let them.  Ignore them.  Your hostnames are defined in
your hosts files, and nothing will touch those.

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

Thread

Got a machine name problem Gene Heskett <gheskett@shentel.net> - 2021-02-23 19:00 +0100
  Re: Got a machine name problem Dan Ritter <dsr@randomstring.org> - 2021-02-23 19:10 +0100
  Re: Got a machine name problem Tom Browder <tom.browder@gmail.com> - 2021-02-23 20:30 +0100
    Re: Got a machine name problem "James B" <portoteacher80@fastmail.com> - 2021-02-24 01:30 +0100
      Re: Got a machine name problem "James B" <portoteacher80@fastmail.com> - 2021-02-24 01:30 +0100
      Re: Got a machine name problem Gene Heskett <gheskett@shentel.net> - 2021-02-24 02:30 +0100
        Re: Got a machine name problem <tomas@tuxteam.de> - 2021-02-24 09:40 +0100
          Re: Got a machine name problem <tomas@tuxteam.de> - 2021-02-24 12:20 +0100
            Re: Got a machine name problem Stefan Monnier <monnier@iro.umontreal.ca> - 2021-02-24 16:20 +0100
          Re: Got a machine name problem Gene Heskett <gheskett@shentel.net> - 2021-02-24 12:20 +0100
            Re: Got a machine name problem Greg Wooledge <greg@wooledge.org> - 2021-02-24 14:50 +0100
              Re: Got a machine name problem Tom Browder <tom.browder@gmail.com> - 2021-02-24 15:00 +0100
                Re: Got a machine name problem Greg Wooledge <greg@wooledge.org> - 2021-02-24 15:20 +0100
                Re: Got a machine name problem Tom Browder <tom.browder@gmail.com> - 2021-02-24 15:30 +0100
              Re: Got a machine name problem Gene Heskett <gheskett@shentel.net> - 2021-02-24 18:30 +0100
                Re: Got a machine name problem Greg Wooledge <greg@wooledge.org> - 2021-02-24 19:00 +0100
                Re: Got a machine name problem IL Ka <kazakevichilya@gmail.com> - 2021-02-24 19:20 +0100
                Re: Got a machine name problem Celejar <celejar@gmail.com> - 2021-02-24 19:00 +0100
    Re: Got a machine name problem Gene Heskett <gheskett@shentel.net> - 2021-02-24 02:10 +0100
      Re: Got a machine name problem David Wright <deblis@lionunicorn.co.uk> - 2021-02-24 02:40 +0100
        Re: Got a machine name problem Tom Browder <tom.browder@gmail.com> - 2021-02-24 03:30 +0100
        Re: Got a machine name problem Gene Heskett <gheskett@shentel.net> - 2021-02-24 04:30 +0100
      Re: Got a machine name problem Stefan Monnier <monnier@iro.umontreal.ca> - 2021-02-24 06:00 +0100
        Re: Got a machine name problem Gene Heskett <gheskett@shentel.net> - 2021-02-24 06:10 +0100
          OT: Spicy stuff in sensitive areas (was Re: Got a machine name problem) The Wanderer <wanderer@fastmail.fm> - 2021-02-24 12:20 +0100
      Re: Got a machine name problem Brian <ad44@cityscape.co.uk> - 2021-02-24 15:20 +0100
        Re: Got a machine name problem Brian <ad44@cityscape.co.uk> - 2021-02-24 21:20 +0100
  Re: Got a machine name problem David Christensen <dpchrist@holgerdanske.com> - 2021-02-24 03:00 +0100
    Re: Got a machine name problem David Wright <deblis@lionunicorn.co.uk> - 2021-02-24 06:00 +0100
  Re: Got a machine name problem "Andrew M.A. Cater" <amacater@einval.com> - 2021-02-24 12:20 +0100
    Re: Got a machine name problem Gene Heskett <gheskett@shentel.net> - 2021-02-24 12:30 +0100

csiph-web