SERVFAIL from 1.1.1.1

Hi,

I’m seeing multiple SERVFAILs when querying against 1.1.1.1 and 1.0.0.1, along with their IPv6 counterparts.

This appears to be intermittent, but repeatable. I’m coming from AS10143 and utilising the Perth, Western Australia Cloudflare POP

➜ ~ nslookup abc.net.au 1.1.1.1

Server: 1.1.1.1

Address: 1.1.1.1#53

Non-authoritative answer:

Name: abc.net.au

Address: 23.202.160.194

➜ ~ nslookup abc.net.au 1.1.1.1

Server: 1.1.1.1

Address: 1.1.1.1#53

** server can’t find abc.net.au: SERVFAIL

1 Like

Hello,

Are you still having difficulties with this zone resolving? With my testing I see that it is resolving correctly.

nslookup abc.net.au 1.1.1.1
Server: one.one.one.one
Address: 1.1.1.1

Non-authoritative answer:
Name: abc.net.au
Address: 23.62.176.97

Please let us know if this is still an issue. We are happy to help.

I can confirm it’s not an issue anymore, but the PER PoP was definitely returning SERVFAILS about 50% of the time for any domain when this was happening

It happened again at 8am AWST, Friday the 10th of November.

1 Like

Here is some evidence from my SmokePing monitoring:

1 Like

Looks like they rerouted 1.1.1.1 to SYD now, at least I am from AS4764

Happened again at 10:10AM AWST

Hi @haydio,

Is it still happening, could you help to get the location that serving your request? Something like dig @1.1.1.1 CHAOS TXT id.server should work.

;; ANSWER SECTION:
id.server. 0 CH TXT “PER”

Sorry for late reply

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