Thanks Peter
This makes sense. We have a Cisco router between the firewall and the
internet. It's one that our ISP provided us.
Cheers
Al
On 02/05/07, Peter Warasin [EMAIL PROTECTED] wrote:
Hi guys
Dave wrote:
Typically yes, 53 ought to be closed off on RED. At least insofar as it
Thanks Dave
Sorry for my ignorance, but why would it need to be open on port 53?
Doesn't it only need to allow outbound connections?
Cheers
Al
On 01/05/07, Dave [EMAIL PROTECTED] wrote:
DNS is port 53.
Al [EMAIL PROTECTED] writes:
I did a port scan on my PC using grc.com's Shields UP
Hi Al,
No need to be sorry. We are all at learning here together.
Typically yes, 53 ought to be closed off on RED. At least insofar as it forwards
requests to an internal IP (unless that's the plan).
If Endian is your gateway it's likely looking up IP's for your network so
clients can resolve
Hi guys
Dave wrote:
Typically yes, 53 ought to be closed off on RED. At least insofar as it
forwards
requests to an internal IP (unless that's the plan).
If Endian is your gateway it's likely looking up IP's for your network so
clients can resolve domains. I'm not certain on
DNS is port 53.
Al [EMAIL PROTECTED] writes:
I did a port scan on my PC using grc.com's Shields UP service.It found that my
port 53 is open. Is this normal? I can't see anything in the firewall config
that would open port 53.