Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
1
10. DNS maps of human-friendly domain names to IP addresses, using a hierarchy of DNS servers
that each have their own “zone of authority”. A client will always send an initial DNS query using
UDP Protocol over Port 53, and if it does not get a response within a certain time it will
retransmit the query using TCP.
11. (b) /etc/hosts has a list of IP addresses and aliases. (a) /etc/HOSTNAME only has the “proper”
(canonical) hostname, which will also be in /etc/hosts if we are not using DNS. (c)
/etc/resolv.conf identifies the nameservers that provide a DNS lookup service (d) /var/hostlist is
not a standard configuration file.
12. DNS CNAME record defines an “alias” or alternative name for a host which means one IP address
can be associated with more than one name.
2
22. Submission port is intended to be used from client to initial server, using SMTP protocol, port
587. Transfer is intended to be server to server (relay) using SMTP protocol, port 25. This allows
administrators to run two distinct services configured optimally for each purpose rather than a
single MTA service that has to make allowances for different types of use. Able to require
encryption and SMTP authentication for port 587 sessions; port 25 sessions can Prefer but
CANNOT Require encryption.
23. Packet filters allow or deny access to services based on per-packet network and transport layer
header information such as source and destination address or port, packet type, direction,
sequence, etc. (bonus: “stateful” firewalls have “circuit-level” rules pertaining to connections
rather than individual packets). Packet sniffers intercept traffic between the source and
destination and show the content. Packet filters are used to create firewalls, packet sniffers are
used to analyse traffic.
3
30. Changing passwords locks out someone who guessed, increasing security. However, new
passwords are hard to remember so users tend to write them down or change in a predictable
pattern. This effect is even worse when administrators force users to choose strong passwords,
composed of a mix of uppercase, lowercase, numeric and special characters.
31. Root access means anything can be done, which magnifies the effect of mistakes. Some feel that
forcing us to type sudo is a way to consciously reinforce this, and we can be better sysadmins by
learning more about sudo configuration options if and when we get tired of it. Others feel that
having the root password is fine and we can learn from our (potentially disastrous) mistakes. An
easy way to remind users when they have a root shell is to change the colour of the prompt
using ASCII terminal escape codes.
32. [1] Look for what you recognise (in the logfiles, starting at the end) [2] Always keep a working
configuration as backup [3] Do one thing at a time, and then test [4] Do the simplest thing first
33. Problems with services? Check ports, permissions, and paths; typo errors cause problems with
parsing scripts and configuration files.
34. Lots of services like to write their process ID to a file in /var/run so the best thing to do is give it
permissions like /tmp [see question 6]