det.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
Mastodon Server des Unterhaltungsfernsehen Ehrenfeld zum dezentralen Diskurs.

Administered by:

Server stats:

2.2K
active users

#BIND

0 posts0 participants0 posts today

For those that run a homelab with DNS and DHCP, are you using IPv6? I'm running BIND and debating if I need to configure IPv6 just to future-proof myself. I'm not seeing any issues, at least any that I notice.

Also, I know little about IPv6, so I admit I need to do some learning.

#homelab#dns#dhcp

Did you know ISC had a #DNS Hackathon recently? It was hosted by #RIPE_NCC , #dnsoarc , and #Netnod in Stockholm on March 14-15. We proposed a project, the DNS Zone Viewer, to integrate another DNS implementation (besides #BIND 9) with Stork, our graphical management interface.

Read more about it at isc.org/blogs/2025-dns-hackath !

www.isc.org · Report from the RIPE/OARC/Netnod DNS HackathonPiotrek Zadroga and I attended the DNS Hackathon, hosted by RIPE NCC, DNS-OARC and Netnod in Stockholm on April 14-15.

I started a discussion with fellow #sysadmin about updating #BIND / #named config to migrate from the overly permissive allow-update {…} stanzas to the more restricted update-policy {…} stanzas using targeted grant statements.

The idea being to allow the #acme client to only be able to update (add / delete) _acme-challenge TXT instead of any record in the zone.

Old:

allow-update {
TSIG_KEY_NAME;
};

New:

update-policy {
grant TSIG_KEY_NAME name _acme-challenge.example.net TXT;
};

💡 You can simultaneously query multiple domain name records using the dig command in Linux as follows:

dig OPTIONS @server -f BATCH_FILE

Example:
dig +nocmd +noquestion +nostats +nocomments @8.8.8.8 -f mydomains.txt
@8.8.8.8 -f mydomains.txt

cat mydomains.txt
example.com A
example.net MX
example.org NS

TIP: dig is part of the dns/bind utilities package depending on your distribution

#ZikTIPS#DNS#Bind

Fixed mounting my #bind mount of a #ZFS volume in /etc/fstab on boot. According to "man systemd.mount" adding the "nofail" mount option to my bind mount was the correct way to break the default dependency of the ZFS mount service on things in /etc/fstab (via local-fs.target). Then I could use a "x-systemd.requires=zfs.target" mount option to my bind mount to have it wait for the ZFS mounts first, without creating a circular dependency. Yaiy! Pretty powerful dep. handling, #systemd backed mounts.

Oh my goodness, how did I miss that in ES7 you can use a closure as a method. Goodbye `bind()`, you will not be missed :)

e.g.,

```js
class A {
b = () => console.log(this)
}

const a = new A()
a.b() // A { b: [Function: b] }

const c = a.b
c() // A { b: [Function:b] }
```

Nice! :)

**Edit**: Be careful with this. See this note by @marsup: mastodon.social/@marsup/113799

MastodonMarsup (@marsup@mastodon.social)@aral@mastodon.ar.al Respectfully, this looks like an anti-pattern. `b` won't be part of the prototype, potentially preventing some meta programming, and you're going to get a new `b` for each instance of that class, consuming that much more memory for each instance you hold.

Finally got around to setup a #FreeBSD server. There was a huge need for more beastie fun 😎
Currently serves #DNS in a #Jail via #Bind
Another #Jail is on the way for some internal hosting via #Nginx :freebsd:

Currently looking for some more ideas on how to leverage the system some more.

What do you guys run on your #BSD servers?

(Most of my services are currently containerized on a #Docker #Linux server)

All #selfhosting people here in the Fediverse:

If you self-host your DNS, what software do you use? Especially folks, who use things like DNSSEC.

I am using #bind with a hidden master and two authoritative DNS servers in offsite data centers for almost 20 years and consider migrating to something more modern (Maybe PowerDNS?!)

Any opinions? Using a cloud service where a third party has control over my zones isn't an acceptable option.