This is what I have on my machine. I can see the ANSWER SECTION in reversed order
localhost ~ # dig registry-1.docker.io ; <<>> DiG 9.16.33 <<>> registry-1.docker.io ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 10324 ;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 4, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;registry-1.docker.io. IN A ;; ANSWER SECTION: registry-1.docker.io. 51 IN A 3.216.34.172 registry-1.docker.io. 51 IN A 44.205.64.79 registry-1.docker.io. 51 IN A 34.205.13.154 ;; AUTHORITY SECTION: docker.io. 171984 IN NS ns-1168.awsdns-18.org. docker.io. 171984 IN NS ns-1827.awsdns-36.co.uk. docker.io. 171984 IN NS ns-421.awsdns-52.com. docker.io. 171984 IN NS ns-513.awsdns-00.net. ;; Query time: 15 msec ;; SERVER: 192.168.1.1#53(192.168.1.1) ;; WHEN: Sun Dec 11 11:06:33 EST 2022 ;; MSG SIZE rcvd: 237 On Sun, Dec 11, 2022 at 12:59 AM Andreas Fink <finkandr...@web.de> wrote: > On Sat, 10 Dec 2022 15:51:17 -0500 > Mansour Al Akeel <mansour.alak...@gmail.com> wrote: > > > Andreas, > > > > Thank you very much. In fact I didn't go that deep yet, and not sure if I > > should. I just found that the url is not accessible even from a browser. > > Googling a bit, tells me there is no clear URL for docker-registry and > > possibly this one is outdated. I will continue looking around to confirm > > what the current default repo should be. If you have any suggestions, > > please let me know. > > > > > > localhost in ~ > > ○ → curl -k -v https://registry-1.docker.io/v2/ > > * Trying 34.228.211.243:443... > > > > * connect to 34.228.211.243 port 443 failed: Connection timed out > > * Failed to connect to registry-1.docker.io port 443 after 129401 ms: > > Couldn't connect to server > > * Closing connection 0 > > curl: (28) Failed to connect to registry-1.docker.io port 443 after > 129401 > > ms: Couldn't connect to server > > > You have a a strange DNS resolution. The IP address 34.227.211.243 > seems wrong. Here is what I see when I look at the DNS records: > andreas@localhost ~$ dig registry-1.docker.io > > ; <<>> DiG 9.16.33 <<>> registry-1.docker.io > ;; global options: +cmd > ;; Got answer: > ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 11419 > ;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 1 > > ;; OPT PSEUDOSECTION: > ; EDNS: version: 0, flags:; udp: 4096 > ;; QUESTION SECTION: > ;registry-1.docker.io. IN A > > ;; ANSWER SECTION: > registry-1.docker.io. 13 IN A 34.205.13.154 > registry-1.docker.io. 13 IN A 44.205.64.79 > registry-1.docker.io. 13 IN A 3.216.34.172 > > ;; Query time: 10 msec > ;; SERVER: 79.143.183.251#53(79.143.183.251) > ;; WHEN: Sun Dec 11 06:56:50 CET 2022 > ;; MSG SIZE rcvd: 97 > > I am not sure > Not sure where you get the wrong IP from, but it is a DNS issue. > >
