#nameservers — Public Fediverse posts on home.social

Saustrup @[email protected] · 2026-04-19 · 15:39 UTC

I run my own #nameservers or #DNS if you will, and have done so for over 25 years. Initially based on #BIND (aka named) but I later moved to #PowerDNS, There are numerous frontends of varying quality available for PowerDNS. I have opinions on those, but this isn't about them.

For the secondary name servers (in the old and less enlightened days known as slaves) I've always run the same software as the primary. First BIND, then PowerDNS. Recently though, I've been testing out what appears to be a much simpler alternative: #NSD by #Amsterdam based NLnet Labs.

Using #CatalogZones - a new concept to me - I'm able to run secondaries with TSIG notifies and zone transfers as well as fully supported primary signed DNSSEC with a configuration of only 40 lines. No updates needed when adding or removing zones.

For this to work well though, some configuration is required for each zone on the primary. With a little trigger and function magic, this can be automized by the database.

Wheee!

#nameservers #dns #bind #powerdns #nsd #amsterdam

Saustrup @[email protected] · 2026-04-19 · 15:39 UTC

I run my own #nameservers or #DNS if you will, and have done so for over 25 years. Initially based on #BIND (aka named) but I later moved to #PowerDNS, There are numerous frontends of varying quality available for PowerDNS. I have opinions on those, but this isn't about them.

For the secondary name servers (in the old and less enlightened days known as slaves) I've always run the same software as the primary. First BIND, then PowerDNS. Recently though, I've been testing out what appears to be a much simpler alternative: #NSD by #Amsterdam based NLnet Labs.

Using #CatalogZones - a new concept to me - I'm able to run secondaries with TSIG notifies and zone transfers as well as fully supported primary signed DNSSEC with a configuration of only 40 lines. No updates needed when adding or removing zones.

For this to work well though, some configuration is required for each zone on the primary. With a little trigger and function magic, this can be automized by the database.

Wheee!

#nameservers #dns #bind #powerdns #nsd #amsterdam

sahilister @[email protected] · 2025-07-04 · 02:44 UTC

Recently made the transition to self hosting authoritative name servers. Wrote a bit of secondary options available for it and the experience itself https://blog.sahilister.in/2025/07/secondary-authoritative-name-server-options-for-self-hosted-domains/

Didn't found the process too hard TBF, worth a try.

#authoritative #nameservers #dns #domains

sahilister @[email protected] · 2025-07-04 · 02:44 UTC

Recently made the transition to self hosting authoritative name servers. Wrote a bit of secondary options available for it and the experience itself https://blog.sahilister.in/2025/07/secondary-authoritative-name-server-options-for-self-hosted-domains/

Didn't found the process too hard TBF, worth a try.

#authoritative #nameservers #dns #domains

sahilister @[email protected] · 2025-07-04 · 02:44 UTC

Recently made the transition to self hosting authoritative name servers. Wrote a bit of secondary options available for it and the experience itself https://blog.sahilister.in/2025/07/secondary-authoritative-name-server-options-for-self-hosted-domains/

Didn't found the process too hard TBF, worth a try.

#authoritative #nameservers #dns #domains

sahilister @[email protected] · 2025-07-04 · 02:44 UTC

Recently made the transition to self hosting authoritative name servers. Wrote a bit of secondary options available for it and the experience itself https://blog.sahilister.in/2025/07/secondary-authoritative-name-server-options-for-self-hosted-domains/

Didn't found the process too hard TBF, worth a try.

#authoritative #nameservers #dns #domains

#domains #dns #nameservers #authoritative

sahilister @[email protected] · 2025-07-04 · 02:44 UTC

Recently made the transition to self hosting authoritative name servers. Wrote a bit of secondary options available for it and the experience itself https://blog.sahilister.in/2025/07/secondary-authoritative-name-server-options-for-self-hosted-domains/

Didn't found the process too hard TBF, worth a try.

#authoritative #nameservers #dns #domains

sahilister @[email protected] · 2025-06-22 · 11:17 UTC

Case of (broken) maharashtra.gov.in Authoritative Name Servers https://blog.sahilister.in/2025/06/case-of-broken-maharashtra.gov.in-authoritative-name-servers/

TLDR they're broken on multiple levels. Sync broken, RFC 1918 address, each NS giving different response - there's too much going on.

#dns #authoritative #nameservers #india

sahilister @[email protected] · 2025-06-22 · 11:17 UTC

Case of (broken) maharashtra.gov.in Authoritative Name Servers https://blog.sahilister.in/2025/06/case-of-broken-maharashtra.gov.in-authoritative-name-servers/

TLDR they're broken on multiple levels. Sync broken, RFC 1918 address, each NS giving different response - there's too much going on.

#dns #authoritative #nameservers #india

sahilister @[email protected] · 2025-06-22 · 11:17 UTC

Case of (broken) maharashtra.gov.in Authoritative Name Servers https://blog.sahilister.in/2025/06/case-of-broken-maharashtra.gov.in-authoritative-name-servers/

TLDR they're broken on multiple levels. Sync broken, RFC 1918 address, each NS giving different response - there's too much going on.

#dns #authoritative #nameservers #india

sahilister @[email protected] · 2025-06-22 · 11:17 UTC

Case of (broken) maharashtra.gov.in Authoritative Name Servers https://blog.sahilister.in/2025/06/case-of-broken-maharashtra.gov.in-authoritative-name-servers/

