Accessing duckdns URL in LAN

Installing and Using OpenWrt
1

Until recently I was able to connect to my local server using its public url (duckdns.org). I then replaced the router (Orange Pi R1) with a chromebox (x86 system with USB ethernet adapter for WAN). Both have OpenWrt v23.05.5.

Since using the chromebox as the router, the one computer connected to LAN via ethernet cable through an unmanaged switch is not able to access the local server (also connected to the unmanaged switch) using the duckdns url - connection times out.

As a test, I reinstalled v23.05.5 on both the chromebox and orange pi and installed only drivers and the bare minimum of packages

  • bind-host
  • ca-certificates
  • curl
  • luci-app-ddns

With the orange pi back in place, accessing the server through the duckdns url works from the ethernet connected computer. Replacing the orange pi with the chromebox prevents the computer from reaching the server using the duckdns url. What is odd is that all WLAN connected devices are able to access the server through both the orange pi and the chromebox.

I configured the same port forwarding rules on the orange pi and the chromebox and the DNS configurations are identical.

I have seen posts like Duckdns url inside LAN but I don't understand why I can access the server without making any changes to the DNS when using the orange pi.

Any ideas on what setting I overlooked to be able to connect to the server on the LAN with the duckdns url? I have not been able to figure out the difference in configuration defaults on the orange pi and the chromebox that might be contributing to this difference in behaviors.

2

Because you get your old public IP back with the Orange, while you get a new one with the Chromebox, and the update won't populate across internet before you switch back?

Try cloning the WAN MAC of the Orange onto the WAN port of the Chromebox.

You could also tell dnsmasq to resolve your FQDN locally, to avoid this problem all together.

image
image1428×258 25.3 KB

3

@frollic ddns updates my public IP when openwrt boots so I don't think that was the issue. I did also try cloning the MAC so that the chromebox would pick up the same IP as the orange pi but that still gave me issues.

So my statement about doing a clean install with minimal packages was not quite true. Turns out that there were still other packages in my install script but I managed to narrow down the package that was resulting in the difference in behavior - dockerd.

Eventually I will probably need to implement the change to dnsmasq in order to be able to make the server accessible locally only using https.