NETWORK PRESENCE ABOUT SERVICES PRODUCTS TRAINING CONTACT US SEARCH SUPPORT
 


Search
display results
words begin  exact words  any words part 

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [FW-1] AW: [FW-1] Name resolution


  • To: [email protected]
  • Subject: Re: [FW-1] AW: [FW-1] Name resolution
  • From: Hal Dorsman <[email protected]>
  • Date: Fri, 21 Jun 2002 12:07:17 -0600
  • Reply-to: Mailing list for discussion of Firewall-1 <[email protected]>
  • Sender: Mailing list for discussion of Firewall-1 <[email protected]>
  • Thread-index: AcIY6BGSFeJs5WPmS2qhI8btK3AMBwAXUUuQAAI4ZsA=
  • Thread-topic: [FW-1] AW: [FW-1] Name resolution

Title: AW: [FW-1] Name resolution
Well, maybe people running Raptor FW's don't know any better.
 
Checkpoint admins seem to understand that you shouldn't run
ANYTHING on a firewall.
 
Sorry, I just had to bust YOUR hump a little.
 
:)
 
Hal
-----Original Message-----
From: Steve McNutt [mailto:[email protected]]
Sent: Friday, June 21, 2002 11:03 AM
To: [email protected]
Subject: Re: [FW-1] AW: [FW-1] Name resolution

I hate to be a contrarian, but people run DNS on raptor firewalls all of the time.  I know you probably meant checkpoint firewalls, but I just had to bust your hump a little ;-)

 

-s

 

-----Original Message-----
From: Andrew Jones [mailto:[email protected]]
Sent:
Friday, June 21, 2002 1:07 AM
To: [email protected]
Subject: [FW-1] AW: [FW-1] Name resolution

 

Dude, this is so not a firewall issue. You can't do this with a firewall, and this functionality doesn't make sense with a firewall anyway. The DNS suffix lists ARE the way to do this.

                        -&

 

 



 
----------------------------------

ABOUT SERVICES PRODUCTS TRAINING CONTACT US SEARCH SUPPORT SITE MAP LEGAL
   All contents © 2004 Network Presence, LLC. All rights reserved.