Home Web Server - Hairpin NAT / NAT Loopback Setup

[markwise]

I believe my problem is somewhat of an old classic.  I had it 10 years ago when running a home web server.  I'm having it again as I setup a new server.

The gist of it is this:  I'm using dynamic DNS to route outside traffic to my home web server.  Let's call my address home.example.com    That part of the setup is up and running just fine.  The problem is accessing it within my local network.  My local devices cannot resolve the DDNS name home.example.com.  The only way to access the webserver while on my local network is directly by typing in its IP address. 

I've done a fair amount of homework trying to resolve this and everything points towards setting up a hairpin NAT to get my local devices to resolve the home.example.com name.   

What I'm looking for is if any wonderful experts out there could direct me to any possible basic solution on my Google Wifi to setup a solution that would solve this.  I've seen some articles that suggest a proper combination of port forwards could do this but my network knowledge is so rusty I'm not quite sure where to get started on that.

[EdwardT]

Hi markwise,

Thanks for reaching out, and I'm sorry for the late response. To use NAT loopback, just set the appropriate port forwarding rules for the desired device. You could click on this link to learn more about setting up port forwarding on your Google WiFi.

Thanks,

Edward

[EdwardT]

Hi markwise,

It's me again, I wanted to check back in to see if you have other questions and concerns. Feel free to let me know if you do.

Thanks,

Edward

[markwise]

Thanks for your responses.  I am still stuck.  I know how to setup basic Port Forwarding on my Google Wifi.  My question is more of a next level one. 

I've already setup Port 80 and Port 443 for TCP and UDP to be forwarded to the IP address of my home web server.  Let's say that address is 192.168.86.20.

My problem is anytime I'm on my local network and I attempt to access it through its external name I am unable to.  By external name I have a dynamic DNS name setup for my home web server.  I've read about this problem on the web.  My understanding from this reading has led me to understand the need to setup Hairpin NAT or a NAT loopback.

I'm unsure of what further configuration I need on my Google Wifi setup to achieve this Hairpin NAT setup and allow my devices to access my home web server from its external dynamic DNS name.

[EdwardT]

Hi markwise,

Thanks for the update. We'd like to look deeper into this. Please fill out this form so we can investigate further.

Thanks,

Edward

[Jeff]

Hi, markwise.

I just wanted to jump in and see if you noticed the link that Edward shared with you and to see if you were able to get that filled out. If you have any questions about that, please let us know.

Thanks.

[markwise]

I appreciate the help guys, but I'm not filling out the form.  Everything it asks for has already been shared in the forum here.  

Thanks!

[Jeff]

Hi, markwise.

The form is to gather data for support teams. I realize you've put that information here in the forums, but that's accessible to community members for their input. To work directly with support channels, the form allows us to get that info to them directly.

Thanks.

[Jeff]

Hi, markwise.

I just wanted to check in to see if you managed to get that form filled out at this point. Let me know if there's anything I can answer for you in regards to that process.

Thanks.

[Jeff]

Hi, everyone.
Just one quick final check in here since activity has slowed down. We'll be locking the thread in the next 24 hours, but if you still need help, I would be happy to keep it open. If there's more we can do, just let me know.
Thanks.

[markwise]

Jeff, your continued diligence is appreciated, but if no one has any further ideas or thoughts to add to this thread then I imagine it would make sense to lock it.

[Jeff]

Thanks, markwise. I'm sorry it didn't resolve as we had hoped. If you want to pick things back up, please feel free to open up a new thread and we can circle back on troubleshooting.

Thanks.