I setup quark to be a secondary NS for earlham.edu.
I added these lines to named.conf:
zone "28.159.IN-ADDR.ARPA" {
type slave;
file "159.28.zone";
allow-query { any; };
masters {
159.28.1.1;
};
};
zone "earlham.edu" {
type slave;
allow-query { any; };
file "earlham.edu.zone";
masters {
159.28.1.1;
};
};
I fixed a DNS issue related to the athena and bazaar clusters. The clusters were not able to resolve hostnames outside of the Earlham subnet due to an ACL preventing recursion. I added the two subnets (159.28.231.0/24 and 159.28.232.0/24) to the cs acl in named.conf on quark to solve the problem.
We've added the DHCP entries from hopper for athena and bazaar to quark's dhcpd.conf. I restarted dhcrelay on a0 and b0 to point to quark rather than hopper.
I just finished installing FreeBSD on Quarkprime (yes, I know it's 6:30 AM, but I've been on an odd sleep schedule lately). Anyways...it's installed but in a rather crippled state as I haven't done anything to it yet. You can ssh to it (159.28.230.9) and login as root, but that's about it.
Some things to note:
I enabled the RAID BIOS as Skylar mentioned before the install, and I didn't really know what kind of bootloader to install so I chose 'none', but it would not boot unelss I disabled the RAID BIOS. If I disabled it, it beeps whenever the machine boots. Is this ok?
Also, will we want to revert Qaurkprime and Image's IP address back to their original ones? It seems like we'd just have to edit a few files and everything would be ok.
I've configured the Cisco AGS to be a router between the admin, OS, and main CS subnets. Right now, it is sitting in the admin office and is just doing routing between the admin subnet and the main CS subnet, but it should be ready to do routing for the OS subnet and any other subnet we need to make.
When I get back, I plan to move the AGS into the 2nd floor wiring closet (I think there's room on the floor), because it is far too loud to work comfortably next to. We can then plug whatever ports we want to into the patch panel, and get the subnets wherever we need them.
Hopefully we can find the other Cisco 2600, so that we have two low-end Cisco routers for Networks. It seems a shame not to use the AGS in production.
Using 1158 out of 65536 bytes
!
! Last configuration change at 06:06:19 UTC Fri Jul 16 2004
! NVRAM config last updated at 06:08:18 UTC Fri Jul 16 2004
!
version 10.0
!
hostname admin-router
!
enable password x
!
ip classless
ip accounting-list 0.0.0.8 255.255.255.0
!
interface Ethernet0
ip address 159.28.230.136 255.255.255.0 secondary
ip address 159.28.230.135 255.255.255.0
ip accounting
no ip route-cache
no mop enabled
bridge-group 1
!
interface Ethernet1
ip address 159.28.135.254 255.255.255.0
ip accounting
no mop enabled
!
interface Ethernet2
ip address 159.28.136.1 255.255.255.0
ip accounting
no mop enabled
!
interface Ethernet3
no ip address
shutdown
!
interface Ethernet4
no ip address
shutdown
!
interface Ethernet5
no ip address
shutdown
!
interface Serial0
no ip address
shutdown
!
interface Serial1
no ip address
shutdown
!
ip name-server 159.28.230.3
ip name-server 159.28.230.91
ip route 0.0.0.0 0.0.0.0 159.28.230.1
access-list 1 permit 0.0.0.0 255.255.255.0
snmp-server community public RO
snmp-server access-list 1
!
bridge 1 protocol ieee
!
line con 0
line aux 0
line vty 0 4
password x
login
!
ntp clock-period 17180082
ntp server 159.28.230.2
end
In response to this message, I poked around on the FreeBSD lists, and found this message. It seems to address the problem that we are having with Apache running out of memory.
The message on the list archive suggested only giving multiple restart signals to Apache. To address that, I took half of our restart signals out, so Apache only restarts when rotating the error logs of a domain.
I've re-enabled spamass-milter on quark, and disabled SpamAssaassin checking in MailScanner. This will use the spamd daemon, and allow scanning of user_prefs files.