For me it also works and I never had any issues with DNS resolution of my mirrors.

I suppose that server(s):

49.12.124.107 2a01:4f8:242:5614::2

Have DNS issues. I also noticed same errors for other mirrors. All those errors were from this/those particular server(s).

пн, 20 февр. 2023 г. в 12:49, Polarian polarian@polarian.dev:

Hello,

I can connect just fine to the mirror on both HTTP and HTTPS, I have not checked rsync, but I assume it would be the same.

I would advice checking the following:

• Change your DNS server, it does not seem like it is resolving the IP

address (try 1.1.1.1 or 1.0.0.1 for cloudflares DNS, or 8.8.8.8 or 8.4.4.8 for googles DNS).

• Try to connect to another service, to check your network connectivity

is working

• Ensure that no firewall is blocking the connection.

Hope this helps,

Polarian GPG signature: 0770E5312238C760 Website: https://polarian.dev JID/XMPP: polarian@polarian.dev

I have no access to checking servers at all. So ArchTeam might want to check it.

пн, 20 февр. 2023 г. в 13:04, Polarian polarian@polarian.dev:

cat /etc/resolv.conf

^^^ would help a lot on the affected servers :)

-- Polarian GPG signature: 0770E5312238C760 Website: https://polarian.dev JID/XMPP: polarian@polarian.dev

Hello,

Maybe it is an issue with German based nameservers?

You need to check if this is just a Germany issue, I have checked from my server here in the UK, and it is working fine (I use recursive DNS resolvers so its not a real representation of the public DNS severs).

Good luck,

Hello,

Dig does use systemd-resolve because that is what LXC containers default to, and I have used dig a lot within LXC containers which querying my server network.

It is most likely a Arch DNS issue... nothing wrong with the dig tool...

Have a good day,

Well, kyberog != kyberorg.

пн, 20 февр. 2023 г. в 13:26, Jelle van der Waa jelle@vdwaa.nl:

Hi

On 20/02/2023 11:27, Aleksandr Muravja wrote:

...

Hello,

I notificed, that my mirror's error log contains name resolution errors. Mirror: https://archlinux.org/mirrors/kyberorg.fi/ https://archlinux.org/mirrors/kyberorg.fi/

Error is: Name or service not known (HTTP/HTTPS) and same for RSync:

rsync: getaddrinfo: rsync.kyberorg.fi http://rsync.kyberorg.fi/ 873: Name or service not known rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.2.7]

I just logged into our mirror checking server and indeed

ping rsync.kyberog.fi ping: rsync.kyberog.fi: Name or service not known

Resolving seems to go fine

dog rsync.kyberorg.fi A rsync.kyberorg.fi. 4m58s 135.181.204.71

Our server uses systemd-resolvd so it might be that dog doesn't use that.

# dig rsync.kyberog.fi

; <<>> DiG 9.18.11 <<>> rsync.kyberog.fi ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 19516 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 65494 ;; QUESTION SECTION: ;rsync.kyberog.fi. IN A

;; AUTHORITY SECTION: fi. 7079 IN SOA a.fi. fi-domain-tech.ficora.fi. 2023022040 3605 1800 2419200 86400

;; Query time: 0 msec ;; SERVER: 127.0.0.53#53(127.0.0.53) (UDP) ;; WHEN: Mon Feb 20 11:25:17 UTC 2023 ;; MSG SIZE rcvd: 105

Either way, I'll bring it up with the other devops. Thanks for reporting!

I checked other mirrors. Some of them also have the same problem. Even high ranked ones, like https://archlinux.org/mirrors/moson.org/ or https://archlinux.org/mirrors/osbeck.com/.

As is in my case "guilty" server(s) is/are:

49.12.124.107 2a01:4f8:242:5614::2

Thanks for investigating this issue and good luck.

пн, 20 февр. 2023 г. в 14:22, Jelle van der Waa jelle@vdwaa.nl:

Hi,

On 20/02/2023 12:28, Aleksandr Muravja wrote:

...

Well, kyberog != kyberorg.

Oof, well it resolves fine.

[jelle@gemini ~]# dig arch.kyberorg.fi

; <<>> DiG 9.18.11 <<>> arch.kyberorg.fi ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 10523 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 65494 ;; QUESTION SECTION: ;arch.kyberorg.fi. IN A

;; ANSWER SECTION: arch.kyberorg.fi. 291 IN A 135.181.204.71

Noticed now that arch.kyberorg.fi also fails:

https://arch.kyberorg.fi/ https Finland Name or service not known

So this is a Python application so I'll do some digging what's wrong!

Greetings,

Jelle