public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "carlos at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug network/27048] Problem resolving one specific name (DNS problem)
Date: Thu, 10 Dec 2020 17:58:18 +0000 [thread overview]
Message-ID: <bug-27048-131-Lt1ZeCuZoB@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27048-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=27048
Carlos O'Donell <carlos at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |NOTABUG
CC| |carlos at redhat dot com
Status|UNCONFIRMED |RESOLVED
--- Comment #1 from Carlos O'Donell <carlos at redhat dot com> ---
(In reply to eric.brunet from comment #0)
> Is there anything I can do to help?
This doesn't seem related to glibc at all.
If the resolution of the name works as expected (DNS stub resolver in glibc +
your configured recursive resolver) then the rest of the problem is on the
network or the server end. The network issue might be a local issue with
filtering or a remote issue with filtering.
You will have to debug this more and come back with a conclusive example
showing a defect in the C library, or other library.
I am able to login to login.live.com just fine from my systems using Fedora 32
on x86_64. So this looks like a local issue relevant to your network.
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2020-12-10 17:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-10 16:38 [Bug network/27048] New: " eric.brunet at ens dot fr
2020-12-10 17:58 ` carlos at redhat dot com [this message]
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=bug-27048-131-Lt1ZeCuZoB@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@sourceware.org \
/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).