Am 13.05.22 um 15:16 schrieb Rainer Duffner:
Thanks for the hints!
It does indeed work with these settings.
The problem is also that google and quad9 and most of the rest of the internet
seem to be able to resolve it
the real problem is that they are working around it - if not the stupid
> The problem is also that google and quad9 and most of the rest of the
> internet seem to be able to resolve it.
Yes, that’s **the problem**. There’s no pressure to get Barclays to fix this.
If you are a customer, complain loudly. Advice your customers who are customers
to complain loudly.
Th
Hi,
Thanks for the hints!
It does indeed work with these settings.
The problem is also that google and quad9 and most of the rest of the internet
seem to be able to resolve it.
While I investigated this issue, I came around a posting from one or two years
ago where similar problems with Ba
Agreed, but without the upstream provider actually fixing the issue I
couldn't find a way to provide resolution of this domain to my customers -
are there better ways to resolve this from our side?
There seems to be a document about this issue -
https://kb.isc.org/docs/aa-01387
Paul
On Fri, 13 M
Working around servers that drop queries causes problems for zones that do have
protocol compliant servers. The workarounds cause problems with getting
DNSSEC responses wic leads to validation failures.
--
Mark Andrews
> On 13 May 2022, at 22:58, Paul Stead wrote:
>
>
> Further to this,
Further to this, I've discovered that disabling DNS cookies also seems to
help with resolution -
$ dig +nocookie +timeout=1 +retries=0 IN A myapplication.glbaa.barclays.com.
@ns21.barclays.com.
Maybe the send-cookie option could be investigated? YMMV..
On a side note other recursive DNS software
I have noticed this, too,
The problem seems to be related to edns - disabling edns for the upstream
servers looks to resolve the issue, this can be seen with later versions of
dig -
$ dig *+noedns* +timeout=1 +retries=0 IN A myapplication.glbaa.barclays.com.
@ns21.barclays.com.
I have config alo
Hi Rainer,
I believe this is unrelated to any upgrade. The nameservers for the domain are
broken:
$ dig IN A myapplication.international.barclays.com @ns2.barcap.com.
; <<>> DiG 9.19.0-1+0~20220421.76+debian10~1.gbpa71ef8-Debian <<>> IN A
myapplication.international.barclays.com @ns2.barcap.co
Hi,
at work, I have a problem resolving the following domain:
myapplication.international.barclays.com
BIND 9.16.27, FreeBSD 12.3-P5.
2022Q2 ports.
I copied the config to a VM at home - but it did not work there, either.
I believe it must have happened on the update from BIND 9.16.26 to 9.16
9 matches
Mail list logo