TLDR they're broken on multiple levels. Sync broken, RFC 1918 address, each NS giving different response - there's too much going on.

#dns #authoritative #nameservers #india

#india #nameservers #authoritative #dns

sahilister @[email protected] · 2025-06-19 · 07:09 UTC

Good enough amount of name servers :P
```
$ dig ns sahil.rocks +short
ns2.afraid.org.
marvin.sahilister.net.
ns1.1984.is.
ns0.1984.is.
ns3.jing.rocks.
colin.sahilister.net.
puck.nether.net.
ns2.albony.in.
ns-global.kjsl.com.
ns4.he.net.
ns5.he.net.
```

#dns #authoritative #nameservers

sahilister @[email protected] · 2025-06-19 · 07:09 UTC

Good enough amount of name servers :P
```
$ dig ns sahil.rocks +short
ns2.afraid.org.
marvin.sahilister.net.
ns1.1984.is.
ns0.1984.is.
ns3.jing.rocks.
colin.sahilister.net.
puck.nether.net.
ns2.albony.in.
ns-global.kjsl.com.
ns4.he.net.
ns5.he.net.
```

#dns #authoritative #nameservers

sahilister @[email protected] · 2025-06-19 · 07:09 UTC

Good enough amount of name servers :P
```
$ dig ns sahil.rocks +short
ns2.afraid.org.
marvin.sahilister.net.
ns1.1984.is.
ns0.1984.is.
ns3.jing.rocks.
colin.sahilister.net.
puck.nether.net.
ns2.albony.in.
ns-global.kjsl.com.
ns4.he.net.
ns5.he.net.
```

#dns #authoritative #nameservers

sahilister @[email protected] · 2025-06-19 · 07:09 UTC

Good enough amount of name servers :P
```
$ dig ns sahil.rocks +short
ns2.afraid.org.
marvin.sahilister.net.
ns1.1984.is.
ns0.1984.is.
ns3.jing.rocks.
colin.sahilister.net.
puck.nether.net.
ns2.albony.in.
ns-global.kjsl.com.
ns4.he.net.
ns5.he.net.
```

#dns #authoritative #nameservers

#nameservers #authoritative #dns

sahilister @[email protected] · 2025-02-13 · 18:14 UTC

Observing .ic TLD against authoritative nameservers serving samsung.com. No information of them anywhere.

$ dig ns samsung.com +short
auth04.sam.ic.
auth02.nhn.ic.
auth01.nhn.ic.
dns-gi2.samsung.com.
auth02.sam.ic.
dnssm.samsung.com.
dns-awskr1.samsung.com.
dnssm2.samsung.com.
dnsst.samsung.com.
dnsst2.samsung.com.
auth03.nhn.ic.
auth04.nhn.ic.
auth01.sam.ic.
auth03.sam.ic.
dns-gi1.samsung.com.

Maybe some internal thingy? Thoughts?

#DNS #Authoritative #Nameservers

#dns #authoritative #nameservers

sahilister @[email protected] · 2025-02-13 · 18:14 UTC

Observing .ic TLD against authoritative nameservers serving samsung.com. No information of them anywhere.

$ dig ns samsung.com +short
auth04.sam.ic.
auth02.nhn.ic.
auth01.nhn.ic.
dns-gi2.samsung.com.
auth02.sam.ic.
dnssm.samsung.com.
dns-awskr1.samsung.com.
dnssm2.samsung.com.
dnsst.samsung.com.
dnsst2.samsung.com.
auth03.nhn.ic.
auth04.nhn.ic.
auth01.sam.ic.
auth03.sam.ic.
dns-gi1.samsung.com.

Maybe some internal thingy? Thoughts?

#DNS #Authoritative #Nameservers

#dns #authoritative #nameservers

sahilister @[email protected] · 2025-02-13 · 18:14 UTC

Observing .ic TLD against authoritative nameservers serving samsung.com. No information of them anywhere.

$ dig ns samsung.com +short
auth04.sam.ic.
auth02.nhn.ic.
auth01.nhn.ic.
dns-gi2.samsung.com.
auth02.sam.ic.
dnssm.samsung.com.
dns-awskr1.samsung.com.
dnssm2.samsung.com.
dnsst.samsung.com.
dnsst2.samsung.com.
auth03.nhn.ic.
auth04.nhn.ic.
auth01.sam.ic.
auth03.sam.ic.
dns-gi1.samsung.com.

Maybe some internal thingy? Thoughts?

#DNS #Authoritative #Nameservers

#dns #authoritative #nameservers

sahilister @[email protected] · 2025-02-13 · 18:14 UTC

Observing .ic TLD against authoritative nameservers serving samsung.com. No information of them anywhere.

$ dig ns samsung.com +short
auth04.sam.ic.
auth02.nhn.ic.
auth01.nhn.ic.
dns-gi2.samsung.com.
auth02.sam.ic.
dnssm.samsung.com.
dns-awskr1.samsung.com.
dnssm2.samsung.com.
dnsst.samsung.com.
dnsst2.samsung.com.
auth03.nhn.ic.
auth04.nhn.ic.
auth01.sam.ic.
auth03.sam.ic.
dns-gi1.samsung.com.

Maybe some internal thingy? Thoughts?

#DNS #Authoritative #Nameservers

#nameservers #authoritative #dns

sahilister @[email protected] · 2025-01-21 · 17:14 UTC