SERVFAIL for www.kyb.mpg.de

1.1.1.1 and 1.0.0.1 return SERVFAIL when trying to resolve the domain www.kyb.mpg.de. Google’s 8.8.8.8 is resolving it fine.

dig www.kyb.mpg.de @1.1.1.1

; <<>> DiG 9.16.20-RH <<>> www.kyb.mpg.de @1.1.1.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 38504
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
; EDE: 6 (DNSSEC Bogus)
;; QUESTION SECTION:
;www.kyb.mpg.de.			IN	A

;; Query time: 55 msec
;; SERVER: 1.1.1.1#53(1.1.1.1)
;; WHEN: Wed Sep 08 21:30:16 CEST 2021
;; MSG SIZE  rcvd: 49
dig www.kyb.mpg.de @1.0.0.1

; <<>> DiG 9.16.20-RH <<>> www.kyb.mpg.de @1.0.0.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 13514
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
; EDE: 6 (DNSSEC Bogus)
;; QUESTION SECTION:
;www.kyb.mpg.de.			IN	A

;; Query time: 52 msec
;; SERVER: 1.0.0.1#53(1.0.0.1)
;; WHEN: Wed Sep 08 21:35:39 CEST 2021
;; MSG SIZE  rcvd: 49
dig www.kyb.mpg.de @8.8.8.8

; <<>> DiG 9.16.20-RH <<>> www.kyb.mpg.de @8.8.8.8
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 46916
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;www.kyb.mpg.de.			IN	A

;; ANSWER SECTION:
www.kyb.mpg.de.		21600	IN	CNAME	npsw-www.mpg.de.
npsw-www.mpg.de.	3600	IN	A	134.76.31.205

;; Query time: 65 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Wed Sep 08 21:36:40 CEST 2021
;; MSG SIZE  rcvd: 82
dig +short CHAOS TXT id.server @1.1.1.1
"FRA"

dig +short CHAOS TXT id.server @1.0.0.1
"FRA"

This post was hidden due to the MoreHelp tag being used ‘inappropriately,’ and should only be used on a post not receiving a response for 72 hours. The post above is 4 days old (96 hours), so I don’t see the problem. Or should the OP be the only one that uses the tag?

It’s supposed to be 72 hours after your own post. That way you don’t jump onto someone else’s thread with a Me Too! and MoreHelp tag it.

If it’s a problem the Community clearly can’t help with, I suggest you open a ticket and post the ticket # here. Tickets generally get auto-closed and referred to the Community, but if it really isn’t something we can help you fix, we can escalate it back to Support with that ticket #.

I’m not a paying customer, I just want to use 1.1.1.1. Can I open an official ticket to get this bug fixed?

Give it a try with an email to: support AT cloudflare DOT com and post the ticket # here.

Created #2254230, but it got closed immediately, because

we can only work with the account holder directly. We have automatically detected that you may not be the account owner of the domain(s) mentioned in this ticket.

I’ll wait a few days to see if the bug report here gets picked up by Cloudflare. If not and I don’t find another way to report bugs, I’ll have to switch to another upstream DNS provider, I guess.

This is the same issue as 1.1.1.1 SERVFAIL resolving deptapps.coe.berkeley.edu - #8 by mvavrusa, added a workaround to fix this domain in the meantime, sorry!

2 Likes

Thank you for the fix/workaround.

This should be resolved now.

1 Like

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