Data last gathered 7/30/2009 by jak

Domain Controllers

• CHEKOV
• SULU

General OIT test server:

• WOLFTEST00.oit.ncsu.edu

Test CRON:

• WTEST-CRON00

The wolftest.ad.ncsu.edu is the test domain used by all groups on campus for testing services before deploying them into WolfTech.

These documents provide information about how OIT is using WolfTest, and docuements ongoing tests and test results.

Neal from SnC asked me to take a look at some software he's thinking about using for intrusion detection.

It's called "OSSec" and you'll find more about it at http://www.ossec.net/

He's also talking about setting up a syslog server that we can use to collect authentication traps and possibly other information.

Here's a summary of where I think we stand with differences between the ACSAD domain controllers serving DNS and the QIP "NCSU-Legacy" DNS

Matched 926 of 1013 records (2 SOA, 5 NS records and 10 others can never match).
830 of 901 total matched 'A' records.
89 of 360 total matched 'SRV' records.

When I tried to do reverse (IP to name) lookups against ns60, ir looka like our PTR records were a complete mess, but I haven't dived in to gather specifics.

Kevin and I figured this out last week, but I hadn't found the time to post it until now.

We've found another wrinkle in the ACSAD DNS migration to QIP.  The existing ACSAD DNS is configured for "dynamic" registration for both DHCP and DNS services.  When a new host comes up, it's name (as set in the Windows control panel) is automatically registered in DNS.  QIP uses "static" registration, in that you must key in DNS info to get the name server to acknoledge you.

Links to important support information

Dell DRAC/ERA documents http://support.dell.com/support/edocs/software/smdrac3/

We had the next to the last "File System Team" meeting this morning.  I wasn't taking good notes, so the particulars I record here may not be correct.  Eric is doing our "official" write-up, so anything differenet between that write up and this one means that this one is in error.

A place to put all the info about the sysnews web site and it's configuration

Not a lot of new stuff on the agenda

• We need servers in ACSAD to switch to use ns60/ns61 for DNS.  Plans are to run ISO servers while the CAB deliberates applying GPO to ship ns60/ns61 domain-wide.

From 6/22/2009

• Terminal Server CALS in WolfTech
• Migration of 4 x OIT groups in WolfTech to WolfTech

Action Items from earlier meetings

Eric and I have just confirmed that the issues previously thought to be DNS problems using ns60 were in fact a firewall problem.

Eric is going to identify a bunch of test vms and provisioning servers, and I'm going to look for admin vms and servers at Monday's WAL meeting to set to use ns60 using a GPO.  The idea is that we eat our own dogfood while the CAB deliberates on pushing ns60 out wholesale to all ACSAD workstations.