Hey gang, I’m considering using DNS4EU in Canada. My ping to their servers is ~130ms. That’s way longer than anything local which is on the order of 1-5ms. Apart from resolving uncached entries taking longer, is there any contraindication to using a DNS server with high latency?

  • Avid Amoeba@lemmy.caOP
    link
    fedilink
    English
    arrow-up
    9
    arrow-down
    2
    ·
    16 hours ago

    Not asking for a workaround. Asking if I’m missing some problem with using a slow DNS server I might run into, other than the obvious one.

    • lambalicious@lemmy.sdf.org
      link
      fedilink
      English
      arrow-up
      11
      ·
      16 hours ago

      The only task of a DNS server is (or should be) to tell you how to get to a resource you’re looking for by name. So, the only thing that is going to be reallistically affected is your (initial) connection times. And – since this is c/selfhosted – if you are setting a decent DNS cache in your local network, that should be even less of an issue.

      The only borderline scenario that I could see feasible, since this is c/selfhosted , is that some software you are setting up that requires nanosecond DNS resolution or somesuch sillyness is going to fail or report false errors. But why would you even do that?

      • just_another_person@lemmy.world
        link
        fedilink
        English
        arrow-up
        2
        ·
        16 hours ago

        And that’s not even letting on that literally ALL DNS queries work from cache unless you are specifically doing a live query.

        None of your software is. It’s asking your OS. Your OS is asking your resolver service. Your resolver service is asking your router. Your router is 5000% caching DNS queries.