tickets #91722
closedmirror.tspu.ru is not resolvable, but is the only mirror that serves Mozilla repo
100%
Description
Hello,
The default mirror for my region (EU) mirror.tspu.ru, is unresolvable,
but it still redirect me to the mirror, which fails update because this
the only mirror that serves the mozilla repo
(https://download.opensuse.org/repositories/mozilla/openSUSE_Tumbleweed/x86_64/)
Here is what dig mirror.tspu.ru
returns :
; <<>> DiG 9.16.12 <<>> mirror.tspu.ru
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 16978
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
; EDE: 6 (DNSSEC Bogus)
;; QUESTION SECTION:
;mirror.tspu.ru. IN A
;; Query time: 188 msec
;; SERVER: 1.0.0.1#53(1.0.0.1)
;; WHEN: lun. avril 26 11:28:49 CEST 2021
;; MSG SIZE rcvd: 49
I can't update my system without disabling the repo, which is fine for now
Updated by pjessen almost 3 years ago
- Category set to Mirrors
- Status changed from New to Workable
- Private changed from Yes to No
stigpro@outlook.fr wrote:
Hello,
The default mirror for my region (EU) mirror.tspu.ru, is unresolvable,
but it still redirect me to the mirror, which fails update because this
the only mirror that serves the mozilla repo
(https://download.opensuse.org/repositories/mozilla/openSUSE_Tumbleweed/x86_64/)
For me, "mirror.tspu.ru" resolves fine, no problems:
dig mirror.tspu.ru a
; <<>> DiG 9.16.6 <<>> mirror.tspu.ru a
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 46452
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;mirror.tspu.ru. IN A
;; ANSWER SECTION:
mirror.tspu.ru. 84152 IN A 193.106.132.11
;; Query time: 0 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Mon Apr 26 12:25:01 CEST 2021
;; MSG SIZE rcvd: 59
Also, looking at this mirror list (for instance):
Found 6 mirrors in other countries, but same continent (EU)
http://widehat.opensuse.org/repositories/mozilla/openSUSE_Tumbleweed/x86_64/enigmail-2.2.4-95.2.x86_64.rpm (de, prio 100)
https://ftp.gwdg.de/pub/opensuse/repositories/mozilla/openSUSE_Tumbleweed/x86_64/enigmail-2.2.4-95.2.x86_64.rpm (de, prio 110)
http://mirror.karneval.cz/pub/linux/opensuse/repositories/mozilla/openSUSE_Tumbleweed/x86_64/enigmail-2.2.4-95.2.x86_64.rpm (cz, prio 100)
http://ftp.lysator.liu.se/pub/opensuse/repositories/mozilla/openSUSE_Tumbleweed/x86_64/enigmail-2.2.4-95.2.x86_64.rpm (se, prio 100)
http://mirror.linux-ia64.org/opensuse/repositories/mozilla/openSUSE_Tumbleweed/x86_64/enigmail-2.2.4-95.2.x86_64.rpm (ru, prio 100)
http://mirror.tspu.ru/opensuse/repositories/mozilla/openSUSE_Tumbleweed/x86_64/enigmail-2.2.4-95.2.x86_64.rpm (ru, prio 100)
It might be interesting to see your mirrorlist for the same file.
Updated by pjessen almost 3 years ago
I can confirm that cloudflare is broken (dnssec fails):
dig @1.0.0.1 mirror.tspu.ru a
; <<>> DiG 9.16.6 <<>> @1.0.0.1 mirror.tspu.ru a
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 9351
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
; EDE: 6 (DNSSEC Bogus)
;; QUESTION SECTION:
;mirror.tspu.ru. IN A
;; Query time: 1635 msec
;; SERVER: 1.0.0.1#53(1.0.0.1)
;; WHEN: Mon Apr 26 12:31:02 CEST 2021
;; MSG SIZE rcvd: 49
dig +cdflag @1.0.0.1 mirror.tspu.ru a
; <<>> DiG 9.16.6 <<>> +cdflag @1.0.0.1 mirror.tspu.ru a
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6543
;; flags: qr rd ra cd; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;mirror.tspu.ru. IN A
;; ANSWER SECTION:
mirror.tspu.ru. 86400 IN A 193.106.132.11
;; Query time: 87 msec
;; SERVER: 1.0.0.1#53(1.0.0.1)
;; WHEN: Mon Apr 26 12:34:57 CEST 2021
;; MSG SIZE rcvd: 59
Updated by bmwiedemann almost 3 years ago
It is not just cloudflare:
host -t ns tspu.ru 8.8.4.4
Using domain server:
Name: 8.8.4.4
Address: 8.8.4.4#53
Aliases:
Host tspu.ru not found: 2(SERVFAIL)
host -t ns tspu.ru 8.8.8.8
Using domain server:
Name: 8.8.8.8
Address: 8.8.8.8#53
Aliases:
tspu.ru name server ns2.r01.ru.
tspu.ru name server ns.tspu.edu.ru.
tspu.ru name server ns.zsttk.ru.
All 3 of those can produce the right reply.
host mirror.tspu.ru 9.9.9.9
Using domain server:
Name: 9.9.9.9
Address: 9.9.9.9#53
Aliases:
mirror.tspu.ru has address 193.106.132.11
Host mirror.tspu.ru not found: 2(SERVFAIL)
Host mirror.tspu.ru not found: 2(SERVFAIL)
host mirror.tspu.ru 9.9.9.9
Using domain server:
Name: 9.9.9.9
Address: 9.9.9.9#53
Aliases:
Host mirror.tspu.ru not found: 2(SERVFAIL)
so is dnssec broken at the tspu.ru domain?
Updated by pjessen almost 3 years ago
bmwiedemann wrote:
It is not just cloudflare:
[snip]
so is dnssec broken at the tspu.ru domain?
Yes, that is what is sounds like, but I am no expert on dnssec.
Updated by toto almost 3 years ago
Yes, one of our slave NS server began to work incorrectly. It has been replaced.
Sorry for the noise.
Updated by pjessen almost 3 years ago
- Status changed from Workable to Resolved
- Assignee set to pjessen
- % Done changed from 0 to 100
Sounds like the problem was solved, many thanks!