Incorrect lookup of interfaces entry with multiple host lines

Given an interfaces entry like (data below has been sanitized for security reasons):

> MYDBSERVER
> query tcp ether myhost 3001
> query tcp ether myhost 3002
> query tcp ether myhost 3003

Sybase native dblib/ctlib libraries will try and connect to the first entry (port 3001),
then if that times out, they'll connect to the 2nd entry, and so on.

But it looks like freetds is connecting to the *last* entry (port 3003).  From the TDBDUMPCONFIG
output:

> config.c:867:Interfaces file /export/home/sybase/clients-mssql/current/interfaces opened.
> config.c:877:Found matching entry for host MYDBSERVER
> config.c:900:host field myhost.
> config.c:900:host field myhost.
> config.c:900:host field myhost.
> config.c:918:Resolved IP as 'NNN.NNN.NNN.NN'.
> config.c:641:Setting 'tdsver' to 5.0 from $TDSVER.
> config.c:195:Final connection parameters:
> config.c:196: server_name = MYDBSERVER
> config.c:197: port = 3003

Is this a known bug/deficiency?

Thanks
Ben Slade
Near Washington DC