Basic question: Why let anyone know what is inside or outside?
Do you plan an "hardening" every system now that you've told everyone what
are the interesting systems?
Merton Campbell Crockett
On Wed, 9 Feb 2000, Bennett Samowich wrote:
> It would seem that using the "int" or "in" doesn't allow for easy expansion
> beyond the initial subnet. I have used divisional acronyms at a few of my
> clients. I also have used names based on geographic locations
> (e.g. host.state.domain.com or host.city.domain.com)
>
> Just my .02,
> - Bennett
>
> At 03:00 PM 2/9/00 -0800, lewst wrote:
> >Greetings,
> >
> >I have some questions regarding how to name my internal network
> >subdomain. What are the commonly used subdomains for firewalled
> >internal networks?
> >
> >I have thought of "*.int.domain.com" and "*.in.domain.com"
> >
> >Which of these two is more standard? Can you think of any others?
> >I'd like to get lots of opinions on this issue. Thanks.
> >
> >(Please CC: me on followups)
> >
> >__________________________________________________
> >Do You Yahoo!?
> >Talk to your friends online with Yahoo! Messenger.
> >http://im.yahoo.com
> >-
> >[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.]
>
-
[To unsubscribe, send mail to [EMAIL PROTECTED] with
"unsubscribe firewalls" in the body of the message.]
