phil

@bieberium@infosec.exchange
51 Followers
213 Following
8.9K Posts

IETF RFC1925:

With sufficient thrust, pigs fly just fine. However, this is not necessarily a good idea. [...]

PronounsHe / Him
LocationCentral Germany
ProfessionSecurity minded AD & Entra ID admin
Bookwyrmhttps://books.infosec.exchange/user/bieberium
Twitter (archival data)https://twitter.com/bieberium
Twittodon (archival data)https://twittodon.com/share.php?t=bieberium&m=bieberium%40infosec.exchange

Reminder: The Shattering Peace, my next novel and the 7th installment in the Old Man's War series, is out two weeks from today! Still time to pre-order from your favorite bookstore, and to plan to see me on my US book tour! Here's the link with all the tour info:

https://whatever.scalzi.com/2025/08/16/the-shattering-peace-tour-dates-other-remaining-2025-appearances-now-live/

Dusty 1970s Ford Granada in the barn of an abandoned farm, Belgium 🇧🇪

#AbandonedPlaces #Barnfind #ClassicCar #WeirdCarMastodon #FordGranada #ClassicCar

"Some factual information for you. Have you any idea how much damage that bulldozer would suffer if I just let it roll straight over you?"
"How much?" said Arthur.
"None at all," said Mr. Prosser.

#HitchhikersGuide #DouglasAdams #quotes #quote #bot

Credit: Simon Kneebone
Von drüben geklaut. Es sollte jedoch noch hinzugefügt werden, dass die jungen Männer ihr Leben für den Erhalt der Vermögen der Milliardäre geben sollen.
Just when you thought you have seen every possible arrow key layout…

Darauf haben viele Senioren gewartet: Dixi-Toilette erstmals als Fahrradanhänger erhältlich

https://www.der-postillon.com/2025/09/dixi-move.html

Darauf haben viele Senioren gewartet: Dixi-Toilette erstmals als Fahrradanhänger erhältlich

Ratingen (dpo) - Gute Nachrichten für alle, die nicht auf öffentliche Klos angewiesen sein wollen: Der traditionsreiche Toilettenhersteller...

Blogger
To add a bit of chaos to the world, start referring to CDNs as "geocaching".
×

At home my Fritz Box takes care of DHCP and stuff, so laptops, phones etc. are in the fritz.box default domain. My homelab however has its own domain, homelab.jhw. So I have a mixture of hostnames with different domains in the same subnet. I just upgraded my home server, srv01.fritz.box and with this DNS setup, I could get a certificate with certbot for my home server from my own CA, which runs as a container on the Raspberry Pi:)

2/3

#SelfHost #DNS #Homelab

#ItsAlwaysDNS I took the plunge. Configured my Fritz Box to hand out my new DNS server to all DHCP devices. So now DNS requests go first to my BIND9, which resolves homelab.jhw. If it can't answer, it forwards to the Fritz Box, who takes care of the local fritz.box domain. And if that doesn't work it goes out to the internet. Seems to work :) I can now reach my homelab machines under their homelab.jhw name and with a valid certificate. Yay! Updated the gist too.

3/3

#SelfHost #DNS #Homelab

@jwildeboer Surprisingly good descriptions already in the document. While I haven't directly configured BIND at all, it is reasonably understandable overall.

@jwildeboer I wish I could properly control my home router, sadly Vodafone does not allow bridge mode in any port.

then I would just setup a proper router with everything AND the kitchen sink...

would even try again one of my first linux projects, LEAF uClibc :)

@jwildeboer If you control everything locally then never hijack an existing domain name/TLD. FritzBox as a company make a big mistake using `.box` as if it would never be delegated… until it was. you should instead create a name for real and use it as suffix for all internal naming. Or use the newest `.internal` TLD, guaranteed to never be delegated. Pro tip if you don't want to avoid future headaches.
@pmevzek I know. But AVM doesn't allow the user to change the domain used by a Fritz Box, it's always fritz.box. So for the devices connecting to my home network with DHCP, they'll get that domain suffix. For my servers and homelab, I now have the homelab.jhw domain. Should someone offer a .jhw TLD, I might switch. But .internal is simply too much to type for me :) TLDs should have never been allowed to have more than 3 characters, in my personal opinion …
@jwildeboer My tip still stands at "don't invent TLDs". You just create unnecessary burden. As for why TLDs should have any specific limits, outside of DNS technical limits, I am not sure why the justification could be. Like if Amsterdam the city wants its `.amsterdam` TLD, that is too long? Should the city change its name? If no fan of city TLDs, then countries, or companies, organizations, etc. Nowadays between bookmarks and autocompletion I am not even sure where you have to type anything…
@pmevzek I live on the terminal most of the time :) And I am fully aware of the possible consequences of my decision on using homelab.jhw for my local setup. I couldn't put the whole architecture decision process in this thread, though :)
@jwildeboer "I live on the terminal most of the time :)" And every good tool (ex: ssh) will autocomplete hostnames, so their length is really no impact on number of keystrokes, usually. Plus locally, while not without perils, you can force a suffix and use short names without the suffix. See /etc/resolv.conf domain and search options.
@jwildeboer "And I am fully aware of the possible consequences of my decision". Sure, everyone is master of his own LAN :-) I was just giving tip for anyone reading the thread and thinking options.Based out of too many horror stories of people starting with a naming design that created collisions later. If you want another example see the `.dev` fiasco once Google enabled it, or also read why `.mail` and `.home` will probably never exist… (granted you dislike over 3 characters, but they exist).
@pmevzek I will write a blog post with far more details where I will also discuss the topic of TLDs. This thread isn't the place for that, IMHO.

@pmevzek I added this warning to my gist.

"I really should use the official `.internal` TLD (Top Level Domain) for my homelab network, but I decided against it. This introduces the risk of name resolution problems, should someone offer a public `.jhw` TLD in future. It's a risk I am willing to accept in exchange for using a 3 letter TLD at home. Dont'be li8ke me! Use `.internal` instead."

https://codeberg.org/jwildeboer/gists/src/branch/main/2025/20250826DNSHomelabBind9.md

gists/2025/20250826DNSHomelabBind9.md at main

gists - A collection of short notes on specific little things that are good enough to share but not yet valuable enough for a blog entry. Mostly geeky stuff. Free to copy/paste, no restrictions from my side. Artisanal, hand typed content. No AI.

Codeberg.org