> ns1.cayne.com is the hostname in question.

dig @a.gtld-servers.net cayne.com

;; AUTHORITY SECTION:
cayne.com. 2D IN NS ns1.cayne.com.
cayne.com. 2D IN NS ns2.cayne.com.
;; ADDITIONAL SECTION:
ns1.cayne.com. 2D IN A 69.93.59.34
ns2.cayne.com. 2D IN A 69.93.59.35


So thats servers that should provide an authoritative answer.

dig @69.93.59.34 ns1.cayne.com
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 6
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

It authoritatively responds with an NXDOMAIN, it doesn't know have an A
record for ns1.cayne.com

Same with the other server.

dig @69.93.59.35 ns1.cayne.com
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 6
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0



You probably should put records for ns1.cayne.com and ns2.cayne.com in
your zone as the .com GTLD servers think they are authoritative for that
zone yet they lack the A records.


sam