• @[email protected]
      link
      fedilink
      141 year 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
      121 year 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.

      • Natanael
        link
        fedilink
        21 year 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

        • Mike
          link
          fedilink
          11 year ago

          Tell that to my opnsense box that refuses to NAT mirror.

        • @dot20
          link
          11 year ago

          I think OP is referring to NAT hairpinning though.

    • @ArtVandelay
      link
      English
      -31 year ago

      That’s a WAN IP, so it would be resolved by external DNS then routed back

          • @ArtVandelay
            link
            English
            4
            edit-2
            1 year 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
          21 year ago

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