Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm trying to set up a fresh Ubuntu 10.04 as my web server but I'm having no joy at all - I can't access the domain via a browser (it times out) and I get no ping response except when I ping from the server itself. I'm a bit of a noob when it comes to this aspect of server config so please bear with me.

I installed 10.04 LTS then apache, mysql and php (all appear to be working fine). I've also installed Webmin and Virtualmin. I seem to be able to create the virtual hosts without any problem, and I can access the server using its IP and its name ( Bind9 came installed with the default distro, so I've not made any changes to it except those made automatically by Virtualmin/Webmin.

I'm sure it's something simple but I've been reading for ages and tweaking, to no avail.

Here's a pastebin of my bind config files:

The domain in question ( has its nameservers set to my server ( and the host's secondary nameserver (

Here's the hosts file for the domain:

root@server:/var/lib/bind# cat
$ttl 38400
@       IN      SOA (
                        38400 )
@       IN      NS
@       IN      NS        IN      A    IN      A    IN      A      IN      A      IN      A

(Obviously the server's real IP isn't

Any help would be really appreciated :)

share|improve this question
> I seem to be able to create the virtual hosts without any problem, and I can access the server using its IP and its name ( So then what exactly are you having trouble doing? ("No joy" = ?) – Systemic Jan 21 '12 at 17:54
I can't access the domain from a browser - it doesn't ping from any machine except the server itself, and browser requests just time out (both with and without the www). – melat0nin Jan 21 '12 at 18:02
Without knowing the particulars of the network, in general it might help to do nslookup or dig from inside and outside the network, to find where the resolution is failing. Also, to clarify troubleshooting, are ICMP packets blocked at the gateway? If so, disregard ping results. – Systemic Jan 21 '12 at 18:17
Does the name resolve correctly? Does it have a firewall in front of it? Is the browser you're on able to connect to its public address, or does it need to use a private address instead? – Shane Madden Jan 21 '12 at 22:08
up vote 1 down vote accepted

Turns out the listen-on IP in /etc/bind/named.conf.options was set to instead of the server's public IP. I changed that, restarted bind, and everything is working as expected now :)

Confusing that it should be configured only to listen to itself on installation (or that the file doesn't include a useful comment to explain what needs to be changed to expose bind to the outside world).

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.