@esc 

I had the exact same issue and I fixed it by setting the DNS on the router to google.

 

Advanced -> Network -> Internet -> Advanced -> Use the Following DNS Address

Primary: 8.8.8.8

Secondary 8.8.4.4

 

Hope it helps.

i've been using 8.8.8.8 and 8.8.4.4 for years before the switch to the c4000.  Sorry, no help there.

 

So, I had my router updated and with the google dns and everything was working super, until the router lost WiFi and I could not get it to work. Returned it to the store. Got a new one, and guess what, my solution doesn’t work on the new router (old firmware, I won’t dare to update it again.). I’ve tried many different solution on my server but can’t get it to work again. Let me know if you got it. :( Best Regards

@GusX3 

I still have not gotten Hairpin NAT to work.  I know name resolution is working correctly because I have done many trace routes and they are correct.

@esc 

Well, I got it working with another dumb solution. I set up my old TP-Link Archer C1200 (Router I had before, which all worked correctly) on Access Point Mode, connected it to port 4 on the AC4000, and then, hooked up my server to the AC1200 (wifi or eth0). That solved most of my problems. :)

If you find something easier please let me know.

Best Regards.

i just purchased this c4000 today . if it does not support nat loopback its going back to the store .

 

i have no use for a router that does not support something so simple .

 

ill give support till monday to answer .

 

 

It's mind boggling that such a simple thing is not supported. It ruined all my home setup because of such a minor feature.

I guess my 6 year old R7000 is going back out from the closet and the C4000 back to the store.