Heya, folks. Today I was doing some more rennovations on the infrastructure:
- Switched apache to nginx+fastcgi to further reduce load and latency - Revamped some DNS and configured some proxies to support any future move of the mail services to another machine In the process, I had changed our DNS entry for www-0.synhak.org from an A record to be a CNAME that points at the AWS public dns, which resolves to the internet-facing IP from the internet, and the internal AWS IP that doesn't cost us money to use from inside our cloud. The entry for mail.synhak.org (the only server in our MX record) was set to be an A record alias for www-0.synhak.org. For some reason I had simply assumed changing the www-0 record to a CNAME would also change the alias to a CNAME. It didn't, so mail was completely gone for a few hours \o/ Since the hostname mail.synhak.org was for all intents and purposes gone from the face of the internet, most mail servers would simply reply with an immediate "undelivered mail returned to sender" bounce. If you tried to send mail between around 8 PM and now, please check if you need to resend anything. The good news, is now we know what else to check next time, there are more knobs to frob to finetune performance, and synhak is just a little bit more future-proof. I'll be fine tuning performance this week as more data is recorded along with working on the next stage of future proofing: packaging up Phong for easy re-use by other spaces and improving document generation from our latex sources. _______________________________________________ Discuss mailing list [email protected] http://synhak.org/mailman/listinfo/discuss
