DNS
Domain Name SystemBest for: Turning names into addresses
- example.com?, from You
- 203.0.113.10, from DNS server
Compare protocols
Best for: Turning names into addresses
Best for: Giving devices an address
DHCP gives your device its own network settings when it joins: an IP address, the router to use and which DNS server to ask. DNS then turns names like www.example.com into IP addresses whenever you open a site. DHCP runs once per join on UDP ports 67 and 68. DNS runs for every new name on port 53. Your home router usually does both.
Tick everything that is true for you.
Your pick shows here
Tick one or more lines and we weigh them for you.
| What differs | DNS | DHCP |
|---|---|---|
| Question it answers | What is the IP address of this name? | What address and settings should I use on this network? |
| When it runs | Every time a new name is needed | When a device joins, then to renew the lease |
| Ports | 53 (UDP, TCP for large answers) | 67 (server) and 68 (client), UDP |
| Messages | Query and response | Discover, Offer, Request, Ack (DORA) |
| Scope | Worldwide, a tree of servers | Only your local network |
| Without it | You must type IP addresses | You must set the IP, gateway and DNS by hand |
| Standard | RFC 1034, RFC 1035 | RFC 2131 |
Each page plays the real packets on a map, step by step, with every header explained.
Each line describes one of the two. Which one?
Question 1 of 7
Question it answers
What is the IP address of this name?
DHCP tells your device which DNS servers to use. Some routers also add each DHCP device's name into local DNS, so you can reach it by name.
Yes. Home routers usually run a DHCP server and a small DNS forwarder together. Offices often run them on separate servers.
The device gets no address, or picks a self-assigned one in 169.254.0.0/16 that cannot reach the internet.
You stay connected, and sites still work by IP address, but names stop loading. Browsers show errors like the server could not be found.