Chapters0/30 ▾
Chapter 3 · Lesson 3 of 5
DNS and DHCP: transports, records, relays and reservations
1 min read
DNS uses UDP 53 for ordinary lookups but switches to TCP 53 for zone transfers and for any answer too large for one datagram (RFC 7766). An access list that allows only UDP 53 lets users resolve names while a secondary server fails to pull its zone.
Encrypted DNS has its own transports: DNS over TLS on TCP 853, and DNS over HTTPS on TCP 443, which blends into normal web traffic and slips past port-53 filtering. DNSSEC signs records to prove they are genuine but does not encrypt them.
Record types to know here: SRV returns the host and port for a named service, with priority and weight; PTR maps an address back to a name; SOA holds the zone's primary server and timers; TXT holds free text such as policy strings.
DHCP runs on UDP because the client has no address yet: the client uses port 68 and the server port 67, so a DISCOVER goes from 68 to 67 (DHCPv6 uses 546 and 547). Routers do not forward that broadcast, so a remote VLAN needs a relay, or IP helper, on its gateway interface.
To give one printer the same address while keeping it on DHCP, create a reservation tied to its MAC address; an exclusion only removes an address from the pool.
Check yourself
1. A secondary DNS server cannot pull a zone from the primary, even though ordinary name lookups through the same firewall succeed. The access list permits UDP 53 only. What must be added?
2. Client software must automatically discover which host and which port provide a particular service in a domain, without either value being configured by hand. Which DNS record type carries that information?
Facts checked 2026-11-16 · Sources: CompTIA Network+ certification overview, IANA Service Name and Transport Protocol Port Number Registry, RFC 7766: DNS Transport over TCP
CompTIA Network+ cheat sheet: every key fact on one page →