We currently have a DNS problem with our main domains aa.net.uk and aaisp.net.uk - this will cause a problem with various services that we run.
This was a simple planned change - it seems however we have been caught out by bind refusing to reload if one zone has one syntax error. Seems one of our customer zones had a typo in it which our tools had not managed to check and that caused it to refuse to load.
Unfortunately it took quite a few minutes to find what was wrong as this was nothing to do with the changes we actually made.
Most things are OK.
Both authorative serves are serving the aaisp.net.uk and aa.net.uk zones correctly.
There are still problems with the aaisp.net.uk domain - we're working on this.
VoIP is currently affected too, this is being worked on now.
We are running in to slightly unexpected errors as well, and working through them. Some things that we have not touched are not working, which kind of makes no sense.
Whilst most things are working, at least from customer lines, there was an issue which caught us out, but was way to far in to the process to sensibly back up. The top level delegation for aaisp.net.uk was going to a special DNS server, which meant when we moved everything it stopped working properly.
Some incoming VoIP is not working, we are still working on this.
Still lots of progress mopping up things. Mostly non customer affecting.
Just to clarify - you should be able to use aaisp.net.uk or aa.net.uk as they interchangable. However, right now, some places are having some issues seeing some of the aaisp.net.uk sub domains.
The preferred version is now aa.net.uk and we should be quoting that everywhere now.
Using aa.net.uk is also a work around for the issues some people are seeing right now, which are down to DNS caches.
At the moment we still have some services affected, these are: some incoming VoIP and accessing our services from outside our network (ie customer using DNS resolvers ither than ours)
We really think this should be sorted now - but monitoring carefully.
Mor details on http://aa.net.uk/news-2012-02-dns.html
We think all is OK now, so closing this incident.