Very sad this still isn't supported. Every other router supports this but not eero. Sure sounds like one developer engineer somewhere who doesn't believe in this feature so they won't include it. 

dfsutherland Thanks for sharing this for those who have an immediate need to temporarily address a major shortcoming of eero.

That said, eero engineers, don't mistake this for a solution. This is something that is beyond the abilities of your core market, and something that many of us will refuse to do on principle, because it's providing functionality that eero should have provided from the beginning.

For what it's worth, I've determined that the Netgear Orbi *does* support NAT loopback. I figure that they'll have sales on Orbi near the holidays, so eero has approximately five to six months to fix this mess before I jump ship.

Actually almost everything supports NAT Loopback/NAT Redirection/Hairpinning/so forth, so anyone should be able to easily find an alternative. Ha ha.

Personally, I went the more expensive route and couldn't be happier. I went Ubiquiti and deployed 2 APs with their USG. At $320, my mom's house has 2 APs and the USG router and she's never had faster speeds on every sq ft of her property. I did the UAP-AC-HD so my network cost $750, but I have 75 active devices and the same results. I never got over 50Mbps down and 35Mbps up on Eero, but I now get 82Mbps/120Mbps. Honestly, I even get faster WAN speeds via ethernet for some reason over every other router I have tried. I had spent $600 on Eero since I bought more access points, but I returned them all within the time frame. The other poor folks on this thread didn't have that opportunity. I was fortunate.

I still follow this thread since I set up systems for other people as a side job, and it's sad to think this hasn't been addressed.

Eero Engineers & go_robot_go 

go_robot_go said:
That said, eero engineers, don't mistake this for a solution. This is something that is beyond the abilities of your core market, and something that many of us will refuse to do on principle, because it's providing functionality that eero should have provided from the beginning.

 Yes, I made this work. But I've been programming since the 1970s, and on the Internet since the old Arpanet had three nodes, so I'm not exactly your core market... except that I'd rather spend a little more to avoid having to mess with issues like this. That's what I thought I was buying! I was only partly correct. 

If I was helping family or friends, the Egress hair-pinning issue would have led to an instant return! I'm just barely willing to do the additional work I described above for myself—and that only because it worked perfectly on the first try. I would be utterly unwilling to do this extra work as volunteer support for someone else.

The primary reason for paying premium prices for devices like the Eero is to get a good-performing network that "just works" with absolute minimum fiddling. Even with Apple making it easy, setting up an internal DNS server is clearly incompatible with absolute minimum fiddling. And with the vast majority of competing devices providing this functionality, you really, really should have provided it from the beginning.

Did anyone with a Synology NAS figure out how to configure the DNS Server app properly as a workaround here?   Messed a bit with the settings, but can't find the magic config that allows my domain name (or even the DDNS name) to be accessible from within my network.  It's crazy that this still is not supported.

+1 for NAT loopback/hairpinning. It's really sad that you don't support this when every cheapo $50 router has for 15+ years. Makes me regret my purchase, looking at Google's now instead.

This is a repost from another commenter that I totally agree with. "+1 for NAT hairpin.  It is ridiculous to require either an internal DNS server or additional hardware (separate router) to enable this functionality.  I bought Eero because I was tired of having a router I needed to reconfigure, troubleshoot & restart all the time, and refuse to add that back in to the mix.  

The smart home becomes dumb, and the camera system becomes overly complex for any non technical person (my wife) to connect to." 

+1 for the feature that, as others have pointed out, almost every other router supports. I'm otherwise happy with the Gen 2 hardware, especially the beacons, but now I have to setup an internal DNS server to access my computers, cameras, and other smart devices the same at home as away.

Another vote for NAT hairpin.  If it is such a security risk, why does every other router manufacturer have it enabled.  I cannot return my eeros as they are 6 months old.  I would like to, after seeing the company fail to enable this feature despite about 100 replies to this thread.

I was having trouble connecting to my iMac 2017 inside of my home wifi when using Screens Connect.  Had to contact tech support at Edovia, who sent me over to this thread.  If Bonjour stops working (for whatever reason) then the secondary connection method Screens uses is refused by eero router because of this hairpinning issue.

So, eero----please get it together and enable this.

Thanks

Go to the Netgear Orbi forum and see how that is going...from there to here...

Amazon has the AmpliFi HD on sale: https://goo.gl/2A1Rrz

Here is the UAP-Pro: https://goo.gl/DFPzVn

And Google WiFi is on sale too!!!!: https://goo.gl/uji3Yf

I have not heard the best stuff about the Orbi, though performance wise, it seems to be solid.

One more +1 for this feature.  It is really hard to believe that it isn't supported yet, even though the cheap ass d-links & linksys routers do....

+1. This is a basic feature needed for any router.  Please implement. Thanks!

+1!  This seems like a major omission for a router with home automation in it's infancy.  This missing feature is becoming more and more important by the day.  Eero, please add this feature ASAP!