DNS failing for api-0.core.keybaseapi.com
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
Has the DNS records changed for key base servers? The Mac client seems to be failing DNS resolution. on checking I see NXDomain for this api-0.core.keybaseapi.com domain
```
vijay@socrates:~$ dig @8.8.8.8 api-o.core.keybaseapi.com
; <<>> DiG 9.18.18-0ubuntu0.22.04.2-Ubuntu <<>> @8.8.8.8 api-o.core.keybaseapi.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 51582
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;api-o.core.keybaseapi.com. IN A
;; AUTHORITY SECTION:
keybaseapi.com. 900 IN SOA ns-1197.awsdns-21.org. awsdns-hostmaster.amazon.com. 1 7200 900 1209600 86400
;; Query time: 19 msec
;; SERVER: 8.8.8.8#53(8.8.8.8) (UDP)
;; WHEN: Mon Apr 15 13:32:19 EDT 2024
;; MSG SIZE rcvd: 136
```
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing the reported lookup with dig against 8.8.8.8, checking both api-0 and api-o as shown in the title and command. Compare the result with the Keybase client’s expected server endpoint and DNS configuration; done means establishing whether the record is missing, renamed, or only mistyped.
Written by the indexing model from the issue text.
Assessment
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100