Post by Yury V. ZaytsevHi!
Oh really?
;; global options: printcmd
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 42216
;; flags: qr aa rd; QUERY: 1, ANSWER: 5, AUTHORITY: 0, ADDITIONAL: 3
;; WARNING: recursion requested but not available
;rpmrepo.net. IN ANY
rpmrepo.net. 10800 IN SOA ns.rpmrepo.org. hostmaster.rpmrepo.org.
2009120605 10800 3600 864000 259200
rpmrepo.net. 10800 IN NS ns0.rpmrepo.org.
rpmrepo.net. 10800 IN NS ns1.rpmrepo.org.
rpmrepo.net. 10800 IN MX 10 mail.rpmrepo.org.
rpmrepo.net. 10800 IN A 160.45.254.23
ns0.rpmrepo.org. 10800 IN A 160.45.254.18
ns1.rpmrepo.org. 10800 IN A 160.45.254.19
mail.rpmrepo.org. 10800 IN A 160.45.254.20
;; Query time: 78 msec
;; SERVER: 160.45.254.18#53(160.45.254.18)
;; WHEN: Wed Mar 31 17:50:42 2010
;; MSG SIZE rcvd: 211
Sounds like a DNS cache...
Yuri,
It's not a caching issues, the issue is that different servers have an
inconsistent view of the world, so it's a question of luck which one you
would happen to contact.
There are at least two major issues:
1. For rpmrepo.org, there is an inconsistency between the DNS and whois.
According to the .org nameservers (which take their info from whois),
the servers are:
ns0.rpmrepo.org. 160.45.254.18
ns1.rpmrepo.org. 85.13.226.40
160.45.254.18 has an old 2009120605 version of the rpmrepo.org zone,
where the nameservers are:
ns0.rpmrepo.org. 160.45.254.18
ns1.rpmrepo.org. 160.45.254.19
(note an inconsistent IP for ns1)
85.13.226.40 has a much newer 2010021503 version of the rpmrepo.org
zone, where the nameservers are:
ns1.rpmrepo.org. 85.13.226.40
ns2.rpmrepo.org. 188.40.68.214
and in this version of the zone, ns0.rpmrepo.org does not exist. And
188.40.68.214 has the same version of the zone.
2. Whois for rpmrepo.net points to ns0.rpmrepo.org. and ns1.rpmrepo.org,
but the *new* ns1.rpmrepo.org (85.13.226.40) does not know anything
about rpmrepo.net (the *old* ns0 and ns1 at 160.45.254.18 and
160.45.254.19 do know).
It looks like somebody moved the DNS for rpmrepo.org recently, but:
a. Did not fully update the whois (ns1 IP was updated, but the ns0 to
ns2 switch was done only in DNS, not in whois)
b. Did not tell the old 160.45.254.18/160.45.254.19 servers that they
are no longer authoritative for rpmrepo.org, so they continued to serve
the old zone.
c. Did not either move the rpmrepo.net to the new servers, or otherwise
made sure rpmrepo.net is still OK after the rpmrepo.org move.
Hopefully somebody could do the a-c now to fix all this.
Aleksey