This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug libc/12154] New: Can not resolve chained CNAME with a wildcard among the chained CNAME
- From: "vincent.viallet at gmail dot com" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sources dot redhat dot com
- Date: Fri, 22 Oct 2010 14:17:18 +0000
- Subject: [Bug libc/12154] New: Can not resolve chained CNAME with a wildcard among the chained CNAME
- Auto-submitted: auto-generated
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.