No, your PC will ask the DNS server for the AAAA IPv6 and A IPv4 records to get the IP-Address.
Since there is no AAAA record for repo.manjaro.org (anymore) your PC should immediately try to connect via IPv4.
What if you ping repo.manjaro.org. ? does it also take long? whats the output?
btw. what are your ipv6 network setting son the router:
Answer at instance/sofort:
ping repo.manjaro.org
PING repo.manjaro.org (116.203.249.219) 56(84) bytes of data.
64 Bytes von static.219.249.203.116.clients.your-server.de (116.203.249.219): icmp_seq=1 ttl=54 Zeit=11.8 ms
64 Bytes von static.219.249.203.116.clients.your-server.de (116.203.249.219): icmp_seq=2 ttl=54 Zeit=10.7 ms
64 Bytes von static.219.249.203.116.clients.your-server.de (116.203.249.219): icmp_seq=3 ttl=54 Zeit=11.3 ms
+
I see: Nur DNS-server zuweisen was flagged instead of DNS-Server, Präfix…
as told in the AVM-Advisor…
But no difference.
No clue. Works fine here (not Telekom though).
wget http://[2a03:4000:47:4db:d492:aaff:fed2:7b39]/stable/community/x86_64/0ad-a24.b-2-x86_64.pkg.tar.zst
Does it download the file?
No:
wget http://[2a03:4000:47:4db:d492:aaff:fed2:7b39]/stable/community/x86_64/0ad-a24.b-2-x86_64.pkg.tar.zst [1]
zsh: no matches found: http://[2a03:4000:47:4db:d492:aaff:fed2:7b39]/stable/community/x86_64/0ad-a24.b-2-x86_64.pkg.tar.zst
And:
ping 6 repo.manjaro.org
PING repo.manjaro.org (116.203.249.219) 56(124) bytes of data.
ping: sendmsg: Das Netzwerk ist nicht erreichbar
ping: sendmsg: Das Netzwerk ist nicht erreichbar
^C
— repo.manjaro.org ping statistics —
938 Pakete übertragen, 0 empfangen, 100% packet loss, time 949485ms
Sorry. With quotes:
wget "http://[2a03:4000:47:4db:d492:aaff:fed2:7b39]/stable/community/x86_64/0ad-a24.b-2-x86_64.pkg.tar.zst"
According to this, you need to use with the Telekomiker 
provider :
Done:
wget “http://[2a03:4000:47:4db:d492:aaff:fed2:7b39]/stable/community/x86_64/0ad-a24.b-2-x86_64.pkg.tar.zst” [1]
–2021-03-13 14:04:28-- http://[2a03:4000:47:4db:d492:aaff:fed2:7b39]/stable/community/x86_64/0ad-a24.b-2-x86_64.pkg.tar.zst
Verbindungsaufbau zu [2a03:4000:47:4db:d492:aaff:fed2:7b39]:80 … fehlgeschlagen: Die Wartezeit für die Verbindung ist abgelaufen.
Erneuter Versuch.
No clue then. I guess you’d need to check with Telekom then.
ping is also not working? ping 2a03:4000:47:4db:d492:aaff:fed2:7b39
You don’t block any outgoing v6 traffic or so on your firewall I assume? ufw status
Is there some specific reason you need IPv6 to be working? Some website that only serves via v6 ?
If not, I would just disable it. You don’t really have any benefit then.
ping 2a03:4000:47:4db:d492:aaff:fed2:7b39 [1]
PING 2a03:4000:47:4db:d492:aaff:fed2:7b39(2a03:4000:47:4db:d492:aaff:fed2:7b39) 56 data bytes
^C
--- 2a03:4000:47:4db:d492:aaff:fed2:7b39 ping statistics ---
10 Pakete übertragen, 0 empfangen, 100% packet loss, time 9109ms
UFW deactivated.
Let us give up.
Too early 
Fritz!Box Preferences:
Das Hilft!
This works.
EDIT:
pure accident. After the Fritz!Box crashed, everything worked like before November 2020;
maybe the Telekomiker had a good day finding the real poblem?
.
EDIT2:
This leads finally to the reason:
automatic update of network-settings in my router was DISABLED and the ISP made changes
w.o. telling useres. Solfted.
This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.
