[Pdns-users] CNAME lookup failure PDNS 2.9.22/PDNS Recursor 3.3.1

[Ruben d'Arco]

Hi,

On my debian stable (recursor 3.2) i have the same result. 
On the current SVN, this work as you expect it.
I suggest you try a newer version of the recursor.

Regards,
	Ruben


On Tue, Mar 20, 2012 at 01:10:25PM -0500, ktm at rice.edu wrote:
> Hi PDNS community,
> 
> I am investigating a CNAME resolution problem using
> PDNS Recursor 3.3.1. Here is the lookup that fails:
> 
> > nslookup blog.mythandsymbol.com
> Server:		127.0.0.1
> Address:	127.0.0.1#53
> 
> ** server can't find blog.mythandsymbol.com: NXDOMAIN
> 
> Is is actually a CNAME:
> 
> > nslookup -type=cname blog.mythandsymbol.com
> Server:		127.0.0.1
> Address:	127.0.0.1#53
> 
> Non-authoritative answer:
> blog.mythandsymbol.com	canonical name = domains.tumblr.com.
> 
> And that name looks up as well:
> 
> > nslookup domains.tumblr.com
> Server:		127.0.0.1
> Address:	127.0.0.1#53
> 
> Non-authoritative answer:
> Name:	domains.tumblr.com
> Address: 66.6.44.4
> 
> The problem is that the first lookup does not restart the
> DNS resolution process with the value that was returned from
> the original CNAME lookup. Is this a known bug and if so, is
> their a fix. Here is what Google DNS returns:
> 
> > nslookup blog.mythandsymbol.com 8.8.8.8
> Server:		8.8.8.8
> Address:	8.8.8.8#53
> 
> Non-authoritative answer:
> blog.mythandsymbol.com	canonical name = domains.tumblr.com.
> Name:	domains.tumblr.com
> Address: 66.6.44.4
> 
> Thank you for any suggestions.
> 
> Regards,
> Ken
> _______________________________________________
> Pdns-users mailing list
> Pdns-users at mailman.powerdns.com
> http://mailman.powerdns.com/mailman/listinfo/pdns-users