2025-04-01, 01:35 PM
Putting your LAN IP in Cloudflare will break access when not at home. Since those are private, non-routable, IPs.
What you should be is put back your public IP in cloudflare. Then in your router you can do one of two things. You can enable NAT loopback/hairpin or you can create custom DNS entries. NAT hairpin/loopback tells your router to intelligently keep traffic local. If it queries your domain name and sees that the IP address is itself, it will keep local traffic local.
The custom DNS entries would tell your local clients to use your LAN IP for your domain. But when your device disconnects, like your phone, the DNS results for your domain will now be your public IP.
I personally prefer custom DNS entries since it will continue to work properly when there is an Internet outage.
What you should be is put back your public IP in cloudflare. Then in your router you can do one of two things. You can enable NAT loopback/hairpin or you can create custom DNS entries. NAT hairpin/loopback tells your router to intelligently keep traffic local. If it queries your domain name and sees that the IP address is itself, it will keep local traffic local.
The custom DNS entries would tell your local clients to use your LAN IP for your domain. But when your device disconnects, like your phone, the DNS results for your domain will now be your public IP.
I personally prefer custom DNS entries since it will continue to work properly when there is an Internet outage.