Chris Thompson wrote:
>
> Don't hold your breath.
Indeed, I put those Barclays nameservers in our noedns list on 2017-07-14
(tho I have also not really tried to get them fixed, despite Barclays
being our bank)
Tony.
--
f.anthony.n.finchhttp://dotat.at/
Bailey: Northeast veering southeast
On Nov 7 2019, Wilfred Sarmiento via bind-users wrote:
Hope this issue will reach Barclays Domain admin.
Don't hold your breath. The problem with these Barclays servers was already
being discussed on bind-users back in June, see the thread starting at
bind-users@lists.isc.org> wrote:
> > >
> > > Hi Bind Users,
> > >
> > > Anyone have a similar issue we are encountering with the subdomain of
> Barclays.com specifically federate.secure.barclays.com
> > > Our cache server could not resolve the said subdomai
omains.
> > Debug just showed below little details of logs.
> > That subdomain was resolvable using Google DNS and other OpenDNS.
> >
> > client @0x7f6a14a7b6a0 xxx.xxx.xxx.xxx#63852
> > (federate.secure.barclays.com): query: federate.secure.barclays.com IN A +
> > (x.x.x.
Hi Steinar,
Noted and thank you very much.
Regards.
*Wil*
On Wed, Nov 6, 2019 at 4:21 PM wrote:
> > The workaround works, does BIND 9.14 has a patch to resolve this? Since
> we
> > have a multiple Cache server, we need to do this every time we encounter
> > another domain that has this same
> The workaround works, does BIND 9.14 has a patch to resolve this? Since we
> have a multiple Cache server, we need to do this every time we encounter
> another domain that has this same issue.
There's probably no patch to "resolve" this, because the correct way
to fix the problem is at the
ut was able to
> resolve their root domain barclays.com and any other known domains.
> > Debug just showed below little details of logs.
> > That subdomain was resolvable using Google DNS and other OpenDNS.
> >
> > client @0x7f6a14a7b6a0 xxx.xxx.xxx.xxx#63852 (
> federate.s
(federate.secure.barclays.com): query: federate.secure.barclays.com IN A
> > + (x.x.x.x)
> >
> > client @0x7f6a4a4cd070 xxx.xxx.xxx.xxx#63852
> > (federate.secure.barclays.com): query: federate.secure.barclays.com IN A
> > + (x.x.x.x)
> >
> > client @0x7f6a14a7b6a0 xxx.xxx.xx
(federate.secure.barclays.com):
> query: federate.secure.barclays.com IN A + (x.x.x.x)
> client @0x7f6a4a4cd070 xxx.xxx.xxx.xxx#63852 (federate.secure.barclays.com):
> query: federate.secure.barclays.com IN A + (x.x.x.x)
> client @0x7f6a14a7b6a0 xxx.xxx.xxx.xxx#63852 (federate.sec
> + (x.x.x.x)
>
> client @0x7f6a14a7b6a0 xxx.xxx.xxx.xxx#63852
> (federate.secure.barclays.com): query failed (timed out) for
> federate.secure.barclays.com/IN/A at query.c:6786
>
> client @0x7f6a31216e30 xxx.xxx.xxx.xxx#63852
> (federate.secure.barclays.com): query: federate.s
(federate.secure.barclays.com):
query: federate.secure.barclays.com IN A + (x.x.x.x)
client @0x7f6a14a7b6a0 xxx.xxx.xxx.xxx#63852 (federate.secure.barclays.com):
query failed (timed out) for federate.secure.barclays.com/IN/A at
query.c:6786
client @0x7f6a31216e30 xxx.xxx.xxx.xxx#63852 (federate.secure.barclays.com):
query
11 matches
Mail list logo