Why do I get "ignoring out-of-zone data" when restarting BIND

Solution 1:

It looks like it's this line's fault:

ns1.mydns.com. IN A 111.111.111.111

You can't have a DNS record for some other zone (mydns.com) in your mydomain.com zones. That record belongs in the zone for mydns.com.

This won't cause some kind of critical failure or explosion, BIND's just saying that it's going to ignore this line.

======

Checking your listed DNS servers for the A record of mapvivo.info seems to indicate that they don't have any data at all for your zone (both return results like this):

[jrod@selene ~]$ dig mapvivo.info @sdns1.ovh.net

; <<>> DiG 9.6.1 <<>> mapvivo.info @sdns1.ovh.net
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 55728
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
;; WARNING: recursion requested but not available`

;; QUESTION SECTION:
;mapvivo.info.                  IN      A

;; Query time: 122 msec
;; SERVER: 213.251.188.140#53(213.251.188.140)
;; WHEN: Tue Mar 23 01:43:50 2010
;; MSG SIZE  rcvd: 30

Is 91.121.9.21 the authoritative nameserver for this domain? My nmap scans indicate that port 53 is closed for both TCP and UDP.

Solution 2:

There are typically two reasons that your domain works for some, but not everyone:

1. One server is returning cached results. There are plenty of servers that violates the TTL in various interesting ways. do a dig +trace and you avoid the caching.

2. Incorrect serial numbers. In this case your zone transfers will break, so your own server might use the correct zone file, but all the slaves uses the old zone file.