I am a big fan of the Okidata page printers, and so I'd recommend one of their color page printers. These aren't laser printers, although they use the familiar image drum, toner, and fuser print technology. Unlike the laser printers (where the image is laid down by scanning a laser across the image drum), the Oki printers use a fixed array of LEDs to lay down the image. This eliminates the need for the optical path and high-speed, high-precision moving parts that often fail in laser printers. The printers also use a system where the toner cartridge, image drum, and transfer belts are separate, user-replacable items for each color.
There are three models worth considering for home or home-office use:
1) The C3400n is the low-end model, and depends on its drivers for protocol support, so I don't recommend using it unless you know you're an all-Windows shop.
2) The C3600n is the mid-range networkd printer, and supports all of the popular network printing protocols (HP, Unix, Apple) and languages (PCL5, PostScript3), so any computer that's likely to be running today can print to it, and you're likely to be able to keep using it long into the future regardless of driver support.
3) The C5650n is a workgroup printer adds duplexing and higher print speeds to the features of the C3600n.
I have a C5300n (basically a predecessor to the C5650n) that's been powered on 24/7 since I got it some 6 or 7 years ago. It has a duplexer and additional RAM, and I have had no mechanical problems, and have done no maintenance to it except replace consumables. Almost all of the likely wear parts are user-replacable: in addition to toner cartridges, you can get replacement image drums and fuser belts, so I expect to be able to keep the printer running for another 7+ years.
According to the briefing, ActiveDirectory uses DNS "like a database" to resolve the names of any Active Directory objects. Dynamic DNS is required, since any changes to the ActiveDirectory name space require updates to the DNS data. We were told that ActiveDirectory wouldn't work without it, and the implication was that Active Directory stored more than just machine names and IP addresses in there.
I asked why use DNS for this, when LDAP (for example) already exists specifically for managing directory information. I got an oblique answer that Active Directory can import information from an LDAP server, but can't update one. Probably the marketdroid didn't understand my question, or know the answer.
I also asked if a RFC-compliant non-Windows Dynamic DNS implementation would work with Win2k and Active Directory, and was told that it would, but that Microsoft very strongly recommended using only their DDNS (anything else is unsupported).
My overall impression is that they're following the RFC's for DDNS, but filling the DNS database up with a lot of records that don't have anything to do with machine-name to IP-address mapping.