copying the question section

[dean gaudet]

On Sun, 4 Aug 2002, Paul Vixie wrote:

> |   - Some name servers send their responses from different
> |     addresses than the one used to receive the query.  That is, a
> |     resolver cannot rely that a response will come from the same
> |     address which it sent the corresponding query to.  This name
> |     server bug is typically encountered in UNIX systems.
>
> libresolv, libbind, and bind8 have required that the response source be the
> same as the query destination since about the BIND KJB/4.9 era, and there's
> no reason to relax now.  (SunOS 4.1.3 was the culprit, and is long dead.)

it seems that aol nameservers have a hell of a time returning responses
from the proper address.

below are the top 20 'response from unexpected source' log entries for my
server today.

-dean

     32	mailin-03.mx.aol.com IN AAAA
     32	mailin-01.mx.aol.com IN A6
     27	ns2.netscape.com IN AAAA
     22	mailin-04.mx.aol.com IN A
     21	ns.worldnet.att.net IN A6
     20	mailin-04.mx.aol.com IN AAAA
     20	mailin-04.mx.aol.com IN A6
     20	mailin-01.mx.aol.com IN AAAA
     19	ns.netscape.com IN A6
     19	mailin-02.mx.aol.com IN AAAA
     19	mailin-02.mx.aol.com IN A6
     12	mailin-03.mx.aol.com IN A6
     12	DNS2.lisco.com IN AAAA
     11	DNS1.lisco.com IN A6
     10	mailin-03.mx.aol.com IN A
     10	mailin-02.mx.aol.com IN A
     10	mailin-01.mx.aol.com IN A
      9	NS1.NETSCAPE.COM IN AAAA
      8	mailin-02.mx.netscape.net IN A6
      8	NS1.NETSCAPE.COM IN A6