DNS, DHCP & NAT
How a machine gets an address and turns a name into one.
0 of 23 answered
Start here
A record or CNAME
Foundation
- Not triedA record or CNAMEFoundation
- Not triedAddresses that never leaveFoundation
- Not triedBefore the resolver is askedFoundation
- Not triedHow a machine gets an addressFoundation
- Not triedSeveral addresses for one nameFoundation
- Not triedWhat a name lookup returnsFoundation
- Not triedWhat happens before the request is sentFoundation
- Not triedWhat the TTL controlsFoundation
- Not triedWhen a lease runs outFoundation
- Not triedWhere mail goesFoundation
- Not triedCaching an answer that does not existCore
- Not triedThe clients that see bothpart of Half the campus reaches the old serverCore
- Not triedThe DNS change that some people cannot seeCore
- Not triedThe phrase DNS propagationCore
- Not triedThe record was added and clients still say it does not existCore
- Not triedWhat NAT changes in a packetCore
- Not triedWhere clients get their resolverspart of Half the campus reaches the old serverCore
- Not triedWho actually knows the answerCore
- Not triedWhy DNS uses UDPCore
- Not triedWhy some clients lagpart of Half the campus reaches the old serverCore
- Not triedA DHCP server on another subnetChallenge
- Not triedBalancing load with DNS aloneChallenge
- Not triedRunning out of portsChallenge