keybase / keybase-issues

A single repo for managing publicly recognized issues with the keybase client, installer, and website.
900 stars 37 forks source link

Cannot prove identity of telcodata.us #835

Open PaulTimmins opened 10 years ago

PaulTimmins commented 10 years ago

pichu:gnupg paul$ keybase prove web https://www.telcodata.us error: Failed to find a connection to www.telcodata.us (error #229) pichu:gnupg paul$ keybase prove web http://www.telcodata.us error: Failed to find a connection to www.telcodata.us (error #229) pichu:gnupg paul$ curl -I http://www.telcodata.us HTTP/1.1 302 Found Date: Tue, 01 Jul 2014 06:50:59 GMT Server: Apache/2.2.16 (Debian) Location: https://www.telcodata.us/ Content-Type: httpd/unix-directory

pichu:gnupg paul$ curl -I https://www.telcodata.us HTTP/1.1 200 OK Date: Tue, 01 Jul 2014 06:51:18 GMT Server: Apache/2.2.16 (Debian) Content-Type: text/html

pichu:gnupg paul$

zQueal commented 10 years ago
C:\Users\xanza\Desktop>dig www.telcodata.us ALL

; <<>> DiG 9.10rc1 <<>> www.telcodata.us ALL
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 61790
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;www.telcodata.us.              IN      A

;; ANSWER SECTION:
www.telcodata.us.       15768   IN      A       208.83.69.36

;; Query time: 34 msec
;; SERVER: 208.67.222.222#53(208.67.222.222)
;; WHEN: Tue Jul 01 11:17:43 Eastern Daylight Time 2014
;; MSG SIZE  rcvd: 61

;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 62408
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;ALL.                           IN      A

;; AUTHORITY SECTION:
.                       3588    IN      SOA     a.root-servers.net. nstld.verisign-grs.com. 2014070100 1800 900 604800 86400

;; Query time: 20 msec
;; SERVER: 208.67.222.222#53(208.67.222.222)
;; WHEN: Tue Jul 01 11:17:43 Eastern Daylight Time 2014
;; MSG SIZE  rcvd: 107

The common TTL for your DNS seems to be set at somewhere between 5 hours and 10.7 hours. Meaning you must wait a minimum of 5 or 10.7 hours to see changes to your DNS. If you haven't already waited, then do so. Once you've waited, then simply try again. Do not try to reauthenticate, or your TXT key will be changed and you'll have to start from square one.

PaulTimmins commented 10 years ago

I'm not trying to use DNS TXT (in part because of the TTLs). I am trying to get it to generate the attestation file I can upload to my webserver, and it refuses to generate that file because of the errors shown above, which don't seem to correlate to anything in my control.