From owner-freebsd-hackers  Fri Dec 29 12:17:22 1995
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id MAA11072
          for hackers-outgoing; Fri, 29 Dec 1995 12:17:22 -0800 (PST)
Received: from romulus.ultranet.com ([199.232.56.2])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id MAA11066
          for <freebsd-hackers@freebsd.org>; Fri, 29 Dec 1995 12:17:18 -0800 (PST)
Received: (from jprovo@localhost) by romulus.ultranet.com (8.7.1/ad0.2) id PAA02646; Fri, 29 Dec 1995 15:15:13 -0500 (EST)
Date: Fri, 29 Dec 1995 15:15:13 -0500 (EST)
From: Joe Provo <jprovo@romulus.ultranet.com>
Message-Id: <199512292015.PAA02646@romulus.ultranet.com>
To: bind-users@vix.com, freebsd-hackers@freebsd.org, volf@oasis.IAEhv.nl
Subject: Re: Freebsd IP alias and BIND
Sender: owner-hackers@freebsd.org
Precedence: bulk


[clip]
>> When a query is sent to the IP alias two responses are generated: one
>> response with the real IP address as the source address, the other one with
>> the alias address as the source address:
[clip]
>I did some more testing to find this problem. With bind debuggind enabled, I 
>found:
[clip]
>This means that bind really gets two copies of the datagram (one send to
>fd 6, the other one to fd 8) and hence, bind is operating correctly and 
>FreeBSD is wrong:

This seems to be the case with most services on alias interfaces; breaking 
or working "right" is OS specific.  For the record, attempting to use alias
interfaces as an "authoritative" name server breaks on OSF [DEC Unix(tm)] 
3.2 (4.9.3b24).

Cheers,

Joe Provo
Network Operations Center
UltraNet Communications, Inc.