Study Addressing, TCP/IP and SOHO Foundations for A+ Core 1 (220-1201)
Use IPv4 settings, DHCP, DNS, gateways, NAT, and small-office router behavior the way A+ Core 1 expects.
This is one of the highest-value A+ networking lessons because it turns a pile of IP facts into support logic. Core 1 wants you to know what a gateway, DNS server, DHCP scope, or private address actually does in a small network.
NAT: Network Address Translation, the process that lets many private devices share one public-facing address at the edge.
APIPA: Automatic private address in the
169.254.0.0/16range that often appears when DHCP configuration fails.
What CompTIA is really testing
The exam usually wants you to:
- recognize the role of each IPv4 setting
- understand private addressing and APIPA behavior
- interpret small-office router features such as DHCP, NAT, and VPN correctly
High-yield addressing map
| Item | What to remember |
|---|---|
| private IPv4 ranges | 10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16 |
| APIPA | 169.254.0.0/16, usually a DHCP failure clue |
| default gateway | where traffic leaves the local subnet |
| DNS server | resolves hostnames to IPs |
| DHCP | hands out IP configuration automatically |
Do not mix the roles
| If the issue is… | Think first about… |
|---|---|
| valid local IP, but no outside access | default gateway, router, or upstream path |
| hostname fails but IP works | DNS |
self-assigned 169.254.x.x address | DHCP |
| only one client fails while others work | client settings or local hardware first |
Small-office support reasoning
In SOHO questions, one router often handles many jobs:
- wireless access point
- DHCP service
- NAT at the internet edge
- basic firewall features
That means one misconfiguration can break several user-visible services at once.
What a SOHO router often combines
| Router role | Why it matters on Core 1 |
|---|---|
| wireless access point | client Wi-Fi association and security |
| DHCP service | automatic address assignment |
| NAT edge device | internet sharing for private hosts |
| basic firewall | common inbound and outbound filtering behavior |
That is why small-office troubleshooting can look broad at first. One misconfigured device may affect Wi-Fi, addressing, and internet access together.
Simple evidence example
1ipconfig /all
2ping 192.168.1.1
3nslookup example.com
What to notice:
ipconfig /allshows whether the IP settings look sane- a failed default-gateway ping can point lower than DNS
nslookuphelps separate name-resolution issues from broader connectivity issues
Harder scenario question
A desktop can ping its default gateway and can browse a site by direct IP, but every hostname lookup fails. Another answer choice suggests replacing the Ethernet cable first because the network feels “unstable.”
The stronger answer usually:
- keeps the failure in the name-resolution lane
- avoids overreacting to the fact that some connectivity still works
- treats DNS as the highest-yield first direction
What strong answers usually do
- classify whether the problem is local settings, gateway path, or name resolution
- read
169.254.x.xas a DHCP clue before chasing random cabling theories - keep gateway and DNS roles separate in their head
- use one working test to rule out entire fault classes quickly