Take the 2-minute tour ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

I have problem with configuring bind9 on debian (lenny) server. Generaly speaking everything is working ok but sometimes I get 404 on few domains (eg. 4stopnie.com but after few refreshes in browser site loads) or I can't validate site with validator.w3.org (error '500 Can't connect to 4stopnie.com:80 (Bad hostname '4stopnie.com')'). Domains were moved from other server. After moving I changed serial number in zone file.

$ttl 600
@       IN      SOA     ns.wpoznaniu.info. xxx.4stopnie.com. (

@       IN      NS      ns.wpoznaniu.info.
@       IN      A

www     IN      CNAME   @
share|improve this question

3 Answers 3

up vote 1 down vote accepted

It looks to me like a DNS caching problem, the upstream DNS server still knows about the old DNS and points towards there giving you the 404 problem.

Also the fact that it can't resolve sometimes is a bit dodgy, what I would do in your case is use the dig utility to check that all your new DNS servers are resolving the zone properly and with the same serial number

dig +search SOA DOMAINNAME
share|improve this answer

The .com nameservers know nothing about 4stopnie.com; check with your domain registrar.

dig +norec +auth -t ns 4stopnie.com a.gtld-servers.net
share|improve this answer

For addendum to what @mthenw wrote before, when bind9 is restarted, in /var/log/syslog there are such entries correspond to bind

Jan 17 16:49:24 r1688 named[30044]: network unreachable resolving 'ns2.wpoznaniu.info/A/IN': 2001:500:49::1#53
Jan 17 16:49:25 r1688 named[30044]: network unreachable resolving 'dns17.ovh.net/AAAA/IN': 2001:503:231d::2:30#53

of course dns17.ovh.net and ns2.wpoznaniu.info are reached by ping;

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.