#nameserver — Public Fediverse posts

Sometime I wonder if India not self managing the .in ccTLD in house is a good thing (as it mostly works) but then again, we haven't had the technical and political will to do investment to manage it here.

With all the talks of sovereign tech and stuff, having such a critical infrastructure outsourced seems ironical.

#nameserver #DNS #India

Sometime I wonder if India not self managing the .in ccTLD in house is a good thing (as it mostly works) but then again, we haven't had the technical and political will to do investment to manage it here.

With all the talks of sovereign tech and stuff, having such a critical infrastructure outsourced seems ironical.

#nameserver #DNS #India

Sometime I wonder if India not self managing the .in ccTLD in house is a good thing (as it mostly works) but then again, we haven't had the technical and political will to do investment to manage it here.

With all the talks of sovereign tech and stuff, having such a critical infrastructure outsourced seems ironical.

#nameserver #DNS #India

Sometime I wonder if India not self managing the .in ccTLD in house is a good thing (as it mostly works) but then again, we haven't had the technical and political will to do investment to manage it here.

With all the talks of sovereign tech and stuff, having such a critical infrastructure outsourced seems ironical.

#nameserver #DNS #India

Sometime I wonder if India not self managing the .in ccTLD in house is a good thing (as it mostly works) but then again, we haven't had the technical and political will to do investment to manage it here.

With all the talks of sovereign tech and stuff, having such a critical infrastructure outsourced seems ironical.

#nameserver #DNS #India

