Another Intermittent Issue

[Justin]

This one has me and my colleages stumped...

We host our own DNS server across multiple domains. NS.JRCORPS.COM, 
NS2.JRCORPS.COM in this case. It manages roughly 30 domains including:
www.jrcorps.com
www.dorothyannbakery.com
www.artattack.to

If you do a dig on those names, on a normal day, you will get this 
(today's not a normal day so I included the IP statement to get it to 
work):

; <<>> DiG 9.2.2-P3 <<>> jrcorps.com @69.54.36.67
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 31372
;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 0

;; QUESTION SECTION:
;jrcorps.com.                   IN      A

;; ANSWER SECTION:
jrcorps.com.            86400   IN      A       69.54.36.67

;; AUTHORITY SECTION:
jrcorps.com.            86400   IN      NS      ns.jrcorps.com.
jrcorps.com.            86400   IN      NS      ns2.jrcorps.com.

;; Query time: 26 msec
;; SERVER: 69.54.36.67#53(69.54.36.67)
;; WHEN: Fri Aug  6 10:20:35 2004
;; MSG SIZE  rcvd: 80

But, and the weird part about it is that it's intermittent, is that 
there will be times when we get a SERVFAIL response. Running a trace we 
get:

; <<>> DiG 9.2.2-P3 <<>> jrcorps.com +trace
;; global options:  printcmd
.                       504211  IN      NS      L.ROOT-SERVERS.NET.
.                       504211  IN      NS      M.ROOT-SERVERS.NET.
.                       504211  IN      NS      A.ROOT-SERVERS.NET.
.                       504211  IN      NS      B.ROOT-SERVERS.NET.
.                       504211  IN      NS      C.ROOT-SERVERS.NET.
.                       504211  IN      NS      D.ROOT-SERVERS.NET.
.                       504211  IN      NS      E.ROOT-SERVERS.NET.
.                       504211  IN      NS      F.ROOT-SERVERS.NET.
.                       504211  IN      NS      G.ROOT-SERVERS.NET.
.                       504211  IN      NS      H.ROOT-SERVERS.NET.
.                       504211  IN      NS      I.ROOT-SERVERS.NET.
.                       504211  IN      NS      J.ROOT-SERVERS.NET.
.                       504211  IN      NS      K.ROOT-SERVERS.NET.
;; Received 436 bytes from 128.101.101.101#53(128.101.101.101) in 2 ms

com.                    172800  IN      NS      A.GTLD-SERVERS.NET.
com.                    172800  IN      NS      G.GTLD-SERVERS.NET.
com.                    172800  IN      NS      H.GTLD-SERVERS.NET.
com.                    172800  IN      NS      C.GTLD-SERVERS.NET.
com.                    172800  IN      NS      I.GTLD-SERVERS.NET.
com.                    172800  IN      NS      B.GTLD-SERVERS.NET.
com.                    172800  IN      NS      D.GTLD-SERVERS.NET.
com.                    172800  IN      NS      L.GTLD-SERVERS.NET.
com.                    172800  IN      NS      F.GTLD-SERVERS.NET.
com.                    172800  IN      NS      J.GTLD-SERVERS.NET.
com.                    172800  IN      NS      K.GTLD-SERVERS.NET.
com.                    172800  IN      NS      E.GTLD-SERVERS.NET.
com.                    172800  IN      NS      M.GTLD-SERVERS.NET.
;; Received 461 bytes from 198.32.64.12#53(L.ROOT-SERVERS.NET) in 85 ms

jrcorps.com.            172800  IN      NS      ns.jrcorps.com.
jrcorps.com.            172800  IN      NS      ns2.jrcorps.com.
;; Received 96 bytes from 192.5.6.30#53(A.GTLD-SERVERS.NET) in 65 ms

dig: Couldn't find server 'ns.jrcorps.com': Name or service not known

DNSreport.com reports that nothing is wrong.

Strangely, things running on our .net name servers seem to be fine.... 
Perhaps the solution is to just make the name servers for the domains 
have both .com and .net name servers, but I have a feeling that there is 
a better solution than that.

Any help you can provide, would be much appreciated Mr. Dns

-Justin Gehring