On Mon, Apr 18, 2016 at 09:18:51PM -0700, David Christensen wrote:
> Please leave the bug report open.
Will do.
> Perhaps if Approx saved the IP address after the first name lookup and used
> that for all transfers, Approx would be more reliable (?).
Yes, that's been on my TODO list for a while.
> As a work-around, can I specify a host that is not round-robined in my
> approx.conf file? How do I find such hosts?
If you use the host command (from the bind9-host package at least),
you'll see all the IP addresses that a name resolves to:
$ host ftp.us.debian.org
ftp.us.debian.org has address 64.50.236.52
ftp.us.debian.org has address 64.50.233.100
ftp.us.debian.org has address 128.61.240.89
ftp.us.debian.org has address 128.30.2.26
ftp.us.debian.org has IPv6 address 2610:148:1f10:3::89
(And if you do it a few times, you'll see that they're returned in
different order, hence the problem.)
You can then find the symbolic name for one:
$ host 64.50.236.52
52.236.50.64.in-addr.arpa domain name pointer ftp-chi.osuosl.org.
and verify that it's not round-robined:
$ host ftp-chi.osuosl.org
ftp-chi.osuosl.org has address 64.50.236.52
Hope this helps.
--
Eric Cooper e c c @ c m u . e d u
