I recently renamed my internal LAN domain name. For some crazy reason I'd thought .int was not a public TLD and didn't check at all before using that before the last time I renamed my internal LAN. I had no issues for several years, but I felt with the holidays it was time to move away from this invalid domain internally to something valid.
I've been waiting to add some features to ipquail.com for a while, but the way in which I was handling API endpoints at the moment needed to change before I could accommodate anything fancier -- at the moment I was using simple Server Side Includes ("SSI" in 90's Apache web server terminology) and some mime-type modifications to fake API endpoints. This needed to change.
While I've had most of my services IPv6 enabled for quite a while, I have not set up monitoring of those services over IPv6 yet. This blog post is a summary of my experiences IPv6 enabling my nagios setup.
On Sunday, September 13th, 2015 during the wee hours of the morning a change was made by AS7122 which silenced four Manitoban ASNs, and removed several other routes from the global routing table. Shortly after the start of their 1AM maintenance window AS7122 enabled BGP atomic aggregate on 205.200.0.0/16 and 207.161.0.0/16, causing AS21876, AS23001, AS32433, and AS54937 to disappear from the global routing table.
