We’re pleased to announce the release of version 0.10.0 of “domain”, our #rustlang crate for interacting with the #DNS. This release results from the first three months of increased focus on the library, with three full-time #Rust developers and a one-year commitment from @sovtechfund.
I hooked my GNU/Linux-loving son up with an old #lenovo#thinkcenter mini-PC that I picked up at a used AV store for about $50. For another $20, I upgraded the ram to 12GB.
He's got it setup it up with #debian as his first home server, with which he's now hosting a few static websites and an internet radio station for his friends and family. He's got loads of resources to spare for when he gets into running larger services.
You don't need to spend $30+ a month on cloud services when an old recycled office PC will more than suffice.
The best part? Helping him troubleshoot his problems with #DNS and #nginx and all that fun stuff. I've already made every mistake possible over the decades, and he gets to benefit from that. That how it should work!
questo e' un pippone supertecnico per sistemisti informatici e basta ok ?
Fino a ieri avevo, da contratto, con un provider, un ip fisso, sempre quello per 10 anni.
Sulla base di questo ho preso la decisione, probabilmente sbagliata, di mettere l'istanza di casa direttamente sul nome a dominio (per fare nome presso cognome).
nginx a seconda che riceva una richiesta per sironi,tk, www.sironi.tk o altraroba.sironi.tk punta al servizio interno corrispondente
Il provider nuovo, gia' in funzione, non mi consente di avere un ip fisso, ma, mentre per i sottodomini, e' facile farli puntare con un cname a un dyndns qualsiasi, il dominio principale deve essere sempre indicato con un record A e un indirizzo ip.
Cambiare dominio activitypub senza perdere lo storico non si puo'.
In sostanza mi servirebbe migrare il dns del dominio su un gestore che permetta l'aggiornamento automatico (con un client tipo quelli dei dyndns) del record A
We have new KSK for the root!
Today a mega ceremony was held where new HSMs were introduced and a new root key was generated in them. This key will be pre-publicated at the end of this year, and the rollover will be at the end of 2026. It'll be the third in the history of the DNS. The first was in 2010 and the second in 2017. #dns#dnssec
The pre-release of NSD 4.10.0 is now available. This version of our #OpenSource authoritative #DNS server dramatically speeds up zone loading and IXFRs, up to almost four times faster than the previous implementation! 🏎️
Our new SIMD-capable #DNS zonefile parser is now part of the NSD main branch as a submodule. We'll finish the latest tests today and then make it available as a pre-release to allow you to test the speed improvements. We're curious to hear how this performs in your systems! https://github.com/NLnetLabs/nsd/pull/328
Why yes, I would love to restart my work laptop because macOS has forgotten how to DNS again, and I can't seem to reset it without a reboot.
With that last detail, I'm going to blame it no the various filters, DNS blockers, etc. provided by IT. At least one of them looked dead (or in distress) this morning.
I wouldn't hate these things so much if they didn't impact productivity so severely. Literally four, just for the network.
More straws on the #DNS camel: another #IETF draft to amend RFC 1035. :)
"4. Updates to RFC 1035
A DNS message with OPCODE = 0 (QUERY) MUST NOT include a QDCOUNT parameter whose value is greater than 1. It follows that the Question Section of a DNS message with OPCODE = 0 MUST NOT contain more than one question.
A DNS message with OPCODE = 0 (QUERY) and QDCOUNT > 1 MUST be treated as an incorrectly-formatted message. The value of the RCODE parameter in the response message MUST be set to 1 (FORMERR)."