Hello, j'ai un domaine dont les NS sont aux US et au Canada. Est ce qu'en soi c'est un problème ? Est ce qu'il existe des NS publics fiables en Europe ? Si je cherche, je tombe bien sur des listes des trucs (genre https://publicdnsserver.com/switzerland/ ). Mais je n'ai aucune idée du sérieux de ce genre de listes, pas plus que de l'utilisabilité de ces serveurs dans ce contexte.

#NameServer #Domaine #NomDeDomaine #DNS

:boost_requested: appréciés

Hello, j'ai un domaine dont les NS sont aux US et au Canada. Est ce qu'en soi c'est un problème ? Est ce qu'il existe des NS publics fiables en Europe ? Si je cherche, je tombe bien sur des listes des trucs (genre https://publicdnsserver.com/switzerland/ ). Mais je n'ai aucune idée du sérieux de ce genre de listes, pas plus que de l'utilisabilité de ces serveurs dans ce contexte.

#NameServer #Domaine #NomDeDomaine #DNS

:boost_requested: appréciés

Hello, j'ai un domaine dont les NS sont aux US et au Canada. Est ce qu'en soi c'est un problème ? Est ce qu'il existe des NS publics fiables en Europe ? Si je cherche, je tombe bien sur des listes des trucs (genre https://publicdnsserver.com/switzerland/ ). Mais je n'ai aucune idée du sérieux de ce genre de listes, pas plus que de l'utilisabilité de ces serveurs dans ce contexte.

#NameServer #Domaine #NomDeDomaine #DNS

:boost_requested: appréciés

Hello, j'ai un domaine dont les NS sont aux US et au Canada. Est ce qu'en soi c'est un problème ? Est ce qu'il existe des NS publics fiables en Europe ? Si je cherche, je tombe bien sur des listes des trucs (genre https://publicdnsserver.com/switzerland/ ). Mais je n'ai aucune idée du sérieux de ce genre de listes, pas plus que de l'utilisabilité de ces serveurs dans ce contexte.

#NameServer #Domaine #NomDeDomaine #DNS

:boost_requested: appréciés

Hello, j'ai un domaine dont les NS sont aux US et au Canada. Est ce qu'en soi c'est un problème ? Est ce qu'il existe des NS publics fiables en Europe ? Si je cherche, je tombe bien sur des listes des trucs (genre https://publicdnsserver.com/switzerland/ ). Mais je n'ai aucune idée du sérieux de ce genre de listes, pas plus que de l'utilisabilité de ces serveurs dans ce contexte.

#NameServer #Domaine #NomDeDomaine #DNS

:boost_requested: appréciés

np-ns.npix.net.np, one of the authoritative nameserver for .np ccTLD has been down since atleast 03/05/2026 https://dnsmon.ripe.net/np?start=2026-04-11T12%3A15%3A00.000Z&end=2026-06-29T10%3A44%3A51.383Z&zone=np.&protocol=tcp&ipVersion=both&viewpoint=unanswered-queries&autoRefresh=false&fullscreen=true&rt_color_range=60-722&rrt_color_range=125-200&uq_color_range=66-99&level=servers

#ccTLD #authoritative #nameserver #Nepal

np-ns.npix.net.np, one of the authoritative nameserver for .np ccTLD has been down since atleast 03/05/2026 https://dnsmon.ripe.net/np?start=2026-04-11T12%3A15%3A00.000Z&end=2026-06-29T10%3A44%3A51.383Z&zone=np.&protocol=tcp&ipVersion=both&viewpoint=unanswered-queries&autoRefresh=false&fullscreen=true&rt_color_range=60-722&rrt_color_range=125-200&uq_color_range=66-99&level=servers

#ccTLD #authoritative #nameserver #Nepal

np-ns.npix.net.np, one of the authoritative nameserver for .np ccTLD has been down since atleast 03/05/2026 https://dnsmon.ripe.net/np?start=2026-04-11T12%3A15%3A00.000Z&end=2026-06-29T10%3A44%3A51.383Z&zone=np.&protocol=tcp&ipVersion=both&viewpoint=unanswered-queries&autoRefresh=false&fullscreen=true&rt_color_range=60-722&rrt_color_range=125-200&uq_color_range=66-99&level=servers

#ccTLD #authoritative #nameserver #Nepal

np-ns.npix.net.np, one of the authoritative nameserver for .np ccTLD has been down since atleast 03/05/2026 https://dnsmon.ripe.net/np?start=2026-04-11T12%3A15%3A00.000Z&end=2026-06-29T10%3A44%3A51.383Z&zone=np.&protocol=tcp&ipVersion=both&viewpoint=unanswered-queries&autoRefresh=false&fullscreen=true&rt_color_range=60-722&rrt_color_range=125-200&uq_color_range=66-99&level=servers

#ccTLD #authoritative #nameserver #Nepal

np-ns.npix.net.np, one of the authoritative nameserver for .np ccTLD has been down since atleast 03/05/2026 https://dnsmon.ripe.net/np?start=2026-04-11T12%3A15%3A00.000Z&end=2026-06-29T10%3A44%3A51.383Z&zone=np.&protocol=tcp&ipVersion=both&viewpoint=unanswered-queries&autoRefresh=false&fullscreen=true&rt_color_range=60-722&rrt_color_range=125-200&uq_color_range=66-99&level=servers

#ccTLD #authoritative #nameserver #Nepal

112 – Was sind Nameserver und Cloudflare

https://nerdcafe.online/episoden/112-was-sind-nameserver-und-cloudflare/

112 – Was sind Nameserver und Cloudflare

https://nerdcafe.online/episoden/112-was-sind-nameserver-und-cloudflare/

So, while working on some #botnet research, I discovered a domain for which a #nameserver was configured with the name ns1.nulled-ns.com and ns2.nulled-ns.com. As more I figure out about this unknown authoritative nameserver, as more I am convinced that the entire purpose of the nameserver is to provide name services for malicious domain names, such as #c2 or #phishing domain names.

Happy about anyone commenting, or reaching out to me with more insights.

Cheers!

#dns #dnsintel #threatintel #infosec

So, while working on some #botnet research, I discovered a domain for which a #nameserver was configured with the name ns1.nulled-ns.com and ns2.nulled-ns.com. As more I figure out about this unknown authoritative nameserver, as more I am convinced that the entire purpose of the nameserver is to provide name services for malicious domain names, such as #c2 or #phishing domain names.

Happy about anyone commenting, or reaching out to me with more insights.

Cheers!

#dns #dnsintel #threatintel #infosec

So, while working on some #botnet research, I discovered a domain for which a #nameserver was configured with the name ns1.nulled-ns.com and ns2.nulled-ns.com. As more I figure out about this unknown authoritative nameserver, as more I am convinced that the entire purpose of the nameserver is to provide name services for malicious domain names, such as #c2 or #phishing domain names.

Happy about anyone commenting, or reaching out to me with more insights.

Cheers!

#dns #dnsintel #threatintel #infosec

So, while working on some #botnet research, I discovered a domain for which a #nameserver was configured with the name ns1.nulled-ns.com and ns2.nulled-ns.com. As more I figure out about this unknown authoritative nameserver, as more I am convinced that the entire purpose of the nameserver is to provide name services for malicious domain names, such as #c2 or #phishing domain names.

Happy about anyone commenting, or reaching out to me with more insights.

Cheers!

#dns #dnsintel #threatintel #infosec

So, while working on some #botnet research, I discovered a domain for which a #nameserver was configured with the name ns1.nulled-ns.com and ns2.nulled-ns.com. As more I figure out about this unknown authoritative nameserver, as more I am convinced that the entire purpose of the nameserver is to provide name services for malicious domain names, such as #c2 or #phishing domain names.

Happy about anyone commenting, or reaching out to me with more insights.

Cheers!

#dns #dnsintel #threatintel #infosec

Welcher #Domain #Registrar empfiehlt sich denn für .de Domains?
Zwingende Features:
- Setzen der autoritativen #Nameserver
- #DNSSEC
- ≤ 10 €/Jahr netto

#followerpower

Welcher #Domain #Registrar empfiehlt sich denn für .de Domains?
Zwingende Features:
- Setzen der autoritativen #Nameserver
- #DNSSEC
- ≤ 10 €/Jahr netto

#followerpower

Welcher #Domain #Registrar empfiehlt sich denn für .de Domains?
Zwingende Features:
- Setzen der autoritativen #Nameserver
- #DNSSEC
- ≤ 10 €/Jahr netto

#followerpower

Welcher #Domain #Registrar empfiehlt sich denn für .de Domains?
Zwingende Features:
- Setzen der autoritativen #Nameserver
- #DNSSEC
- ≤ 10 €/Jahr netto

#followerpower

Welcher #Domain #Registrar empfiehlt sich denn für .de Domains?
Zwingende Features:
- Setzen der autoritativen #Nameserver
- #DNSSEC
- ≤ 10 €/Jahr netto

#followerpower

As of today, #DNS4EU is live. A project that started somewhat of 3 years ago. Now, it's public and live, promising secure and resilient service to #EU citizens, strengthening the #European #cyberresiliency .

More here.

I queried my own domain name out of interest. The EU protective resolver resolves in 340 ms, whereas #Cloudflare and #Quad9 both resolve within 50 ms.

The unfiltered resolution however resolves within 50 ms as well, revealing that the filtering introduces a slight performance penalty.

#DNS #Nameserver

As of today, #DNS4EU is live. A project that started somewhat of 3 years ago. Now, it's public and live, promising secure and resilient service to #EU citizens, strengthening the #European #cyberresiliency .

More here.

I queried my own domain name out of interest. The EU protective resolver resolves in 340 ms, whereas #Cloudflare and #Quad9 both resolve within 50 ms.

The unfiltered resolution however resolves within 50 ms as well, revealing that the filtering introduces a slight performance penalty.

#DNS #Nameserver

As of today, #DNS4EU is live. A project that started somewhat of 3 years ago. Now, it's public and live, promising secure and resilient service to #EU citizens, strengthening the #European #cyberresiliency .

More here.

I queried my own domain name out of interest. The EU protective resolver resolves in 340 ms, whereas #Cloudflare and #Quad9 both resolve within 50 ms.

The unfiltered resolution however resolves within 50 ms as well, revealing that the filtering introduces a slight performance penalty.

#DNS #Nameserver

As of today, #DNS4EU is live. A project that started somewhat of 3 years ago. Now, it's public and live, promising secure and resilient service to #EU citizens, strengthening the #European #cyberresiliency .

More here.

I queried my own domain name out of interest. The EU protective resolver resolves in 340 ms, whereas #Cloudflare and #Quad9 both resolve within 50 ms.

The unfiltered resolution however resolves within 50 ms as well, revealing that the filtering introduces a slight performance penalty.

#DNS #Nameserver

As of today, #DNS4EU is live. A project that started somewhat of 3 years ago. Now, it's public and live, promising secure and resilient service to #EU citizens, strengthening the #European #cyberresiliency .

More here.

I queried my own domain name out of interest. The EU protective resolver resolves in 340 ms, whereas #Cloudflare and #Quad9 both resolve within 50 ms.

The unfiltered resolution however resolves within 50 ms as well, revealing that the filtering introduces a slight performance penalty.

#DNS #Nameserver

rate-limit {
  responses-per-second 5;
  window 5;
  slip 0;
  exempt-clients {
    alle_meine_freunde;
  };
  log-only no;
};
logging {
  channel rate-limit_file {
    file "/var/log/rate-limit.log" versions 3 size 5m;
    severity dynamic;
    print-time yes;
  };
  category rate-limit { rate-limit_file; };
};

rate-limit {
  responses-per-second 5;
  window 5;
  slip 0;
  exempt-clients {
    alle_meine_freunde;
  };
  log-only no;
};
logging {
  channel rate-limit_file {
    file "/var/log/rate-limit.log" versions 3 size 5m;
    severity dynamic;
    print-time yes;
  };
  category rate-limit { rate-limit_file; };
};

rate-limit {
  responses-per-second 5;
  window 5;
  slip 0;
  exempt-clients {
    alle_meine_freunde;
  };
  log-only no;
};
logging {
  channel rate-limit_file {
    file "/var/log/rate-limit.log" versions 3 size 5m;
    severity dynamic;
    print-time yes;
  };
  category rate-limit { rate-limit_file; };
};

Wie dumm ist eigentlich die Idee, einen der secondary authoritative #nameserver für eine Domain nur per #ipv6 erreichbar zu haben?

Wie dumm ist eigentlich die Idee, einen der secondary authoritative #nameserver für eine Domain nur per #ipv6 erreichbar zu haben?

Wie dumm ist eigentlich die Idee, einen der secondary authoritative #nameserver für eine Domain nur per #ipv6 erreichbar zu haben?

Wie dumm ist eigentlich die Idee, einen der secondary authoritative #nameserver für eine Domain nur per #ipv6 erreichbar zu haben?

Wie dumm ist eigentlich die Idee, einen der secondary authoritative #nameserver für eine Domain nur per #ipv6 erreichbar zu haben?

Kann es sein, dass die #telekom #nameserver #dns die #TTL nicht unbedingt befolgen?

Ich habe (#AusGruenden) hier einen RR auf 60 Sekunden gesetzt und irgendwie hat's jetzt (ziemlich genau?!) eine Stunde gedauert, bis die Updates an den LTE-VPN-Knoten durch waren...

Kann es sein, dass die #telekom #nameserver #dns die #TTL nicht unbedingt befolgen?

Ich habe (#AusGruenden) hier einen RR auf 60 Sekunden gesetzt und irgendwie hat's jetzt (ziemlich genau?!) eine Stunde gedauert, bis die Updates an den LTE-VPN-Knoten durch waren...

Kann es sein, dass die #telekom #nameserver #dns die #TTL nicht unbedingt befolgen?

Ich habe (#AusGruenden) hier einen RR auf 60 Sekunden gesetzt und irgendwie hat's jetzt (ziemlich genau?!) eine Stunde gedauert, bis die Updates an den LTE-VPN-Knoten durch waren...

Kann es sein, dass die #telekom #nameserver #dns die #TTL nicht unbedingt befolgen?

Ich habe (#AusGruenden) hier einen RR auf 60 Sekunden gesetzt und irgendwie hat's jetzt (ziemlich genau?!) eine Stunde gedauert, bis die Updates an den LTE-VPN-Knoten durch waren...

Kann es sein, dass die #telekom #nameserver #dns die #TTL nicht unbedingt befolgen?

Ich habe (#AusGruenden) hier einen RR auf 60 Sekunden gesetzt und irgendwie hat's jetzt (ziemlich genau?!) eine Stunde gedauert, bis die Updates an den LTE-VPN-Knoten durch waren...

What would one use for an internal, authoritative nameserver these days on Debian? Shall I go with good old Bind as I have been for decades or is there something better?

(Just a handful of zones, definitely keeping text-based zone files, tooling for automatically generating reverse zones could be nice...)

:BoostOK:

#debian #nameserver

What would one use for an internal, authoritative nameserver these days on Debian? Shall I go with good old Bind as I have been for decades or is there something better?

(Just a handful of zones, definitely keeping text-based zone files, tooling for automatically generating reverse zones could be nice...)

:BoostOK:

#debian #nameserver

What would one use for an internal, authoritative nameserver these days on Debian? Shall I go with good old Bind as I have been for decades or is there something better?

(Just a handful of zones, definitely keeping text-based zone files, tooling for automatically generating reverse zones could be nice...)

:BoostOK:

#debian #nameserver

What would one use for an internal, authoritative nameserver these days on Debian? Shall I go with good old Bind as I have been for decades or is there something better?

(Just a handful of zones, definitely keeping text-based zone files, tooling for automatically generating reverse zones could be nice...)

:BoostOK:

#debian #nameserver

What would one use for an internal, authoritative nameserver these days on Debian? Shall I go with good old Bind as I have been for decades or is there something better?

(Just a handful of zones, definitely keeping text-based zone files, tooling for automatically generating reverse zones could be nice...)

:BoostOK:

#debian #nameserver

Managing authoritative and recursive name servers (i.e. DNS servers) at hopbox, has shown us a bunch of quirks and insights of domain name system. Read more at https://blog.hopbox.net/sahil/dns-chronicles-part-1

#DNS #nameserver

Managing authoritative and recursive name servers (i.e. DNS servers) at hopbox, has shown us a bunch of quirks and insights of domain name system. Read more at https://blog.hopbox.net/sahil/dns-chronicles-part-1

#DNS #nameserver

Managing authoritative and recursive name servers (i.e. DNS servers) at hopbox, has shown us a bunch of quirks and insights of domain name system. Read more at https://blog.hopbox.net/sahil/dns-chronicles-part-1

#DNS #nameserver

Managing authoritative and recursive name servers (i.e. DNS servers) at hopbox, has shown us a bunch of quirks and insights of domain name system. Read more at https://blog.hopbox.net/sahil/dns-chronicles-part-1

#DNS #nameserver

#Fleek is leveraging #TEEs, specifically #IntelSGX, to create a secure, #decentralized #DNS #nameServer. This protects DNS data and keeps private keys secure by executing sensitive processes inside a secure enclave.

Centralized name servers can lie or be compromised. DNSSEC helps somewhat but is limited. Fleek’s approach aims to address this by ensuring only the #domain owner (a private key holder or smart contract) can update DNS records!

https://fleek.xyz/blog/announcements/decentralized-trustless-frontend-hosting-fleek/

#fleekxyz #web3

#Fleek is leveraging #TEEs, specifically #IntelSGX, to create a secure, #decentralized #DNS #nameServer. This protects DNS data and keeps private keys secure by executing sensitive processes inside a secure enclave.

Centralized name servers can lie or be compromised. DNSSEC helps somewhat but is limited. Fleek’s approach aims to address this by ensuring only the #domain owner (a private key holder or smart contract) can update DNS records!

https://fleek.xyz/blog/announcements/decentralized-trustless-frontend-hosting-fleek/

#fleekxyz #web3

#Fleek is leveraging #TEEs, specifically #IntelSGX, to create a secure, #decentralized #DNS #nameServer. This protects DNS data and keeps private keys secure by executing sensitive processes inside a secure enclave.

Centralized name servers can lie or be compromised. DNSSEC helps somewhat but is limited. Fleek’s approach aims to address this by ensuring only the #domain owner (a private key holder or smart contract) can update DNS records!

https://fleek.xyz/blog/announcements/decentralized-trustless-frontend-hosting-fleek/

#fleekxyz #web3

#Fleek is leveraging #TEEs, specifically #IntelSGX, to create a secure, #decentralized #DNS #nameServer. This protects DNS data and keeps private keys secure by executing sensitive processes inside a secure enclave.

Centralized name servers can lie or be compromised. DNSSEC helps somewhat but is limited. Fleek’s approach aims to address this by ensuring only the #domain owner (a private key holder or smart contract) can update DNS records!

https://fleek.xyz/blog/announcements/decentralized-trustless-frontend-hosting-fleek/

#fleekxyz #web3

#Fleek is leveraging #TEEs, specifically #IntelSGX, to create a secure, #decentralized #DNS #nameServer. This protects DNS data and keeps private keys secure by executing sensitive processes inside a secure enclave.

Centralized name servers can lie or be compromised. DNSSEC helps somewhat but is limited. Fleek’s approach aims to address this by ensuring only the #domain owner (a private key holder or smart contract) can update DNS records!

https://fleek.xyz/blog/announcements/decentralized-trustless-frontend-hosting-fleek/

#fleekxyz #web3

Yesterday I get mad cause subtly, in random times my PC It was be able to resolve names like duckduckgo, lichess, mastodon, etc but in some times it doesn't...

Today I realized that dad's smartphone is getting the same ipv4 that my pc 🤦‍♂️... Router's DHCP giving the same ipv4 in two devices so so weird...

Cheers!

#randommoments #dhcp #dns #nameserver #anecdotes