Cloudflare Zero Trust Gateway (Doh and DoT) failed to resolve uidai.gov.in

[saugata.datta]

Cloudflare Gateway (Doh and DoT) failed to resolve uidai.gov.in. This is Govtr. India website for Aadhaar.

Response details

tls://xxxxxxxx.cloudflare-gateway.com:853 *(served from cache)*
Elapsed : 0.46 ms
Response code : SERVFAIL

https://xxxxxxxx.cloudflare-gateway.com:443/dns-query *(served from cache)*
Elapsed : 0.40 ms
Response code : SERVFAIL

It also getting failed to CF Cloudflare Gateway DNS IP.

> uidai.gov.in
Server:  UnKnown
Address:  172.64.36.1

*** UnKnown can't find uidai.gov.in: Server failed

> uidai.gov.in
Server:  UnKnown
Address:  172.64.36.2

*** UnKnown can't find uidai.gov.in: Server failed

[saugata.datta]

Anyone have any information on this? Issue can be replicate easily by setting those two DNS server IP as your own and try resolving uidai.gov.in

[saugata.datta]

Is there anyone will help me with this?

[cscharff]

I’m unable to reproduce.

My recommendation would be to determine the specific colo from which you are resolving by following these steps:

Have problems with 1.1.1.1? *Read Me First*

Here are some tips for troubleshooting if you are having issues using Cloudflare’s Resolver. Please take a moment to review them along with the information that will help us to understand and help diagnose any issues. There are two sections to this guide. The first is for troubleshooting name resolution errors/issues and the second is for unreachability or routing issues. New Diagnostic Tool We have a new diagnostic tool which can help gather some of the information requested below. If you copy…

Specifically this step:

dig +short CHAOS TXT id.server @172.64.36.1

If there is an issue it would appear to be regional which may indicate the authoritative DNS server is refusing queries from Cloudflare.

[saugata.datta]

It looks like it is regional issue. I have tried di, but same error.

https://1.1.1.1/help#eyJpc0NmIjoiWWVzIiwiaXNEb3QiOiJZZXMiLCJpc0RvaCI6IlllcyIsInJlc29sdmVySXAtMS4xLjEuMSI6IlllcyIsInJlc29sdmVySXAtMS4wLjAuMSI6IlllcyIsInJlc29sdmVySXAtMjYwNjo0NzAwOjQ3MDA6OjExMTEiOiJObyIsInJlc29sdmVySXAtMjYwNjo0NzAwOjQ3MDA6OjEwMDEiOiJObyIsImRhdGFjZW50ZXJMb2NhdGlvbiI6IkJPTSIsImlzV2FycCI6Ik5vIiwiaXNwTmFtZSI6IkNsb3VkZmxhcmUiLCJpc3BBc24iOiIxMzMzNSJ9

[saugata.datta]

Is there anyone from support can help me with this?

[saugata.datta]

Do we really have any support staff in this community to pass this bug report to proper team for fixing it?

[mvavrusa]

Hi @saugata.datta, sorry I didn’t see this as it wasn’t tagged in the 1.1.1.1 category. We are already tracking this, the nameservers are not reachable from some of our pops (see the “no reachable authority” error). I tried to work around this by moving traffic around, but it seems like over time same thing happens, and I haven’t heard back from the zone authority owner. I’ll see if there’s anything else we can try in the meantime.

[saugata.datta]

Thank you for your reply, I was about to lose my hope to get it fixed. I opened this bug report, sent more than half a dozen of tweet, but don’t get any response.

I will be waiting for a fix.

Regards,
Saugata D.