3 ms·
DNS, Avahi are super usefuler.
by RiverCrochet 7mo ago
DNS, Avahi are super usefuler.
- userbinator 7mo agoGood luck when you're trying to troubleshoot and DNS not working is one of the symptoms. 8.8.8.8 and 4.2.2.x are easy to remember.
- flexagoon 7mo agoSo is 2620:fe::fe for Quad9 DNS
- miyuru 7mo agoDNS should be auto configured and work with multiple redundancy these days. If it breaks, so much that you cannot do a dig, you need to re think your network.
- gzread 7mo agoOh yes, that's really convenient for home users. "Install this thing on several computers and keep it in sync or you're not qualified to have a network"
- miyuru 7mo agoreally home users who mess with DNS settings? Lot of people here are living in a bubble.
- vel0city 7mo agoHome users would ideally be served by things like mDNS and LLMNR, which should just work in the background. If I want to connect to the thermostat I should be able to just go to http://honeywell-thermostat and have it work. If I want to connect to the printer it should just be ipp://brother and I shouldn't even need to have a DNS server.
- M95D 7mo agoAnd if DNS fails, I have to use a serial console to get into my router and fix it, because I can't remember what address to type in ssh?
- vel0city 7mo agoYour interface has a default gateway configured for it, doesn't it? Isn't that default gateway the router? NDP should show the local routers through router advertisements. There is also LLDP to help find such devices. LLMNR/mDNS provides DNS services even without a centralized nameserver (hence the whole "I shouldn't even need to have a DNS server"). So much out there other than just memorizing numbers. I've been working with IPv6 for nearly 20 years and I've never had an issue of "what was the IP address of the local router", because there's so many ways to find devices. Even then nobody is stopping you from giving them memorable IP addresses. Giving your local router a link-local address of fe80::1 is perfectly valid. Or if you're needing larger networking than just link-local and have memorable addresses use ULAs and have the router on network one be fd00:1::1, the router on network two be fd00:2::1, the router on network three be fd00:3::1, etc. Is fe80::1 or fd00:1::1 really that much harder to memorize than 192.168.0.1 or 192.168.1.1 or 10.0.0.1, if you're really super gung-ho about memorizing numbers?
- M95D 6mo ago> Giving your local router a link-local address of fe80::1 is perfectly valid. You're right. That would work.
- whatevaa 7mo agoMy DNS "server" is a router which can "add" static entries. Easy with static addresses, won't work with dynamic addresses. What redundancy, multiple servers? Do you think everybody runs dedicated homelabs to access a raspberry pi.
- vel0city 7mo ago> My DNS "server" is a router which can "add" static entries...won't work with dynamic addresses. Sounds like a pretty poor setup, systems which could auto-add DHCP'd or discovered entries have been around for literally decades. You're choosing to live in that limitation. > What redundancy, multiple servers? Multicast name resolution is a thing. Hosts can send out queries and other devices can respond back. You don't need a centralized DNS server to have functional DNS.
- RiverCrochet 7mo agoOK, so use the IPv6 endpoints? Write them down if you have to use them that much? - 2001:4860:4860::8888 - 2001:4860:4860::8844 If you hate typing that much, computers may not be for you.
- yjftsjthsd-h 7mo agoI really don't think 2001:4860:4860::8888 is as easy to remember as 8.8.8.8, no. > If you hate typing that much, computers may not be for you. Nobody said anything about typing?