Interesting. We resolve our rfc1918 addresses on our own DNS servers.
Those servers do NOT involve external DNS servers in resolving undefined
rfc1918 addresses, so I had not seen the resolution result you described.
If you are seeing this (read-rfc1918-for-details.iana.net) on your internal
network then at least one of your DNS servers must be involving external
DNS servers in resolving addresses. If this is not your intent then your
separation between internal DNS and external DNS is not complete.
Delmer
James Smith <[EMAIL PROTECTED]> on 04/21/99 10:19:04 AM
To: [EMAIL PROTECTED]
cc: (bcc: Delmer Harris/ASFMT)
Subject: read-rfc1918-for-details.iana.net
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.]
