-
I just realized how old these name servers are
I guess I’ve had them around for a while… Maybe I should clean these up… cjac@ns1:~$ ls /lib/modules/ 2.6.18-4-xen-amd64colliertech.fw+0 2.6.32-5-amd64 2.6.24-19-xen 3.2.0-4-amd64 cjac@ns2:~$ ls /lib/modules/ 2.6.18-4-xen-amd64colliertech.fw+0 2.6.24-19-xen 2.6.32-5-amd64 cjac@ns2:~$ sudo rsync -aue ssh ns1:/lib/modules/`uname -r` /lib/modules I remember editing the .config file for that kernel and building it on my first ever 64-bit system back…
-
Setting up a cluster
So… I guess at this point, the hosts on colliertech.org could be considered a cluster. We have all of the services you would expect from a real ISP running on the network at this point. I think. I’m learning more and more as I go along. I set up autofs for the first time this…
-
Bind configuration cleaned up
Okay. That wasn’t so bad. Now I need to find out whether people are querying colliertech.org or ns1.colliertech.org and ns2.colliertech.org. If colliertech.org is still getting the brunt of the requests, I need to find out how I misconfigured bind and then fix it. If the requests have started flowing to ns1.colliertech.org (66.152.65.10) and ns2.colliertech.org (66.152.65.11)…
-
DNS changes
I’m working on the family’s servers over vacation. I’m moving a bunch of the bandwidth-consuming bits off of the server on the T1. One of the services I’m moving to its own VM is bind9. I figure it should live on its own box that does only DNS-ish stuff. That way I can make sure…
-
currently 153 release critical bugs in etch. Get to it.
http://lists.debian.org/debian-devel-announce/2006/12/msg00004.html http://bts.turmzimmer.net/details.php?bydist=etch