public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "vincent.viallet at gmail dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug libc/12154] New: Can not resolve chained CNAME with a wildcard among the chained CNAME Date: Fri, 22 Oct 2010 14:17:00 -0000 [thread overview] Message-ID: <bug-12154-131@http.sourceware.org/bugzilla/> (raw) http://sourceware.org/bugzilla/show_bug.cgi?id=12154 Summary: Can not resolve chained CNAME with a wildcard among the chained CNAME Product: glibc Version: unspecified Status: NEW Severity: normal Priority: P2 Component: libc AssignedTo: drepper.fsp@gmail.com ReportedBy: vincent.viallet@gmail.com Apparently linux resolver can not resolve chained CNAME where one of the CNAME is using a wildcard / *. Or more precisely when a CNAME links to a * (star) CNAME that then resolv as a wildcard domain that links to another CNAME... (more clear in the example below) This behavior affects all the latest linux version I tested (CentOS 5.5 / Ubuntu) Reproduce the error : run dig to resolve a chained cname record : > dig @8.8.8.8 messenger.live.com > ... > ;; ANSWER SECTION: > messenger.live.com. 2343 IN CNAME get.live.com. > get.live.com. 3538 IN CNAME *.live.com. > *.live.com. 3538 IN CNAME rds.live.com.nsatc.net. > rds.live.com.nsatc.net. 103 IN A 65.55.60.123 Can not resolve messenger.live.com : > ping messenger.live.com > ping: unknown host messenger.live.com Resolving get.live.com is not working either. But using the wildcard domain is working : > ping random-domain.live.com > PING rds.live.com.nsatc.net (65.55.60.123) 56(84) bytes of data. -- Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
next reply other threads:[~2010-10-22 14:17 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-10-22 14:17 vincent.viallet at gmail dot com [this message] 2010-10-22 14:51 ` [Bug libc/12154] " vincent.viallet at gmail dot com 2010-11-20 14:21 ` pasky at suse dot cz 2012-02-21 2:11 ` [Bug network/12154] " jsm28 at gcc dot gnu.org 2012-12-19 10:45 ` schwab@linux-m68k.org 2014-06-30 7:23 ` fweimer at redhat dot com 2022-07-04 16:17 ` [Bug network/12154] Cannot resolve hosts which have wildcard aliases fweimer at redhat dot com 2022-08-10 9:35 ` fweimer at redhat dot com 2022-08-30 8:04 ` cvs-commit at gcc dot gnu.org 2022-08-30 8:04 ` cvs-commit at gcc dot gnu.org 2022-08-30 8:15 ` fweimer at redhat dot com 2022-08-31 1:34 ` vincent.viallet at gmail dot com 2022-09-13 11:23 ` cvs-commit at gcc dot gnu.org 2022-09-13 11:23 ` cvs-commit at gcc dot gnu.org 2022-09-13 11:24 ` cvs-commit at gcc dot gnu.org 2022-09-20 11:07 ` cvs-commit at gcc dot gnu.org 2022-09-20 11:07 ` cvs-commit at gcc dot gnu.org 2022-09-21 18:01 ` cvs-commit at gcc dot gnu.org 2022-09-21 18:01 ` cvs-commit at gcc dot gnu.org 2024-02-26 21:31 ` fw at deneb dot enyo.de 2024-02-27 11:07 ` fw at deneb dot enyo.de
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-12154-131@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sources.redhat.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: linkBe 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).