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!