Bind Mailing List wrote:

> We use bind 9.3.0 on Solaris 8. For unknown reason we can't resolv the
> ns2.lamatapedia.com. Other DNS seem to answer this.


ns2.lamatapedia.com is not known to the nameservers for lamatapedia.com.

% dig lamatapedia.com. ns +short
ns67.worldnic.com.
ns68.worldnic.com.

% dig @ns67.worldnic.com. ns2.lamatapedia.com. any +norec

; <<>> DiG 9.2.3 <<>> @ns67.worldnic.com. ns2.lamatapedia.com. any +norec
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 3462
;; flags: qr aa; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;ns2.lamatapedia.com. IN ANY

;; AUTHORITY SECTION:
lamatapedia.com. 7200 IN SOA NS67.WORLDNIC.com. namehost.WORLDNIC.com. 2004062800 10800 3600 604800 7200

Same with ns68.worldnic.com.

There does seem to be a glue record for ns2.lamatapedia.com in the .com
zone, which BIND 9.3.0 might ignore.

--
Ronan Flood
working for but not speaking for
Network Services, University of London Computer Centre
(which means: don't bother ULCC if I've said something you don't like)