EDNS history (as you know) isn’t available in the portal, so it would taking digging into transfer agent
 logs to get the whole story, but while 40 minutes is on the long side, it’s not unheard of for
transfers to take a little longer occasionally. Do you happen to know if your server got a response back from us
when it sent that Notify?


On Jun 28, 2012, at 4:18 PM, Preyer, Johnny (CMG-Atlanta) wrote:

It took 40 minutes for 2800 to go live, and about 15 minutes for 2801 to
go live after than.  We use DNS notify to activate changes (we changed
another zone, fairfield-echo.com at the same time and it's change
propagated after 15 minutes or so).
---------------

Johnny,

(Sorry about that other email, finger slipped and I couldn’t catch it in time.)

This is the SOA for that zone, don’t know what it was before but this is what it is now:

  daytondailynews.com.	360	IN	SOA	ns1.cimedia.net. hostmaster.cimedia.com. 2012062801 10800 3600 604800 360

That’s a refresh interval of 3 hours, so we could theoretically wait that long before checking for an update. How long before 2800 did 2600 go live? Or do you do DNS Notify to activate a change?

By the way, the ns1.cimedia.net hostname in the SOA should probably be changed to be consistent with the NS records, as it is possible a resolver might actually go forward to that server as authoritative for that zone (which I assume you don’t want.)

--
Mark Hayes
Technical Support Engineer