March 1, 2020. archlinux.org is not being resolved DNS issue?

FirstAirBender · 2020-03-02 04:06:51

I recently started noticing that any time my machine tries to connect to archlinux.org or any subdomain, it will often take a long time, or after multiple tries, finally is able to connect.

A video speaks volumes:

https://vimeo.com/394853518

I thought this may be an issue with the domain itself, and I have been searching online to see if anyone else is experiencing this same issue, but the internet seems to be very calm and I have not noticed any new topics around this issue, so that's why I have resorted to ask on this forum.
Additionally, my phone seems to have no problem connecting to the domain, which is what has led me to suspect that it may have something to do with the fact that I use unbound as my DNS resolver.

I don't know if this is my problem or someone else is noticing this as well. I have been scratching my head wondering what the issue could possibly be and why it only seems to affect one domain. I have restarted my computer and I have restarted the unbound service, but the problem still persists.

Even attempting to ask this question took forever to post because I had to keep retrying to connect

Any help will be appreciated.

Ping:
➜ ping -c5 archlinux.org
PING archlinux.org (138.201.81.199) 56(84) bytes of data.
64 bytes from apollo.archlinux.org (138.201.81.199): icmp_seq=1 ttl=54 time=256 ms
64 bytes from apollo.archlinux.org (138.201.81.199): icmp_seq=4 ttl=54 time=186 ms

--- archlinux.org ping statistics ---
5 packets transmitted, 2 received, 60% packet loss, time 8273ms
rtt min/avg/max/mdev = 186.276/221.321/256.366/35.045 ms

Dig:
➜ dig TXT archlinux.org

; <<>> DiG 9.16.0 <<>> TXT archlinux.org
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 57327
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;archlinux.org. IN TXT

;; ANSWER SECTION:
archlinux.org. 86400 IN TXT "v=spf1 mx ip4:66.211.214.132/28 ip4:5.9.250.164 ip6:2a01:4f8:160:3033::2 ip4:138.201.81.199/32 ip4:88.198.91.70/32 a:aur.archlinux.org a:apollo.archlinux.org ?all"

;; Query time: 483 msec
;; SERVER: ::1#53(::1)
;; WHEN: Sun Mar 01 22:24:21 CST 2020
;; MSG SIZE rcvd: 217

I'm basically looking for debug help because I don't know how else to debug this issue. Like I mentioned in the post, I use unbound for DNS resolution, so if anyone knows any way to debug unbound so that we can see what is really going on, that would really help.

Last edited by FirstAirBender (2020-03-02 04:51:23)

jasonwryan · 2020-03-02 04:11:45

Rather than post a video no-one will watch, post details of your networking setup, journal entries, or output from dig, ping etc.

Lone_Wolf · 2020-03-02 13:36:20

Please post output of

$ ping -6 archlinux.org
$ ping 2a01:4f8:172:1d86::1
$ ping 138.201.81.199

FirstAirBender · 2020-03-02 19:24:23

➜ ping -6 archlinux.org
ping: connect: Network is unreachable

/tmp
➜ ping 2a01:4f8:172:1d86::1
ping: connect: Network is unreachable

/tmp
➜ ping 138.201.81.199
PING 138.201.81.199 (138.201.81.199) 56(84) bytes of data.
64 bytes from 138.201.81.199: icmp_seq=1 ttl=54 time=350 ms
64 bytes from 138.201.81.199: icmp_seq=2 ttl=54 time=378 ms
64 bytes from 138.201.81.199: icmp_seq=3 ttl=54 time=193 ms
64 bytes from 138.201.81.199: icmp_seq=4 ttl=54 time=215 ms
64 bytes from 138.201.81.199: icmp_seq=5 ttl=54 time=239 ms
64 bytes from 138.201.81.199: icmp_seq=6 ttl=54 time=265 ms
64 bytes from 138.201.81.199: icmp_seq=7 ttl=54 time=283 ms
^C
--- 138.201.81.199 ping statistics ---
7 packets transmitted, 7 received, 0% packet loss, time 6007ms
rtt min/avg/max/mdev = 192.792/274.667/378.255/63.452 ms

It seems we have a good connection there because the ping seems alright (i.e. no dropped packets), but let me just wait and try again when the issue starts to happen.

Meh...after 5 mins and flushing the cache, I don't seem to be experiencing the issue, but then again I'm not sure if this is just me or something was resolved on the server side. I didn't do anything different between yesterday and today, so this is still weird for me.

Lone_Wolf · 2020-03-03 11:20:33

Those outputs suggests your connection doesn't support ipv6 fully and this is not a resolve problem.
Let's look at lower level network stuff .

Install traceroute if needed, then run and post output of

$ ip addr
$ ip link
$ ip -4 route
$ traceroute -4 archlinux.org
$ ip -6 route
$ traceroute -6 archlinux.org

Last edited by Lone_Wolf (2020-03-03 11:21:48)

Arch Linux

#1 2020-03-02 04:06:51

March 1, 2020. archlinux.org is not being resolved DNS issue?

#2 2020-03-02 04:11:45

Re: March 1, 2020. archlinux.org is not being resolved DNS issue?

#3 2020-03-02 13:36:20

Re: March 1, 2020. archlinux.org is not being resolved DNS issue?

#4 2020-03-02 19:24:23

Re: March 1, 2020. archlinux.org is not being resolved DNS issue?

#5 2020-03-03 11:20:33

Re: March 1, 2020. archlinux.org is not being resolved DNS issue?

Board footer