Website proof fails - both DNS and file

keybase / keybase-issues

A single repo for managing publicly recognized issues with the keybase client, installer, and website.

902 stars 37 forks source link

Website proof fails - both DNS and file #4000

Closed freitasm closed 3 years ago

freitasm commented 3 years ago

I have a valid website proof for a domain I own - both web and Windows desktop app show the blue tick for DNS authentication.

The problem is with a second domain I own - added the DNS record and the web shows the blue tick but the Windows app shows "UNREACHABLE".

Both domains are with the same registrar and DNS provider - but why web would show it as ok but the Windows (and mobile) apps would show it is not?

Windows app: Capture1

Web: Capture2

Thanks!

phixion commented 3 years ago

maybe a temporary DNS issue, but shouldnt keybase verify the identities and not the clients?

freitasm commented 3 years ago

@phixion nope - this has been happening for a couple of years now and every now and then I remove the DNS, add again... Still shows "Unreachable" in the app/windows app but ok on web.

Same registrar and DNS provider as the other domain which is validated ok.

plttn commented 3 years ago

Looks like an issue with your DNS on your client, not anything with keybase. What does a dig -t txt geekzone.co.nz from your network look like?

freitasm commented 3 years ago

I've decided to remove all the TXT records for Google verification as those are no longer needed once verified.

The change reduced the size of the DNS response and the app now shows as verified.

This leads me to think there may be a fault where Keybase is limiting the TXT buffer and if it overflows it stops processing the response - may be depending on network (although I had this problem at work, home and mobile).

I will close now as it's solved for me - but the suggestion to check the code for a buffer overflow remains.