I used to give all my machines permanent IP addresses and added entries in my domain for them. (I have /24 globally routable IP addresses.) I then got lazy and let most be assigned dynamically. But not servers. Now I'm even more lazy. I'm starting to use .local. So machines declare their hostname and mDNS / bonjour gets to resolve name.local. Neat. Tonight I'm creating an experimental NextCloud server. Let's say it's hostname is nc. - ping nc.local works - ssh nc.local works - host nc.local works - Firefox and even links cannot see nc.local. Why is that? Firefox is set to use the default DNS, not Firefox's own. If I give Firefox the actual IP address, Apache balks because it cares about the DNS name used. But that's further than nc.local got. I guess Firefox doesn't do mDNS. Why would that be? Or am I making a wrong guess? Clearly I could give to computer a real DNS name, but I'm kind of stubborn and want to understand what's going on.
D. Hugh Redelmeier via talk wrote on 2024-02-26 22:43:
I'm starting to use .local. So machines declare their hostname and mDNS / bonjour gets to resolve name.local. Neat.
I ought to look into using .local myself, instead of when I had DDNS running. Sounds interesting.
Tonight I'm creating an experimental NextCloud server. Let's say it's hostname is nc.
- ping nc.local works - ssh nc.local works - host nc.local works - Firefox and even links cannot see nc.local.
Why is that?
I'm not sure, but I suspect somehow `ping`, `ssh`, and `host` avoid mDNS entirely. For your situation to work, it appears you need to tweak your /etc/nsswitch.conf file: https://superuser.com/questions/1417190/why-do-i-need-to-change-the-order-of... https://askubuntu.com/questions/678372/chrome-and-firefox-can-not-resolve-th... Basically, there should be a line which prioritizes mdns4_minimal over dns, similar to:
hosts: files mdns4_minimal dns
On Tue, Feb 27, 2024 at 01:43:36AM -0500, D. Hugh Redelmeier via talk wrote:
I used to give all my machines permanent IP addresses and added entries in my domain for them. (I have /24 globally routable IP addresses.)
I then got lazy and let most be assigned dynamically. But not servers.
Now I'm even more lazy. I'm starting to use .local. So machines declare their hostname and mDNS / bonjour gets to resolve name.local. Neat.
Tonight I'm creating an experimental NextCloud server. Let's say it's hostname is nc.
- ping nc.local works - ssh nc.local works - host nc.local works - Firefox and even links cannot see nc.local.
Why is that? Firefox is set to use the default DNS, not Firefox's own.
If I give Firefox the actual IP address, Apache balks because it cares about the DNS name used. But that's further than nc.local got.
I guess Firefox doesn't do mDNS. Why would that be? Or am I making a wrong guess?
Clearly I could give to computer a real DNS name, but I'm kind of stubborn and want to understand what's going on.
Is your firefox set to do DNS over HTTPS or normal DNS? Apparently since version 104 firefox always does a search for words entered in the address bar unless they end in standard domain suffixes. Entering host.local/ apparently should skip that and use dns instead. So does nc.local/ work in firefox? Now links is odd. Does it think it is a file name and not http since the .local is weird to it? Certainly on my system using 'links host.local' gives an error that file:///home/lsorense/host.local does not exist while 'links http://host.local' works. Looking at the source, links (well links2) uses the contents in the publicsuffix package at compile time to generate the internal list of known suffixes that it treats as http by default. Well that list plus 'onion' which for some reason mozilla doesn't want to include in the official suffix list but links2 does. -- Len Sorensen
D. Hugh Redelmeier via talk wrote on 2024-02-26 22:43:
(I have /24 globally routable IP addresses.)
I'm curious about the story behind how you acquired what's become such a rare item? Also - how does one use them behind a residential ISP? Do you have your own AS number? This all sounds quite interesting if you don't mind sharing some of the details for the nerdy amongst us. Thanks, rb
| From: Ron / BCLUG via talk <talk@gtalug.org> | D. Hugh Redelmeier via talk wrote on 2024-02-26 22:43: | | > (I have /24 globally routable IP addresses.) | | I'm curious about the story behind how you acquired what's become such a rare | item? If you asked 30+ years ago you got a "Class C" assignment. This isn't delegated. More recently, you get subnets delegated by your ISP. If you change ISPs, you change IPs. | Also - how does one use them behind a residential ISP? I have an arrangement with a small ISP. I've known one of the guys there for a long time. Unfortunately they can only resell DSL so the speed is low. Most of my traffic goes through NAT and over Bell Fibre (with a Bell dynamic address). If it mattered, I could rent a box at a colo and get fast speed for my /24. I could tunnel the traffic to my home through Bell. I have no idea whether colos are used to Bring Your Own IPs. | Do you have your own AS number? I haven't needed one. I've always assumed that I could get one if I wanted to. I've switched ISPs a few times over the years. I switch as the current one dies or is consolidated.
Interesting story; I just put my /24 block up for sale. I recall just asking U of T for it and they gave me one ... many decades ago, even pre-dating ARIN by a few years. So as a result, I've never had an ARIN agreement and don't even need one now to sell it. You might be surprised, but prices have actually been dropping for IP addresses over the last few years. Much cheaper now than through the COVID heyday. I do not have an AS number. On Tue, Feb 27, 2024 at 4:14 PM Ron / BCLUG via talk <talk@gtalug.org> wrote:
D. Hugh Redelmeier via talk wrote on 2024-02-26 22:43:
(I have /24 globally routable IP addresses.)
I'm curious about the story behind how you acquired what's become such a rare item?
Also - how does one use them behind a residential ISP?
Do you have your own AS number?
This all sounds quite interesting if you don't mind sharing some of the details for the nerdy amongst us.
Thanks,
rb
--- Post to this mailing list talk@gtalug.org Unsubscribe from this mailing list https://gtalug.org/mailman/listinfo/talk
-- Evan Leibovitch, Toronto Canada @evanleibovitch / @el56
On 2/27/24 17:30, Evan Leibovitch via talk wrote:
You might be surprised, but prices have actually been dropping for IP addresses over the last few years. Much cheaper now than through the COVID heyday.
That may be because more & more traffic is moving to IPv6.
Also - how does one use them behind a residential ISP?
Probably the way I use my /56 IPv6 prefix. I route it.
James Knott via talk wrote on 2024-02-27 14:50:
That may be because more & more traffic is moving to IPv6.
I suspect this is the case, although I'm still a bit surprised pricing would go down at all.
Also - how does one use them behind a residential ISP?
Probably the way I use my /56 IPv6 prefix. I route it.
I'm more thinking how does one get an entire /24 routed *to* one's home ISP address? Wouldn't the ISP have to be on board somewhere? And the AS that controls that /24? Does an AS even have control over it? /not a networking guru...
| From: D. Hugh Redelmeier via talk <talk@gtalug.org> | Tonight I'm creating an experimental NextCloud server. Let's say it's | hostname is nc. | | - ping nc.local works | - ssh nc.local works | - host nc.local works | - Firefox and even links cannot see nc.local. This report turns out to be very incomplete. These tests were on nc. On any other host, nc.local doesn't resolve at all. Odd. avahi is running. $ avahi-browse --all shows many things, but none of them being my PCs. /etc/nsswitch.conf has a line: hosts: files myhostname mdns4_minimal [NOTFOUND=return] resolve [!UNAVAIL=return] dns So I'm guessing that the nc.local is being resolved by "myhostname", not mdns4_minimal. On my desktop: $ sudo netstat -l -p -4 | grep avahi | cat udp 0 0 0.0.0.0:mdns 0.0.0.0:* 890/avahi-daemon: r udp 0 0 0.0.0.0:48151 0.0.0.0:* 890/avahi-daemon: r $ grep mdns /etc/services | cat mdns 5353/tcp # Multicast DNS mdns 5353/udp # Multicast DNS mdnsresponder 5354/tcp noclog # Multicast DNS Responder IPC mdnsresponder 5354/udp noclog # Multicast DNS Responder IPC The firewall allows mdns BTW, I'm tunning fedora 39 on all the boxes involved. I was going by this tutorial; it's bit old: <https://fedoramagazine.org/find-systems-easily-lan-mdns/> Pausing for dinner.
D. Hugh Redelmeier via talk wrote on 2024-02-27 15:39:
/etc/nsswitch.conf has a line: hosts: files myhostname mdns4_minimal [NOTFOUND=return] resolve [!UNAVAIL=return] dns
So I'm guessing that the nc.local is being resolved by "myhostname", not mdns4_minimal.
I don't understand why "myhostname" is in there (but that's probably a failing on my part). What if you switch "myhostname" and "mdns4_minimal" in nsswitch.conf and restart whichever services necessary, see if that works? Fingers crossed it's that simple and you're up & running afterwards. rb
participants (5)
-
D. Hugh Redelmeier -
Evan Leibovitch -
James Knott -
Lennart Sorensen -
Ron / BCLUG