[Dnsmasq-discuss] [Cerowrt-devel] Had to disable dnssec today
woody77 at gmail.com
Sat Apr 26 16:20:05 UTC 2014
With two of them (akamai and cloudflare), I _think_ it's a dnsmasq issue
with the DS records for proving insecure domains are insecure. But Simon
Kelley would know that better than I.
With BofA, I'm nearly certain it's them, or an issue with one of their
partners (since the domain that fails isn't BofA, but something else):
(with dnssec turned off):
;; QUESTION SECTION:
;sso-fi.bankofamerica.com. IN A
;; ANSWER SECTION:
sso-fi.bankofamerica.com. 3599 IN CNAME saml-bac.onefiserv.com.
saml-bac.onefiserv.com. 299 IN CNAME saml-bac.gslb.onefiserv.com.
saml-bac.gslb.onefiserv.com. 119 IN A 126.96.36.199
And it's the saml-bac.gslb.onefiserv.com host that's failing (see here for
On Sat, Apr 26, 2014 at 6:00 PM, <dpreed at reed.com> wrote:
> Is this just a dnsmasq issue or is the DNSSEC mechanism broken at these
> sites? If it is the latter, I can get attention from executives at some
> of these companies (Heartbleed has sensitized all kinds of companies to the
> need to strengthen security infrastructure).
> If the former, the change process is going to be more tricky, because
> dnsmasq is easily dismissed as too small a proportion of the market to
> care. (wish it were not so).
> On Saturday, April 26, 2014 7:38am, "Aaron Wood" <woody77 at gmail.com> said:
> Just too many sites aren't working correctly with dnsmasq and using
> Google's DNS servers.
> - Bank of America (sso-fi.bankofamerica.com)
> - Weather Underground (cdnjs.cloudflare.com)
> - Akamai (e3191.dscc.akamaiedge.net.0.1.cn.akamaiedge.net)
> And I'm not getting any traction with reporting the errors to those sites,
> so it's frustrating in getting it properly fixed.
> While Akamai and cloudflare appear to be issues with their entries in
> google dns, or with dnsmasq's validation of them being insecure domains,
> the BofA issue appears to be an outright bad key. And BofA isn't being
> helpful (just a continual "we use ssl" sort of quasi-automated response).
> So I'm disabling it for now, or rather, falling back to using my ISP's dns
> servers, which don't support DNSSEC at this time. I'll be periodically
> turning it back on, but too much is broken (mainly due to the cdns) to be
> able to rely on it at this time.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Dnsmasq-discuss