|
|
|
|
|
|
|
|
 |
 |
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] RE: [FW1] Strange Log Entry
I think the point is that these addresses should not be in public DNS servers, since they are by definition private addresses. I would certainly agree to have them in private DNS servers. They are not only used by engineers but by the whole internal network for host resolution as well. We generally go to great pains to hide our internal addressing from the public. Why should we then advertise it our DNS? Not to mention causing some of the unusal results that prompted the question in the first place. Daniel Gaughan -----Original Message----- From: [email protected] [mailto:[email protected]] Sent: Friday, January 05, 2001 6:27 PM To: [email protected]; [email protected] Cc: [email protected] Subject: Re: [FW1] Strange Log Entry I don't know if I would agree with that. Lot's of ISP's use RFC1918 addressing AND DNS entries for the management of broadband/adsl networks. Usually the ADSL/Cablemodem will obtain an RFC1918 address during it's bootp process. This is used by network engineers for SNMP and other diagnostic tools. It's kind of handy to have DNS entries for those. Sometimes the provider does not do a good job and allows those RFC1918 addresses to traverse the bridge so you might see them leaking across occassionally. Seattle, WA 98134-2383 mailto:[email protected] ================================================================================ To unsubscribe from this mailing list, please see the instructions at http://www.checkpoint.com/services/mailing.html ================================================================================
|
||||||||||
 |
 |
 |
 |
 |
 |
 |
 |
 |
|
