• AnActOfCreation@programming.dev
      link
      fedilink
      arrow-up
      10
      ·
      1 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@lemmy.cafe
      link
      fedilink
      English
      arrow-up
      9
      ·
      1 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@slrpnk.net
        link
        fedilink
        arrow-up
        2
        ·
        1 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