We have a RUT955 (192.168.1.1) running 00.06.07.5 and are experiencing DNS issues on the LAN.
From the RUT955 we can resolve iot.beans.be (uses the DNS configured through CLI, as the GUI wasn’t working). A LAN client with DNS configured as the RUT955 in unable to resolve iot.beans.be.
On the LAN device, when we do a nslookup iot.beans.be the server is RUT955.lan and address 192.168.1.1 and it gives the following error;
No internal type for both IPv4 and IPv6 Addresses (A+AAAA) records available for iot.beans.be
Is there something I can check or am I missing a piece of configuration?
Is the issue specific to iot.beans.be or it fails to resolve other hostnames as well? What DNS servers are you using? You can check the DNS servers used via the following command:
You can try disabling DNS rebind protection in the DNS settings. This helps if the DNS returns a private IP address.
Also, you can try using DHCP option 6 to push a DNS server to LAN clients instead of relying on RUT to forward them. If you push the DNS servers to the LAN clients directly, are they able to resolve the hostname properly?
Additionally, the firmware version you are using is quite old. Therefore, I would suggest updating the firmware if it is possible. Since the differences between your current firmware and the new one are quite subtantial, you would have to update the device with the ‘keep settings’ option disabled, and reconfigure the device manually.
I updated the firmware to 6.9.5 and now it seems to work fine. So possibly a firmware issue indeed.
This topic was automatically closed after 15 days. New replies are no longer allowed.