Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can I use https://www.tumblr.com/api/v2 as the API endpoint? (dns cache issue) #143

Open
bennworks opened this issue Jan 16, 2025 · 2 comments

Comments

@bennworks
Copy link

When using the Tumblr API, I experience the 'host not found' error quite frequently. It will return to normal after a while, but it occurs frequently when I first use it. The API endpoint is https://api.tumblr.com/v2, and I think this problem occurs because the DNS of the ISP I am connected to does not cache this address. I am connected to a very major ISP, and many users are experiencing similar problems. This problem has been occurring more frequently recently (in the past few months) and it is becoming quite a problem. When I looked at the Tumblr website, it uses https://www.tumblr.com/api/v2, and I was wondering if app developers can also use this address. If we use the www.tumblr.com address, we probably won't experience the 'host not found' error.

@cyle
Copy link
Member

cyle commented Jan 16, 2025

I experience the 'host not found' error quite frequently. It will return to normal after a while, but it occurs frequently when I first use it.

this is fairly concerning. can you provide more detail on this, such as the output of a dig command? there should be no issues looking up Tumblr's DNS records. api.tumblr.com and www.tumblr.com are both using the same infrastructure on our side, so one working consistently and the other not working consistently doesn't make sense.

even so, usage of https://www.tumblr.com/api/v2 is only allowed by our official web client. anyone else trying to use it will be blocked as potential abuse/spam, so please don't use it.

@bennworks
Copy link
Author

Strangely enough, since I used the dig command in the terminal, I haven't encountered the 'host not found' error for the past two weeks. I'm not sure why, but the issue has disappeared on all devices within the same space (could it be a router problem?). I don't know about other users. I'll have to monitor it further. The following is the output of the dig command:

% dig api.tumblr.com

; <<>> DiG 9.10.6 <<>> api.tumblr.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 54053
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;api.tumblr.com. IN A

;; ANSWER SECTION:
api.tumblr.com. 60 IN A 192.0.77.40

;; Query time: 43 msec
;; SERVER: 192.168.0.1#53(192.168.0.1)
;; WHEN: Fri Jan 31 11:18:48 KST 2025
;; MSG SIZE rcvd: 59

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants