Knowledgebase
IPTABLES Gone Crazy
| Posted by aodat2, 04-01-2009, 10:27 PM | | I'm not too sure what happened in between or etc but my client started complaining that his server cannot resolve the domains hosted there. So naturally, I went to check and the funny thing is that after checking, I found out that PORT 53 has been blocked and thus I stopped the IPTABLES and everything went back to normal.
The funniest thing is that everytime IPTABLES restarted, it would give the same error again. The domains there will not resolve. It seems that even after trying to add a rule to IPTABLES for PORT 53 to be unblocked, it would still do the same thing.
Does anyone actually know or have encountered this problem before? My client's server is running on CentOS and DirectAdmin. I've asked DA about this problem and they just told me to stop the IPTABLES which I do not think is a good solution.
If anyone could help, it would be very much appreciated. I have found no errors on IPTABLES, the config and etc are all the DEFAULT settings and has not been changed. Plus, APF rules did state that port 53 be opened already.
Please do help out if you have encountered this problem before. Thanks a lot!
|
| Posted by macooper, 04-02-2009, 07:29 AM | | If your using APF, you should stop and start APF with the appropriate command, typically:
service apf stop
service apf start
This is based on a typical redhat system, so is also the same for centos. Some other distrubutions don't have the service command, in which case you'll need to call the start / stop scripts directly.
The thing is, if your using the command :
service iptables stop;
service iptables start;
tehn that is probably your problem. APF manipulates iptables directly. The iptables rc script when called will restore whatever default settings have been saved on the server. You will also need to remove iptables from being run at system boot.
HTH.
|
| Posted by ServerManagement, 04-02-2009, 08:44 AM | | If you have a firewall installed like APF, you should be doing your configuration in APF, not iptables directly. You should check the APF configuration and logs to make sure it is loading properly, that's a common problem that is missed.
|
|
 Add to Favourites
 Print this Article
|
Also Read
