problem resolving ardownload.adobe.com

Barry Margolin barmar at alum.mit.edu
Tue Jul 8 14:21:34 UTC 2014


In article <mailman.517.1404786934.26362.bind-users at lists.isc.org>,
 Mark Andrews <marka at isc.org> wrote:

> 
> The adobe servers are just plain broken.
> 
> 	Request a CNAME -> NXDOMAIN (Should return CNAME record)
> 	Request a TXT -> NXDOMAIN (Should return CNAME record)
> 	Request a NS -> NXDOMAIN (Should return CNAME record)
> 	Add a EDNS option -> NXDOMAIN (Should return CNAME record)
> 
> I suspect load balancer is passing non A/AAAA queries through to a
> backing server that doesn't have a fallback CNAME in the zone for
> ardownload.wip4.adobe.com resulting in NXDOMAIN being returned.
> That said, the load balancer should know that if it returning CNAME
> to A and AAAA queries, that it should also return CNAME to all other
> query types.  This is basic RFC 1034 behaviour.

This is pretty common misbehavior for dedicated load balancers.

-- 
Barry Margolin
Arlington, MA


More information about the bind-users mailing list