ns1 & ns2.vf.net.nz (aka ns1 & ns2.ihug.net.nz) are a cluster of 4 machines, and which ones you get depends on which site your queries are routed to. BIND should refuse to load zonefiles which have rewound serial numbers, so that limits the possibilities. It's possible the nameserver VM's have been rolled back to some snapshot state, though that on its own doesn't explain why they're not receiving updates at least every few minutes. (Anyone at Vodafone reading this feel free to call me if you need a brieding on how the data is extracted from TP2 and pushed to the nameservers.) -Martin On Mon, 14 Sep 2015, Justin Lewis - ResponseMedia wrote:

Is anyone else seeing ns1.ihug.net.nz and ns2.ihug.net.nz reverting to older zone files since around lunch time today? Looking like the zone serial is back to "2015082705" should be at least "20150905XX"

Have a customer whose entire zone file has been reverted to an old record that's over 3 weeks old.

Customer portal is showing the new zone file though.