Hey,
currently there are intermittent DNS problems when resolving "image.tmdb.org":
dig A image.tmdb.org
; <<>> DiG 9.16.1-Ubuntu <<>> A image.tmdb.org
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 7016
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;image.tmdb.org. IN A
;; ANSWER SECTION:
image.tmdb.org. 26 IN CNAME tmdb-image-prod.b-cdn.net.
tmdb-image-prod.b-cdn.net. 4 IN A 127.0.0.1
;; Query time: 88 msec
;; SERVER: 127.0.0.53#53(127.0.0.53)
;; WHEN: Mon Aug 22 01:37:45 CEST 2022
;; MSG SIZE rcvd: 98
The problem seems to have just been fixed again at least with DNS (1.1.1.1).
找不到电影或节目?登录并创建它吧。
ticao2 🇧🇷 pt-BR 的回复
于 2022 年 08 月 25 日 10:37上午
There were issues in Northern European countries with Cloudflare DNS Service (1.1.1.1).
Some cases were resolved by switching to Google DNS Service (8.8.8.8).
In wich country are you ?
Always using DNS 1.1.1.1 ?
dennis_de 的回复
于 2022 年 08 月 25 日 12:00下午
Hey,
we are located in Germany. But yes, we use 1.1.1.1 globally.
ticao2 🇧🇷 pt-BR 的回复
于 2022 年 08 月 25 日 1:43下午
If I remember correctly, some users in Germany had problems.
That's because Cloudflare (1.1.1.1) was allocating some IPs in the wrong country.
To Russia or Belarus if I'm not mistaken.
So when they switched to Google (8.8.8.8) they fixed the problem.
Perhaps Clouflare resolved this confusion.
dennis_de 的回复
于 2022 年 08 月 29 日 6:45上午
Okay, thanks. In the meantime, the problem has not reoccurred. I will continue to monitor this and otherwise contact CloudFlare myself.