Not to mention mortgage interest.

Ok so it is fully qualified then? I’m just confused because it sounded like you were saying I wasn’t using the term correctly in your other comment.

Hmm, my understanding was that FQDN means that anyone will resolve the domain to e.g. the same IP address? Which is the case here (unless DNS rebinding mitigations or similar are employed) — but it doesn’t resolve to the same physical host in this case since it’s a private IP. Wikipedia:

A fully qualified domain name is distinguished by its lack of ambiguity in terms of DNS zone location in the hierarchy of DNS labels: it can be interpreted only in one way.

In my example, I can run nslookup jellyfin.myexample.com 8.8.8.8 and it resolves to what I expect (a local IP address).

But IANA network professional by any means, so maybe I’m misusing the term?

TIL, thanks. I use namecheap and haven’t had any problems (mikrorik router).

If you have your own domain name+control over the DNS entries, a cute trick you can use for Jellyfin is to set up a fully qualified DNS entry to point to your local (private) IP address.

So, you can have jellyfin.example.com point to 192.168.0.100 or similar. Inaccessible to the outside world (assuming you have your servers set up securely, no port forwarding), but local devices can access.

This is useful if you want to play on e.g. Chromecast/Google TV dongle but don’t want your traffic going over the Internet.

It’s a silly trick to work around the fact that these devices don’t always query the local DNS server (e.g., your router), so you need something fully qualified — but a private IP on a public DNS record works just fine!

The network gear I manage is only accessible via VPN, or from a trusted internal network…

…and by the gear I manage, I mean my home network (a router and a few managed switches and access points). If a doofus like me can set it up for my home, I’d think that actual companies would be able to figure it out, too.

Travel expense reimbursement — though many companies have a “no receipt required if under $xyz” policy.

Debian (i3 on laptop, headless on homelab).

But apparently my coffee is Arch.

You can roll your own saline nasal rinse, but it takes a little care to get the salinity just right. And best to boil the water first in case of brain eating amoebas (seriously — not common, but very, very bad).

I’m holding out for Aperture Science, if for no other reason than that their AI has a dry, dark sense of humor.

Same, an R4 with an i5 4670k I built in grad school. It’s my ham radio computer now, as happy running Debian as the day I built it.

UN-Verified

Unfortunate abbreviation…

We have one kid, one one the way, and then it’s time for a Balls Voyage party (or snipped but still equipped, if you prefer).

I would be very surprised if such a fork would diverge from Linux. I would guess that this would be little more than a branch with (most likely) support for Russian hardware. Just my hunch.

A legitimate hard fork doesn’t seem particularly smart to me, but what do I know…

Duh, just read it back from /dev/random

You will recover the data, you just need to wait long enough.

I think it has a lot to do with disposition and convenience. I’m lazy, and I don’t like to drive if I can help it. But I live near enough to public transportation that we’ll spontaneously decide to hop on the subway and grab dinner on the waterfront.

It’s not the money that’s preventing us from hopping in the car to go to some new beach for dinner, it’s the convenience.

That’s how I started using Linux — big book with CD, I think it was “RedHat Linux Secrets 5.4” or something. 2.0 or 2.2 kernel.

Honestly, it was fantastic. And almost all of it is still relevant today. (Some of the stuff on xfree86 and the chap/pap stuff not so much.)

But it gave a really solid (IMHO) intro to a Linux/*NIX system, a solid overview of coreutils, etc. And while LILO has been long replaced, and afaik /sys didn’t exist at the time, it formed a good foundation.

I’ll refrain from commenting on any init system changes that have taken place since then.

Just use your $200+ Fluke to check the batteries, problem solved.

Wouldn’t be surprised if he thinks the bad guys won the American Civil War, too…

It’s mostly so that I can have SSL handled by nginx (and not per-service), and also for ease of hosting multiple services accessible via subdomains. So every service is its own subdomain.

Additionally, my internal network (as in, my physical LAN) does not have any port forwarding enabled — everything is over WireGuard to my VPS.