From: Jelle Licht <jlicht@fsfe.org>
To: Pierre Neidhardt <mail@ambrevar.xyz>, help-guix@gnu.org
Subject: Re: Random domain name resolution errors
Date: Fri, 07 Feb 2020 14:36:54 +0100 [thread overview]
Message-ID: <87sgjmplhl.fsf@jlicht.xyz> (raw)
In-Reply-To: <87pneqfs4p.fsf@ambrevar.xyz>
Pierre Neidhardt <mail@ambrevar.xyz> writes:
> Hi!
>
> A strange thing just happened to me: ever since I went to Belgium last
> week (don't know if it's relevant) I keep getting domain name resolution
> errors.
>
> For instance right now duckduckgo.com fails but guix.gnu.org works.
>
> I'm back home now and the issue persists.
>
> Any clue how to investigate?
When I have *some* domain name resolution issues, it usually has
something to do with my nscd being a bit too eager caching negative
results. Assuming you are using Guix System, does `herd invalidate nscd
hosts' help?
- Jelle
next prev parent reply other threads:[~2020-02-07 13:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-07 13:23 Random domain name resolution errors Pierre Neidhardt
2020-02-07 13:36 ` Jelle Licht [this message]
2020-02-07 13:38 ` Pierre Neidhardt
2020-02-07 13:42 ` Julien Lepiller
2020-02-07 13:51 ` Pierre Neidhardt
2020-03-14 14:59 ` Pierre Neidhardt
2020-03-14 17:22 ` Leo Famulari
2020-03-14 18:26 ` Pierre Neidhardt
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sgjmplhl.fsf@jlicht.xyz \
--to=jlicht@fsfe.org \
--cc=help-guix@gnu.org \
--cc=mail@ambrevar.xyz \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).