Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*read\-rfc1918\-for\-details\.iana\.net\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*read\-rfc1918\-for\-details\.iana\.net\s*$/: 2 ]

Total 2 documents matching your query.

1. Re: read-rfc1918-for-details.iana.net (score: 1): Author: Massimo Carnevali <Massimo.Carnevali AT COMUNE.BOLOGNA DOT IT>; Date: Fri, 30 Apr 1999 13:45:46 +0100; I too noticed this problem. It seems that for a small perdiod of days trying to resolve internal addresses (like 10.*.*.*) on the external world gave that answer. Check your DNS inverse ip resolution; /usr/local/webapp/mharc-adsm.org/html/nv-l/1999-04/msg00618.html (10,555 bytes)
2. Re: read-rfc1918-for-details.iana.net (score: 1): Author: Dave Luiz <daveluiz AT JPS DOT NET>; Date: Fri, 30 Apr 1999 08:30:07 -0700; requests for all private networks specified in rfc1918. After seeing these illegal requests climb in number, they decided to start enforcing policy and began to answer these resolution requests with; /usr/local/webapp/mharc-adsm.org/html/nv-l/1999-04/msg00628.html (11,330 bytes)

Current List: 1 - 2
Page: [1]