Tough interview questions.

Fri Aug 13 15:21:14 PDT 2004

DNS: What's the difference between a zone and a domain?
DNS: How can you force a cache update in a secondary DNS server?
DNS: What's the difference between "refresh" and "retry" in the SOA record?
DNS: Do your glue records belong in the parent zone or not?
DNS: If your TTL value is 86400 and you need to change where your mail 
comes in, in the next hour, worldwide, how can you do it?
(I could keep going....)

Ethernet: What does a MAC address of 55:55:55:55:55:55 or aa:aa:aa:aa:aa:aa 
indicate?
Ethernet: How does a transceiver detect a collision, electrically?
Ethernet: Draw a block diagram of an Ethernet transceiver.  [10Base-5; 
lotsa laughs]

IP: Can an IP router forward a packet out the same interface where it came 
in?
IP: What happens next in this case?

802.11: What does WEP stand for?  (Hint: _not_ Wireless Encryption Protocol)

One of the easiest questions (I thought) on my "is this person a senior 
UNIX sysadmin" exam (21 questions, 7 in each of {DNS,IP,Email}, going from 
easy to hard; 14 is a passing score) is "1.1 What does TCP/IP stand for?" 
A surprising number of people don't get it right.

Lots more, but I don't want to give away -all- my secrets.