| 1 |
This is what I have on my machine. I can see the ANSWER SECTION in reversed |
| 2 |
order |
| 3 |
|
| 4 |
localhost ~ # dig registry-1.docker.io |
| 5 |
|
| 6 |
; <<>> DiG 9.16.33 <<>> registry-1.docker.io |
| 7 |
;; global options: +cmd |
| 8 |
;; Got answer: |
| 9 |
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 10324 |
| 10 |
;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 4, ADDITIONAL: 1 |
| 11 |
|
| 12 |
;; OPT PSEUDOSECTION: |
| 13 |
; EDNS: version: 0, flags:; udp: 4096 |
| 14 |
;; QUESTION SECTION: |
| 15 |
;registry-1.docker.io. IN A |
| 16 |
|
| 17 |
;; ANSWER SECTION: |
| 18 |
registry-1.docker.io. 51 IN A 3.216.34.172 |
| 19 |
registry-1.docker.io. 51 IN A 44.205.64.79 |
| 20 |
registry-1.docker.io. 51 IN A 34.205.13.154 |
| 21 |
|
| 22 |
;; AUTHORITY SECTION: |
| 23 |
docker.io. 171984 IN NS ns-1168.awsdns-18.org. |
| 24 |
docker.io. 171984 IN NS ns-1827.awsdns-36.co.uk. |
| 25 |
docker.io. 171984 IN NS ns-421.awsdns-52.com. |
| 26 |
docker.io. 171984 IN NS ns-513.awsdns-00.net. |
| 27 |
|
| 28 |
;; Query time: 15 msec |
| 29 |
;; SERVER: 192.168.1.1#53(192.168.1.1) |
| 30 |
;; WHEN: Sun Dec 11 11:06:33 EST 2022 |
| 31 |
;; MSG SIZE rcvd: 237 |
| 32 |
|
| 33 |
|
| 34 |
|
| 35 |
On Sun, Dec 11, 2022 at 12:59 AM Andreas Fink <finkandreas@×××.de> wrote: |
| 36 |
|
| 37 |
> On Sat, 10 Dec 2022 15:51:17 -0500 |
| 38 |
> Mansour Al Akeel <mansour.alakeel@×××××.com> wrote: |
| 39 |
> |
| 40 |
> > Andreas, |
| 41 |
> > |
| 42 |
> > Thank you very much. In fact I didn't go that deep yet, and not sure if I |
| 43 |
> > should. I just found that the url is not accessible even from a browser. |
| 44 |
> > Googling a bit, tells me there is no clear URL for docker-registry and |
| 45 |
> > possibly this one is outdated. I will continue looking around to confirm |
| 46 |
> > what the current default repo should be. If you have any suggestions, |
| 47 |
> > please let me know. |
| 48 |
> > |
| 49 |
> > |
| 50 |
> > localhost in ~ |
| 51 |
> > ○ → curl -k -v https://registry-1.docker.io/v2/ |
| 52 |
> > * Trying 34.228.211.243:443... |
| 53 |
> > |
| 54 |
> > * connect to 34.228.211.243 port 443 failed: Connection timed out |
| 55 |
> > * Failed to connect to registry-1.docker.io port 443 after 129401 ms: |
| 56 |
> > Couldn't connect to server |
| 57 |
> > * Closing connection 0 |
| 58 |
> > curl: (28) Failed to connect to registry-1.docker.io port 443 after |
| 59 |
> 129401 |
| 60 |
> > ms: Couldn't connect to server |
| 61 |
> |
| 62 |
> |
| 63 |
> You have a a strange DNS resolution. The IP address 34.227.211.243 |
| 64 |
> seems wrong. Here is what I see when I look at the DNS records: |
| 65 |
> andreas@localhost ~$ dig registry-1.docker.io |
| 66 |
> |
| 67 |
> ; <<>> DiG 9.16.33 <<>> registry-1.docker.io |
| 68 |
> ;; global options: +cmd |
| 69 |
> ;; Got answer: |
| 70 |
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 11419 |
| 71 |
> ;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 1 |
| 72 |
> |
| 73 |
> ;; OPT PSEUDOSECTION: |
| 74 |
> ; EDNS: version: 0, flags:; udp: 4096 |
| 75 |
> ;; QUESTION SECTION: |
| 76 |
> ;registry-1.docker.io. IN A |
| 77 |
> |
| 78 |
> ;; ANSWER SECTION: |
| 79 |
> registry-1.docker.io. 13 IN A 34.205.13.154 |
| 80 |
> registry-1.docker.io. 13 IN A 44.205.64.79 |
| 81 |
> registry-1.docker.io. 13 IN A 3.216.34.172 |
| 82 |
> |
| 83 |
> ;; Query time: 10 msec |
| 84 |
> ;; SERVER: 79.143.183.251#53(79.143.183.251) |
| 85 |
> ;; WHEN: Sun Dec 11 06:56:50 CET 2022 |
| 86 |
> ;; MSG SIZE rcvd: 97 |
| 87 |
> |
| 88 |
> I am not sure |
| 89 |
> Not sure where you get the wrong IP from, but it is a DNS issue. |
| 90 |
> |
| 91 |
> |
Archives