You're not alone — networking has mutated while still pretending it's the same. Here's a compact survival guide for modern Linux networking, especially with Red Hat–style systems like Fedora, RHEL, and Rocky:
|
Tool |
Purpose |
Notes |
|---|
Short answer: If Camelot is plugged into Ethernet, that should be the default — and you can safely ignore Wi-Fi unless you need it for something.
But let's go through what actually matters, so you can decide if you care.
NetworkManager will:
(short, memorable, and much less swear-inducing)
10.20.30.1 → camelot
10.20.30.2 → frodo
No new networks.
No mystery subnets.
No auto-assigned 10.42.x.x.
No analysis.
No surprises.
Just two machines on one clean wired LAN.
✅ FINAL, CLEAN CONFIG — TEMPORARY FIRST (to confirm it works)
🌐 Networking in Windows (10/11)
A wildcard DNS record in a zone file looks similar to this example:
*.example.com. 3600 IN MX 10 host1.example.com.
This wildcard DNS record will cause DNS lookups on domain names ending in example.com that do not exist to have MX records synthesized for them. So, a lookup for the MX record for somerandomname.example.com would return an MX record pointing to host1.example.com.