GNU social JP
  • FAQ
  • Login
GNU social JPは日本のGNU socialサーバーです。
Usage/ToS/admin/test/Pleroma FE
  • Public

    • Public
    • Network
    • Groups
    • Featured
    • Popular
    • People

Conversation

Notices

  1. Embed this notice
    sahilister (sahil@toots.sahilister.in)'s status on Wednesday, 22-Jan-2025 02:14:08 JST sahilister sahilister

    How good (or a bad) idea is to run ones own authoritative nameservers?

    Any tips/tricks/suggestions or gotyas to remember?

    #dns #authoritative #nameservers

    In conversation Wednesday, 22-Jan-2025 02:14:08 JST from toots.sahilister.in permalink
    • Embed this notice
      John Kristoff (jtk@infosec.exchange)'s status on Wednesday, 22-Jan-2025 12:45:35 JST John Kristoff John Kristoff
      in reply to

      @sahil If you want to see details about who and what is issuing queries for your names, it's a good idea.

      If your name(s) are prone to attack, it might be a bad idea unless you partner with a provider who can host and help mitigate large floods.

      If your zone(s) don't change very often and have few records, it is relatively easy to setup and run a couple of authoritative name servers, ideally on at least a couple of diverse networks using bind, unbound, or whatever you're comfortable with.

      Don't provide answers (recursion) you're not authoritative for.

      Don't forget to update your SOA serial every time you make a zone change.

      Do run your zone through various zone checking online tools (e.g., zonemaster.fr).

      Do use a provider who won't arbitrarily block networks/addresses or source ports.

      Don't run anything else on your name server, but maybe just SSH and NTP - and protect those from unsolicted access.

      You may not have a need for all their guidance, but see IETF RFCs 2870 ad 9199 for other ideas.

      In conversation Wednesday, 22-Jan-2025 12:45:35 JST permalink

      Attachments

      1. Domain not in remote thumbnail source whitelist: change.do
        CHANGE with us
        A fearless commitment to creativity and innovation, we strive to craft captivating visual and structurals narratives that evoke emotion and provoke thought.
      2. No result found on File_thumbnail lookup.
        Zonemaster
    • Embed this notice
      sahilister (sahil@toots.sahilister.in)'s status on Wednesday, 22-Jan-2025 12:46:07 JST sahilister sahilister
      in reply to
      • John Kristoff

      @jtk what're your thoughts on having a hidden primary? Is that a common occurrence in the wild?

      I'm thinking of adding some secondaries (off net, not managed by me as well), so in case my systems go down, updates can still be pushed via this "hidden" primary to everywhere as well.

      In conversation Wednesday, 22-Jan-2025 12:46:07 JST permalink
    • Embed this notice
      sahilister (sahil@toots.sahilister.in)'s status on Wednesday, 22-Jan-2025 12:50:54 JST sahilister sahilister
      in reply to
      • Patrick Mevzek

      @pmevzek I'm strongly leaning on PowerDNS (with BIND backend) because of some experience with that.

      > ... different OS and nameservers software
      for security reasons that is? Can you elaborate a bit here.

      Also, If I understand correctly IXFR/AXFR should flow fine across different name server software primary-secondary combinations (?)

      In conversation Wednesday, 22-Jan-2025 12:50:54 JST permalink
    • Embed this notice
      Patrick Mevzek (pmevzek@framapiaf.org)'s status on Wednesday, 22-Jan-2025 12:50:56 JST Patrick Mevzek Patrick Mevzek
      in reply to

      @sahil Depends authoritative on what kind of zones :-) If "critical" and you need 99.9999% reliability, then no. Otherwise, maybe. Theoretically, you need either solid anycast, OR at least 2 separate IP blocks in separate AS in separate datacenters with separate routing (+ ideally different OS and nameservers software). Plus the usual (power source, monitoring, etc.). But to do it at home on some toy zones, absolutely, to learn things!

      In conversation Wednesday, 22-Jan-2025 12:50:56 JST permalink

Feeds

  • Activity Streams
  • RSS 2.0
  • Atom
  • Help
  • About
  • FAQ
  • TOS
  • Privacy
  • Source
  • Version
  • Contact

GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.

Creative Commons Attribution 3.0 All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.