Re: FYI: adobe.com GSLB DNS servers choking on "nsid"

2015-01-13 Thread Mark Andrews
We tried. Its "we don't get enough complaints" so we won't actually ask our nameserver vendor how to fix this despite us telling them that they just need to add a CNAME record to the backend zone. The load balancer has a front end that answers A and queries. CNAME/TXT/SOA and "unsual" A and

Re: FYI: adobe.com GSLB DNS servers choking on "nsid"

2015-01-13 Thread Carl Byington
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, 2015-01-13 at 12:49 +, Phil Mayers wrote: > Just found another; dns{0,1}.getsurfed.com are returning crazy error > codes with "nsid" (and presumably other) edns options: > # dig +norec +nsid @213.162.97.177 www.london-nano.com > ;; Got a

Re: FYI: adobe.com GSLB DNS servers choking on "nsid"

2015-01-13 Thread Phil Mayers
On 13/01/15 12:39, Phil Mayers wrote: On 13/01/15 12:37, Anand Buddhdev wrote: On 13/01/15 13:27, Phil Mayers wrote: Just to save anyone else the trouble, I've just found that some of the GSLB names for *.adobe.com return NXDOMAIN with "nsid" options present: It's not just NSID. They're resp

Re: FYI: adobe.com GSLB DNS servers choking on "nsid"

2015-01-13 Thread Phil Mayers
On 13/01/15 12:37, Anand Buddhdev wrote: On 13/01/15 13:27, Phil Mayers wrote: Just to save anyone else the trouble, I've just found that some of the GSLB names for *.adobe.com return NXDOMAIN with "nsid" options present: It's not just NSID. They're responding with NXDOMAIN if you send any ED

Re: FYI: adobe.com GSLB DNS servers choking on "nsid"

2015-01-13 Thread Anand Buddhdev
On 13/01/15 13:27, Phil Mayers wrote: > Just to save anyone else the trouble, I've just found that some of the > GSLB names for *.adobe.com return NXDOMAIN with "nsid" options present: It's not just NSID. They're responding with NXDOMAIN if you send any EDNS option they don't understand, so it's

Re: FYI: adobe.com GSLB DNS servers choking on "nsid"

2015-01-13 Thread Phil Mayers
On 13/01/15 12:27, Phil Mayers wrote: Just to save anyone else the trouble, I've just found that some of the GSLB names for *.adobe.com return NXDOMAIN with "nsid" options present: ...and in fact "sit", which is the actual problem option we're hitting (our 9.10 package seems to have been unint

FYI: adobe.com GSLB DNS servers choking on "nsid"

2015-01-13 Thread Phil Mayers
Just to save anyone else the trouble, I've just found that some of the GSLB names for *.adobe.com return NXDOMAIN with "nsid" options present: # dig +norec +dnssec +nsid @193.104.215.247 ardownload.wip4.adobe.com ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 50062 ...versu