Hui WANG's Blog

After transferring my domain from byethost to my new web host, I got a 500 internal server error when trying to browser my site. The problem was resolved “itself” after almost 48 hours during which none of my efforts have taken effect. After this pain,  there are some gains. Here is the cause I’ve figured out.

What is a 500 Internal Server Error ?

The 500 Internal Server Error is a very general HTTP status code that means something has gone wrong on the web site’s server but the server could not be more specific on what the exact problem is. One thing is certain that the problem is not with your PC or Internet connection but instead is a problem with the web site’s server. Read the rest of this entry »

I have installed bind9 in ubuntu 9.04. This error arises when I try to restart bind9 after some configurations.

To find out what is preventing bind9 from getting started,  your can use this command

named -g -p 53

18-Aug-2009 22:43:35.631 starting BIND 9.5.1-P2 -g -p 53
18-Aug-2009 22:43:35.632 found 1 CPU, using 1 worker thread
18-Aug-2009 22:43:35.632 using up to 4096 sockets
18-Aug-2009 22:43:35.642 loading configuration from ‘/etc/bind/named.conf’
18-Aug-2009 22:43:35.642 /etc/bind/named.conf.options:17: expected IP address near ‘{‘

18-Aug-2009 22:43:35.643 loading configuration: unexpected token
18-Aug-2009 22:43:35.643 exiting (due to fatal error)

Everything becomes fine after I change the expected IP to one contained /etc/resolv.conf.

Good luck.