• @PR_freak
    link
    16
    edit-2
    7 months ago

    deleted by creator

    • @AnActOfCreation
      link
      149 months ago

      If the router supports hairpinning, the IP request can be resolved locally.

      The domain name lookup would be a different issue and could potentially need to be resolved externally, but the router’s DNS cache should be able to answer eventually.

    • Illecors
      link
      fedilink
      English
      129 months ago

      Depends. If the zone responsible for whatever resolves to that IP is hosted locally - then DNS request would stay local.

      If the service behind that IP is running locally - then all traffic would stay local. Network stack would be smart enough to not run circles to find itself.

      • @[email protected]
        link
        fedilink
        29 months ago

        Yeah, the router ought to know that public IP belongs to a device in its own network unless you’re doing stuff like running your own router behind an ISP provided router and just forwarding ports instead of maintaining IP assignment / routing tables

      • @PR_freak
        link
        14
        edit-2
        7 months ago

        deleted by creator

        • @AnActOfCreation
          link
          39 months ago

          Because the title mentions having a domain, I guess.

          • @[email protected]
            link
            fedilink
            English
            4
            edit-2
            9 months ago

            Yes, that was the train of thought I was on. I equated “find” to “resolve” and I’ve been dutifully chastised.

        • macniel
          link
          fedilink
          29 months ago

          Yeah no need for DNS but an ARP lookup would be in order.