Today I was presented with an interesting problem; someone changed two MX records in a DNS/BIND in a rush as a stopgap to yet another situation in two of our domains xxx1.pt and xxx2.pt.
As such precautions of diminishing the particular TTL of that record on advance were not observed.
The change was done while under the TTL of 2 weeks.
Interestingly enough, it was pointed to me the Google DNS public servers answers are not all the same.
Testing with 126.96.36.199 still resolves it with with the old address with the odd answer returning the new address.
The SOA serial was updated for sure, as by local procedures/configuration it is automatically updated to prevent people forgetting to do that.
So I was asked why the odd answer, and if something could be done on BIND´s side.
There are also a particular urgency on solving the cache problem on Google side, for reasons not pertinent to this question.
What can I do at BIND side?