Updated to Dadmin 1.28, then no webpages anymore

harro

Verified User
Joined
Oct 15, 2005
Messages
177
Hi all,

last night I pushed the "update directadmin" button, to upgrade from version 1.27.1 (?) to 1.28. This afternoon I get a call that my websites are not online anymore!! When I go to any of the websites hosted on my server I get a "Server not found" error.

So far I never had any problems with DirectAdmin updates, so I didn't think of checking the websites afterwards. More so because email (pop, smtp, IMAP) still works fine.

Apart from that SSH works fine, Apache works as well when I use the direct IP and I can get into the control panel like that too. There are no errors (other than the usual ones on certificate server name) that I can find.

I restarted httpd, named and DirectAdmin (in that order) without any change.

Does anyone have thoughts what the problem could be? I am at a bit of a loss here... If you want to check you could try www.sengerema.nl, for example.

Thank you for your ideas!

Harro

[edit]
**** update ****

On a hunch I checked DNSreport.com for sengerema.nl and got the following reply:
Code:
A timeout occurred getting the NS records from your nameservers! None of your nameservers responded fast enough. They are probably down or unreachable.

And I found a log entry in my errortaskq.log file:
Code:
2006:09:27-16:02:02: service named wasn't running, starting it

So there is a problem with my named, which isn't solved by restarting it (according to the service status and DA services panel the named is running at the moment!)

Any ideas how this could have happened after an update of DirectAdmin to v.1.28 ?
[/edit]
 
Last edited:
Thanks for the reaction Sullise.

I bumped into another post from a while back that suggested that the firewall was blocking website by name (not by IP).

This sounds a but strange, but if the firewall is blocking access to my DNS server, then it is understandable that no website can be found.

The post was:
http://www.directadmin.com/forum/showthread.php?s=&threadid=616

I will have to find out how to disable the apf firewall and see whether this solves my problem. Still it remains odd how this change suddenly occurred after a year of no problems.

Possibly still related to the upgrade to DA 1.28, or maybe a freak coincidence?

Thoughts are still appreciated!

Harro

[edit]
After switching off the APF firewall, the websites were accessible again. So in the end it was the FIREWALL that was blocking everything.

Why would the firewall block a DNS service?

The search continues...
[/edit]
 
Last edited:
Back
Top