SUMMARY II: monitoring DNS

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]

Hi and thanks to Reto Lichtensteiger <rali@meitca.com>,
                 Bill Krauss <billk@LANcomp.COM>,
                 Nicky Ayoub <Nicky.Ayoub@Microchip.COM>,
                 Jochen Bern <bern@penthesilea.uni-trier.de> ,
                 Michael Ryan <mike@networx.ie>

-----------------
Original question
-----------------
I would like to know if possible to filter incoming requests for my DNS.

I can prensently filter incoming requests for many network services like
ftp, telnet, etc... with TCPWrapper 7.4

-------
Answers
-------

<rali@meitca.com> said:

<<If you block server requests, then how will anyone look up your mail
  server?>>

So, by the way I have to have a DNS visible for the world.

<billk@LANcomp.COM>,
<Nicky.Ayoub@Microchip.COM>,
<bern@penthesilea.uni-trier.de> ,
<mike@networx.ie>

they said around the samethings:

<<It's important to split my DNS>>

<<This is where you set up two DNS servers. The 1st
  answers DNS queries to the outside world and sits on the outside
  of your firewall. The 2nd is inside the firewall and answers
  DNS queries for the internal network. The inside server uses
  the outside server as a "forwarders" and is a "slave". The
  outside server contains entries for just the machines you want
  the world to know about (e.g. Web server, FTP server, mail
  server, etc.). >>

Thanks to all,

Best Regards,

--
JFD
_________________________________
 Jean-Frederic Dallaire
 System Administrator
 Hydro-Quebec
 dallaire@rouyn-ogc.hydro.qc.ca
_________________________________

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]

This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:11:05 CDT