>From what I've learned, IANA has been "silently discarding" resolution
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
"read-rfc1918-for-details.iana.net". After much public uproar, it was
backed
off. IANA is giving time to organizations to have vendors fix code
affected by
this change. I hear Openview customers had major grief with the product
going
into name resolution/object update loops. I was also told that IANA will
again
be answering requests for private networks soon and this time will not
be
backed off.  Hope that helps!

Massimo Carnevali wrote:

> 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, may be it is asking outside what it
> should
> keep inside.
> Hope this helps.
> Massimo Carnevali - IBM Global Services -Italy