odd dig results for fqdn

[M. Meadows]

: dig mta.news.getaroomgetadeal.com +noall +answer @4.2.2.1
; <<>> DiG 9.3.6-P1-RedHat-9.3.6-4.P1.el5_4.2 <<>> mta.news.getaroomgetadeal.com +noall +answer @4.2.2.1
;; global options:  printcmd

 
: dig news.getaroomgetadeal.com +nssearch @4.2.2.1
SOA ns1.exacttarget.com. hostmaster.exacttarget.com. 2011012501 7200 3600 1209600 3600 from server ns1.exacttarget.com in 3 ms.
SOA ns1.exacttarget.com. hostmaster.exacttarget.com. 2011012501 7200 3600 1209600 3600 from server ns2.exacttarget.com in 95 ms.

 
: dig mta.news.getaroomgetadeal.com +noall +answer @4.2.2.1
; <<>> DiG 9.3.6-P1-RedHat-9.3.6-4.P1.el5_4.2 <<>> mta.news.getaroomgetadeal.com +noall +answer @4.2.2.1
;; global options:  printcmd
mta.news.getaroomgetadeal.com. 3600 IN  A       68.232.198.41

 
Then wait a while (less than the 3600 TTL) and the dig for mta.news.getaroomgetadeal.com starts failing again. Repeat the dig of the domain with +nssearch and it works again.
 
 
Haven't seen this behavior before. Sort of screwy isn't it? Any thoughts on why this might happen?
 
Thanks,
Martin Meadows
  		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/bind-users/attachments/20110125/51f47d87/attachment.html>