Problem postbank.de

Hello,

I’m referring to this post:

May I ask whether you have still implemented the workaround for postbank.de? The problem still seems to exist and we are facing it too.

Thanks,
Winfried

Hi Winfried, which problem exactly does still exist? Could you explain what the problem exactly is?

I have done some lookups:

PS C:\Windows\system32> nslookup postbank.de 1.1.1.1
Server:  one.one.one.one
Address:  1.1.1.1

Nicht autorisierende Antwort:
Name:    postbank.de
Address:  160.83.8.182

PS C:\Windows\system32> nslookup postbank.de 8.8.8.8
Server:  dns.google
Address:  8.8.8.8

Nicht autorisierende Antwort:
Name:    postbank.de
Address:  160.83.8.182

Both (1.1.1.1 & 8.8.8.8) resolve to the very same IP, which is correct and their webpage works for me aswell (with 1.1.1.1 as DNS)

which problem exactly

It still seems to be there on the authoritative DNS servers over at postbank.de. CF 1.1.1.1 implemented a workaround to fix it on their side:

In the meantime, we’ve disabled DNSSEC for the affected domain(s) until it’s resolved

There is no problem with 1.1.1.1 at the moment. My question was, is this workaround (“disabled DNSSEC for the affected domain(s)” ) still active within 1.1.1.1?

Winfried

I quickly tag someone who is an expert on things like 1.1.1.1

@mvavrusa

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.