ooops. [news for unchi.org]
Aug. 26th, 2004 04:42 pm![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
topazShort version: we haven't been sending mail at all today and may even have been eating some mailing list mail, sigh. I can't fix it until I get home tonight.
The geeky bits: this morning the nameserver at home went belly-up. (In related news, never install a UPS where a two-year-old can get to it!) This doesn't directly affect anyone else, it's just our internal nameserver for Ellen's and my machines.
So before I left for work I installed djbdns on the machine that's going to replace anderson.unchi.org Real Soon Now. I got a basic install of tinydns & dnscache running, set up a basic zone. Reverse DNS wasn't working for internal machines but I figured I could fix that later, since forward DNS was working.
However, once I got to work I found I couldn't ssh into the new server. This was possible before the nameservice change, and the connection hangs for about a minute before being refused, so I suspect the lack of reverse DNS is what's stopping it.
Moreover, when I set up the internal DNS zone this morning I neglected to include an MX record for "unchi.org". So internal machines which connect to our mail server and try to send mail from "@unchi.org" addresses get rejected for not coming from a valid domain. The prime victim on this one is Ecartis, our mailing list manager.
Anyway, because I can't log in to the box to fix it, I won't be able to get back to it 'till this evening. More later....
The geeky bits: this morning the nameserver at home went belly-up. (In related news, never install a UPS where a two-year-old can get to it!) This doesn't directly affect anyone else, it's just our internal nameserver for Ellen's and my machines.
So before I left for work I installed djbdns on the machine that's going to replace anderson.unchi.org Real Soon Now. I got a basic install of tinydns & dnscache running, set up a basic zone. Reverse DNS wasn't working for internal machines but I figured I could fix that later, since forward DNS was working.
However, once I got to work I found I couldn't ssh into the new server. This was possible before the nameservice change, and the connection hangs for about a minute before being refused, so I suspect the lack of reverse DNS is what's stopping it.
Moreover, when I set up the internal DNS zone this morning I neglected to include an MX record for "unchi.org". So internal machines which connect to our mail server and try to send mail from "@unchi.org" addresses get rejected for not coming from a valid domain. The prime victim on this one is Ecartis, our mailing list manager.
Anyway, because I can't log in to the box to fix it, I won't be able to get back to it 'till this evening. More later....
