Cloudflare Public DNS Resolver 1.1.1.1 is blocking t-online.de

Hello,

It depends on the client IP address, but 1.1.1.1 does often not resolve t-online.de and its subdomains! I get REFUSED:

$ dig @1.1.1.1 t-online.de 

; <<>> DiG 9.18.12-0ubuntu0.22.04.1-Ubuntu <<>> @1.1.1.1 t-online.de
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: REFUSED, id: 6174
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;t-online.de.			IN	A

;; Query time: 15 msec
;; SERVER: 1.1.1.1#53(1.1.1.1) (UDP)
;; WHEN: Mon Apr 17 11:23:52 CEST 2023
;; MSG SIZE  rcvd: 40

My IP address in this case was 217.244.220.98

t-online.de is a huge media and email provider. The blocking on CF leads to major problems!

Could someone at CF pleas unblock t-online.de?

Winfried

Seems this Issue has been fixed. From my perspective It works again.

The title basically says it all. Since sometime yesterday, my TV stopped working and I also couldn’t send Mail from my Telekom account anymore. The problem seems to be that Cloudflare no longer resolves their domains, as both their own DNS and Google are working fine.

C:\Windows\System32>nslookup securesmtp.t-online.de 1.1.1.1
Server:  one.one.one.one
Address:  1.1.1.1

*** securesmtp.t-online.de wurde von one.one.one.one nicht gefunden: Query refused.

C:\Windows\System32>nslookup securesmtp.t-online.de
Server:  fritz.box
Address:  fd00::b2f2:8ff:fe93:b5de

Nicht autorisierende Antwort:
Name:    sfwdallmx.t-online.de
Addresses:  194.25.134.46
          194.25.134.110
Aliases:  securesmtp.t-online.de


C:\Windows\System32>nslookup securesmtp.t-online.de 8.8.8.8
Server:  dns.google
Address:  8.8.8.8

Nicht autorisierende Antwort:
Name:    sfwdallmx.t-online.de
Addresses:  194.25.134.110
          194.25.134.46
Aliases:  securesmtp.t-online.de

See also Cloudflare Public DNS Resolver 1.1.1.1 is blocking t-online.de

I actually just gave it another try and it seems to be working again now.

Indeed. Seems this Issue has been fixed. From my perspective It works again as well.

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