Hi, I received notification via bug 38073 that our mirror server was not responding to rsync requests: rsync: failed to connect to 193.1.219.88: No route to host Please note that our mirror server is two headed: ftp.heanet.ie (which resolves to 193.1.219.100) should be used for advertising an rsync/http/ftp server for clients to use. rsyncer.ftp.heanet.ie (which resolves to 193.1.219.88) should be allowed access to upstream rsync server rsync1.us.gentoo.org, but should not itself be advertised. Thanks, Brian. Reproducible: Always Steps to Reproduce: 1. 2. 3.
Okay, it all sorted out. 193.1.219.100 now has access to rsync1.us 192.1.219.88 is now in the rsync.europe and rsync.ie rotation. sorry for the confusion, happy mirroring! thanks for helping out.
Hi, In your resolution to this bug, I think you got things the wrong way around. You said: 193.1.219.100 now has access to rsync1.us 192.1.219.88 is now in the rsync.europe and rsync.ie rotation. Theres two things wrong here: 1) The IP Address above, 192.1.219.88 is wrong - may be just a type, but all our servers are in 193.1... 2) 193.1.219.100 will never try to contact rsync1.us - it is the world facing http/ftp/rsync request filler. It should be put in rsync and rsync.ie rotation for use by other sites who wish to sync from our gentoo mirror. It is also for use by anyone wish to access our gentoo mirror by ftp or http. 193.1.219.88 is a rsync client - it needs access to rsync1.us to download changes to files on your gentoo master mirror. You never need to put it in any rotation, DNS or otherwise, but any access controls on the rsync daemon on rsync1.us should permit it. Best regards, Brian.
Hi, To continue on this subject, it looks like the DNS side is pointing at the right target - I guess you got them mixed up in your bug response only. Would it be possible to refer to our server using a CNAME rather than an A record? This allows us flexibility should our server ever need to change address, and automatically makes IPV6 work, as clients with IPV6 turned on will automatically look up the AAAA record for our site. Best regards, Brian.
My sincere apologies, lets see if I get this right now ;) 193.1.219.88 -- has access to rsync1.us 193.1.219.100 -- is in the dns rotation to be seen by the world With regards to your CNAME/A record question, I will forward that query to someone with more expertise than I in the matter, and will post a response to this bug when I receive it. Thanks for helping out! -Jeffrey
