On 21 February 2013 01:28, Robert Moskowitz r...@htt-consult.com wrote:
It looks like no system, internal or external could access the DNS on my
new server. IPTABLES was set for 53 both UDP and TCP. Firewall was OK.
In fact a local system on the same subnet, thus NOT going through my
On 02/21/2013 04:30 AM, James Hogarth wrote:
On 21 February 2013 01:28, Robert Moskowitz r...@htt-consult.com wrote:
It looks like no system, internal or external could access the DNS on my
new server. IPTABLES was set for 53 both UDP and TCP. Firewall was OK.
In fact a local system on the
Great. I have to make notes on how to test about selinux reporting.
audit2allow is useful to generate custom modules etc too - just don't be to
blind in using them ;)
other useful things are semange boolean and so on - centos has a good wiki
page on selinux
I assume that 'getenforce
On Thursday 21 February 2013 11:25:44 Robert Moskowitz wrote:
On 02/21/2013 04:30 AM, James Hogarth wrote:
On 21 February 2013 01:28, Robert Moskowitz r...@htt-consult.com
wrote:
It looks like no system, internal or external could access the
DNS on my new server. IPTABLES was set for 53
On 02/20/2013 08:28 PM, Robert Moskowitz wrote:
It looks like no system, internal or external could access the DNS on my
new server. IPTABLES was set for 53 both UDP and TCP. Firewall was OK.
In fact a local system on the same subnet, thus NOT going through my
firewall was denied access to
Robert Moskowitz rgm@... writes:
It looks like no system, internal or external could access the DNS on my
new server. IPTABLES was set for 53 both UDP and TCP. Firewall was OK.
In fact a local system on the same subnet, thus NOT going through my
firewall was denied access to the
On 02/21/2013 10:16 AM, David G. Miller wrote:
Robert Moskowitz rgm@... writes:
It looks like no system, internal or external could access the DNS on my
new server. IPTABLES was set for 53 both UDP and TCP. Firewall was OK.
In fact a local system on the same subnet, thus NOT going through
It looks like no system, internal or external could access the DNS on my
new server. IPTABLES was set for 53 both UDP and TCP. Firewall was OK.
In fact a local system on the same subnet, thus NOT going through my
firewall was denied access to the internal domain. Localhost of course
works.
How about checking logs ?
Eero
On Thursday, February 21, 2013, Robert Moskowitz wrote:
It looks like no system, internal or external could access the DNS on my
new server. IPTABLES was set for 53 both UDP and TCP. Firewall was OK.
In fact a local system on the same subnet, thus NOT going
9 matches
Mail list logo
