public inbox for connman@lists.linux.dev
 help / color / mirror / Atom feed
From: Richard Sent <richard@freakingpenguin.com>
To: KeithG <ys3al35l@gmail.com>
Cc: connman@lists.linux.dev
Subject: Re: Global nameservers or alternative to / change in FallbackNameservers
Date: Sun, 16 Jun 2024 13:13:47 -0400	[thread overview]
Message-ID: <87bk40olo4.fsf@freakingpenguin.com> (raw)
In-Reply-To: <CAG17S_MDPgomPHz0WGvc656fHobod=jwqT_t_xNqbTMw2K-Wcg@mail.gmail.com> (KeithG's message of "Sun, 16 Jun 2024 10:59:00 -0500")

Hi Keith,

KeithG <ys3al35l@gmail.com> writes:

> Might this be where we recompile to use systemd-resolved? This is what
> I do so that I have control over DNS. It's in the docs. It would be
> nice, though if this were a runtime setting instead of a compile time
> flag.

Thanks for the suggestion! In my case I'm both on a non-systemd distro
(Guix System) and using --nodnsproxy so that's not an option, but it's
good to know it exists.

systemd-resolved support was added in 2018 (972e16af), while the comment
mentioning the mysterious seemingly-unimplemented global nameservers was
2010 (1cdd39b9). I think needing to change the entire DNS backend to use
a global nameserver instead of DHCP-discovered ones is a bit much to
ask, so a runtime setting would be lovely. :)

-- 
Take it easy,
Richard Sent
Making my computer weirder one commit at a time.

  parent reply	other threads:[~2024-06-16 17:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-16 15:47 Global nameservers or alternative to / change in FallbackNameservers Richard Sent
     [not found] ` <CAG17S_MDPgomPHz0WGvc656fHobod=jwqT_t_xNqbTMw2K-Wcg@mail.gmail.com>
2024-06-16 17:13   ` Richard Sent [this message]
2024-06-16 17:45 ` Grant Erickson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87bk40olo4.fsf@freakingpenguin.com \
    --to=richard@freakingpenguin.com \
    --cc=connman@lists.linux.dev \
    --cc=ys3al35l@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox