On Wed, 21 Apr 1999 12:22:06 -0700 (PDT), you wrote:
>This was coming from the authoritative servers for the RFC 1918 space
>zones. It has been planned for more than a year. The data that drove
>the change was the exponental increase in the number of queries that
>these servers receive. This was an indication that firewall and NAT
>designers were becoming "sloppy" and not following the RFC statement
>that these addresses should not appear in the Internet. It appears
>that besides the "sub-optimal" firewall & NAT implementations, there
>are also other commercial packages that object to authoritative
>replies. :) This effect was compounded by the terse lable that formed
>the query response.
Let me follow up on this one. My ISP uses a 192.168 number for a
router on their network. Formerly, I received a DNS timeout when I did
a traceroute through that router. Now, I get a
read-rfc1918-for-details.iana.net reply. I am not in a position to
change that since my machine uses my ISPs name server.
What are they supposed to do about that? Change their DNS (which won't
solve the issue for traces coming from the outside) or stop using
RfC1918 addresses for routers?
Greetings
Marc
--
-------------------------------------- !! No courtesy copies, please !! -----
Marc Haber | " Questions are the | Mailadresse im Header
Karlsruhe, Germany | Beginning of Wisdom " | Fon: *49 721 966 32 15
Nordisch by Nature | Lt. Worf, TNG "Rightful Heir" | Fax: *49 721 966 31 29
-
[To unsubscribe, send mail to [EMAIL PROTECTED] with
"unsubscribe firewalls" in the body of the message.]
