Does Archer BE400 (BE6500) support NAT Loopback / Hairpin NAT?

Does Archer BE400 (BE6500) support NAT Loopback / Hairpin NAT?

Does Archer BE400 (BE6500) support NAT Loopback / Hairpin NAT?
Does Archer BE400 (BE6500) support NAT Loopback / Hairpin NAT?
9 hours ago
Model: Archer BE400  
Hardware Version:
Firmware Version:

Hi,

I'm considering buying the Archer BE400 to replace my ISP router (TELUS NH20A), which doesn't support NAT loopback.

My setup:

  • ISP: TELUS PureFibre 1.5 Gbps (Canada)
  • NAS: Synology DS224+ with DDNS

My goal is to access my NAS from inside my local network using its external DDNS address, without editing the hosts file on every device.

Before purchasing, can anyone confirm:

  1. Does the BE400 support NAT loopback / hairpin NAT?
  2. Is it enabled by default, or does it require manual configuration?

I've confirmed this works on the Archer AX73, but the BE400 seems like a better value right now. I just can't find a clear answer specific to this model.

Thanks!

  0      
  0      
#1
Options
1 Reply
Re:Does Archer BE400 (BE6500) support NAT Loopback / Hairpin NAT?
6 hours ago

  @psynth 

 

In general, NAT loopback if implemented, is enabled by default.

If you chose a model that doesn't have NAT loopback implemented, you can configure a local DNS server to resolve the external domain to the internal IP address.

Since you already have a Synology NAS, you can use it for configuring a Local DNS.

 
Steps for Setting Up DNS on Synology NAS:
  • Install Package: Open Package Center in DSM and install the "DNS Server" utility.
  • Create Master Zone: In DNS Server, go to Zones > Create > Master zone. Enter your domain name (e.g., home.lan) and the static IP of your NAS.
  • Add Records: Create A records to map local hostnames to specific IP addresses (e.g., nas.home.lan
    192.168.1.10).
  • Configure Resolvers: Enable Resolution in settings and add forwarders (e.g., Cloudflare 1.1.1.1 or Google 8.8.8.8) to handle external requests.
  • Configure Clients: Set your router or individual devices to use your NAS IP as the primary DNS server. 
 
Important Considerations
  • Static IP: Ensure your NAS has a fixed local IP address.
  • Port 53: The DNS server requires TCP/UDP port 53 to be open if using a firewall.
  • Backup: Set a public DNS server (like 8.8.8.8) as a secondary DNS on your clients to maintain internet connectivity if the NAS reboots.
 
Drawback
  • Using a NAS for DNS is highly beneficial for local, persistent domain resolution, particularly for managing home lab services, but it creates a dependence on the NAS for network connectivity.
If this was helpful click on the arrow pointing upward to make it blue. If this solves your issue, click the star to make it blue as a "Recommended Solution". Tips:149wubkkfoLmNDjDbiTxx4ZU8mpcMA5CJt
  0  
  0  
#2
Options