Re: glibc's getaddrinfo() sort order
* Anthony Towns:
> FreeBSD 6.2, Jan 2007: stable, but not rule 9
>
> 10:00 <gjb> {'96.96.96.96': 1000}
> 10:00 <aj> what os?
> 10:00 <gjb> Python 2.4.3 (#2, Nov 8 2006, 23:56:15)
> 10:00 <gjb> FreeBSD 6.2-RELEASE-p5 i386 SMP-GENERIC
> 10:34 <gjb> aj: it was 172.16.x.x, nat'd behind 203.y.y.y
On FreeBSD 6.2, I get:
{'144.144.144.144': 66, '64.64.64.64': 67, '240.240.240.240': 66, '32.32.32.32': 67, '208.208.208.208': 67, '96.96.96.96': 67, '192.192.192.192': 67, '112.112.112.112': 66, '160.160.160.160': 67, '176.176.176.176': 67, '80.80.80.80': 66, '16.16.16.16': 67, '48.48.48.48': 66, '128.128.128.128': 67, '224.224.224.224': 67}
This is with a BIND 9 resolver in the default configuration (IOW, it
performs round-robin).
> Fedora Core 5, March 2005: stable
>
> 10:02 <Jerub> {'128.128.128.128': 1000}
> 10:03 <aj> jerub: os?
> 10:03 <Jerub> aj: fedora core 5, behind a caching bind server.
Does that BIND perform round-robin address selection?
Reply to: