• DefederateLemmyMl@feddit.nl
    link
    fedilink
    English
    arrow-up
    4
    ·
    6 hours ago

    Randomly? No, only when your pi goes down

    Not how secondary DNS works. It round robins the requests across primary and secondary DNS servers.

    • JackbyDev@programming.dev
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 hour ago

      Why call it secondary then, that’s so counterintuitive lol 😭 I guess “the second hardest problem in computer science” applies because I can’t think of a better name either.

      • DefederateLemmyMl@feddit.nl
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 hour ago

        Why call it secondary then, that’s so counterintuitive lol

        I don’t think that’s even the official naming. It probably comes from what Windows 95 called it back in the day:

        On Linux, it’s just an additional “nameserver x.x.x.x” line in /etc/resolv.conf, with no indication of which is the “primary” or “secondary”.

      • chaospatterns@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        ·
        edit-2
        1 hour ago

        Different Operating Systems call it different things. Windows calls it Alternate. Even if it was only used when the primary was down, DNS doesn’t provide any sort of guidance or standard on when to switch between primary and secondary. Is one query timeout enough to switch? How often do you reattempt to the first DNS server? When do you switch back? With individual queries, you can timeout and hit another NS server, but that’s a lot easier at an individual level than to infer a global system state from one query timing out.