Yeah, we noticed this this morning. I'm surprised there wasn't more
uproar. It's definitely new. I noticed it because I had built tcpd w/
-DPARANOID, and was allowing 2 machines from outside my control telnet
access over a leased line into one of my boxes. Well, when their
addresses started resolving to a not resolvable name, I started dropping
them immediately. The solution of course was to start serving up an empty
reverse zone.
> Has anyone picked up on the fact that private (rfc1918) IP addresses
> suddenly started resolving to read-rfc1918-for-details.iana.net in the last
> few days?
>
> This is affecting my, and other's syslog listings and all my machines on our
> 192.168.x.x internal network behind our NAT box and Firewall.
>
> Is this a new decision in the world of TCP/IP that I missed? Also DNS seems
> to resolve these addresses as this host name (nslookup) this seems to be the
> seat of the problem, but no one can tell me if this is new.
>
> Though this is probably not a Firewall issue it affects private networks
> which are generally behind Firewalls.... Oh I'm not going to try to motivate
> why I posted it here, I just wanted the best brains I knew of to brainstorm
> about the problem.
>
> Regards,
>
> James Smith
>
> -
> [To unsubscribe, send mail to [EMAIL PROTECTED] with
> "unsubscribe firewalls" in the body of the message.]
>
-
[To unsubscribe, send mail to [EMAIL PROTECTED] with
"unsubscribe firewalls" in the body of the message.]
