Bug 49141 – rsync.nl.gentoo.org is not up2date and holds a Turkish mirror

• Status: RESOLVED FIXED
• Product: Mirrors

[Description Xavier Neys (RETIRED) 2004-04-27 03:06:38 UTC]

Some Dutch rsync mirrors haven't been available for a while but are still in the rotation. Besides a Turkish mirror made its way into the nl group.

Checked with this one-liner:
HO=rsync.nl.gentoo.org ruby -e '`dig #{ENV["HO"]}`.each{|l| puts "#{$1}\t=>\t#{`host #{$1}`.gsub("\n","\n\t\t\t")}\n" if l =~ /^#{ENV["HO"]}.\s\d+\sIN\sA\s(\d+\.\d+\.\d+\.\d+)/}'

80.251.40.16    =>      16.40.251.80.in-addr.arpa domain name pointer bianca.cc.ankara.edu.tr.

81.173.7.182    =>      Host 182.7.173.81.in-addr.arpa not found: 3(NXDOMAIN)

132.229.67.201  =>      Host 201.67.229.132.in-addr.arpa not found: 3(NXDOMAIN)

195.86.128.57   =>      57.128.86.195.in-addr.arpa domain name pointer ftp.easynet.nl.

212.79.254.44   =>      44.254.79.212.in-addr.arpa domain name pointer rsync5.nl.gentoo.org.

Same check on the Belgian rotation is OK (just for the example)
193.190.198.19  =>      19.198.190.193.in-addr.arpa domain name pointer dalet.belnet.be.

195.238.1.14    =>      14.1.238.195.in-addr.arpa domain name pointer bismuth.skynet.be.

134.184.49.5    =>      5.49.184.134.in-addr.arpa domain name pointer igwe5.vub.ac.be.
                        5.49.184.134.in-addr.arpa domain name pointer moon.vub.ac.be.

[Comment 1 Peter Penkala 2004-05-14 11:07:55 UTC]

Removed 80.251.40.16 from the .nl rotation.  Looks like it was added by mistake.

The other .nl IPs seem valid.  Do you have specific IPs that appear to be 
unavailable?

Thanks.

[Comment 2 Xavier Neys (RETIRED) 2004-05-14 12:07:50 UTC]

Thanks.

I was wondering about those two which have no reverse DNS but rsync::{their IP} does work indeed.

Strangely I always end up with either rsync4.nl.gentoo.org or rsync5.nl.gentoo.org when I use the rsync.nl.gentoo.org rotation. I just tried _repeatedly_, enough for getting banned for at least a week ;-) It's probably a coincidence though.

It's probably not worth checking any further. I'll leave it up to you.

Cheers.

[Comment 3 Peter Penkala 2004-05-14 13:18:25 UTC]

I think we'll call this fixed then.

Thanks again.