Re: DNS problems NOT fixed

2003-03-25 Thread David Busby
the 'lo' in the command means "Loopback", its the 127.0.0.1 address. /B - Original Message - From: "Dana Holland" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, March 25, 2003 13:58 Subject: Re: DNS problems NOT fixed > I was a

Re: DNS problems NOT fixed

2003-03-25 Thread Dana Holland
I was able to get it working by adding the following commands to iptables. -A INPUT -i lo -j ACCEPT -A OUTPUT -o lo -j ACCEPT I found this solution while searching Usenet. However, since I'm still very new to RH and iptables, I'm a little nervous about entering these lines. Am I opening any se

Re: DNS problems NOT fixed

2003-03-24 Thread nate
Dana Holland said: > I'm at a complete loss here - why would I be getting this error message? check the DNS logs on the box, tune the log configuration on BIND if you need to, my log configuration for BIND 8 is below(seems similar to what BIND 9 uses): logging { channel chroot_default { file

DNS problems NOT fixed

2003-03-24 Thread Dana Holland
I only thought I had corrected my DNS problems. It seems that the dig command: dig @205.165.189.182 189.165.205.in-addr.arpa soa works fine if I'm on that box, but if you issue it from any other box, you get the following message: [EMAIL PROTECTED] /root]# dig @205.165.189.182 189.165.205.in-ad