enforced delegation-only problem

[Bruce Esquibel]

Sorry if this is a trivial question but I'm kind of stumped for an answer.

We're an ISP in Chicago and run a couple nameservers (version 9.2.3) for the
customers to use.

One person was having a problem with www.findadeath.com not being able to
resolve, doing a dig +trace on it, the bottom line was:

;; Received 508 bytes from 192.5.5.241#53(f.root-servers.net) in 130 ms

findadeath.com.         172800  IN      NS      ns1.the-nextlevel.net.
findadeath.com.         172800  IN      NS      ns2.the-nextlevel.net.
;; Received 121 bytes from 192.54.112.30#53(H.GTLD-SERVERS.NET) in 198 ms

dig: Couldn't find server 'ns1.the-nextlevel.net': host/servname not known

Using dig again on both ns's did return the 67.19.121.91 and .92 A records.

Going through the named logs for a clue, this came up everytime (the ip is
address is differrent depending on which root was hit)...

Mar  9 14:49:54 e4500 named[198]: [ID 873579 news.notice] enforced
delegation-only for 'net' (ns1.the-nextlevel.net/A/IN) from 192.43.172.30#53

Taking out the "enforced delegation-only" from our servers did fix it but
does anyone know where the problem is, us, the-nextlevel.net or
findadeath.com?

Strikes me odd going back about a month in the logs that they
(the-nextlevel.net) are the only ".net" in there with the "enforced
delegation-only" turned on.

-bruce
bje at ripco.com