OpenWRT DDNS: Difference between revisions

(3 intermediate revisions by the same user not shown)

Line 20:

opkg update

Client: opkg install ddns-scripts ddns-scripts-nsupdate luci-app-ddns wget curl *

Client: opkg install ddns-scripts ddns-scripts-nsupdate luci-app-ddns wget curl bind-nslookup ip-full (Reboot after installation)

Server: opkg install bind-server bind-tools (bind-tools includes: bind-rndc bind-check, plus dependencies are all installed)**

If it isn't obvious, the client ~~and server~~ software will ~~not~~ be installed on ~~the same router as DNS server software such as~~ BIND / NAMED ~~rely on having~~ a static IP Address assigned to the ~~OS they're installed on~~.

If it isn't obvious, the client software will be installed on different devices. The Server will be running BIND / NAMED and should also have a static IP Address assigned to the WAN interface.

See the BIND / NAMED section in this [[Linksys AC Series Router Configuration Tips for OpenWRT#DNS ( BIND / NAMED )|article]] for additional information on configuration.

Line 34:

<nowiki>*</nowiki> This OpenWRT [https://openwrt.org/docs/guide-user/services/ddns/client article] discusses and addresses several subjects related to WGET and CURL.

<nowiki>**</nowiki> It is necessary to disable the DNS functionality of DNSMASQ for BIND / NAMED to function properly. If DHCPD is used, and none of DNSMASQ's functionality is necessary, it is highly recommended to remove DNSMASQ instead of disabling it. Odd issues seem to crop up if it remains installed, even if disabled.

<nowiki>**</nowiki> It is necessary, on Server installation to disable the DNS functionality of DNSMASQ for BIND / NAMED to function properly. If DHCPD is used, and none of DNSMASQ's functionality is necessary, it is highly recommended to remove DNSMASQ instead of disabling it. Odd issues seem to crop up if it remains installed, even if disabled.

====Directories and Configuration File Locations====

Line 423:

Error loading shared library libbind9-9.18.7.so: No such file or directory (needed by /usr/bin/nsupdate)

</syntaxhighlight>Try reinstalling the bind-libs package: opkg update bind-libs (or remove it and reinstall it, etc.)

Also make sure nslookup is installed: opkg install bind-nslookup

Oh, and just noticed (because generally BIND / NAMED is installed on all documented OpenWRT Routers, not DNSMASQ, it looks like full blown BIND / NAMED must be installed too with DNSMASQ disabled for the Network and Interface Method(s) to function.

===Script Error for NSUPDATE (and possibly other scripts too)===

@@ Line 20: / Line 20: @@
 opkg update
-Client: opkg install ddns-scripts ddns-scripts-nsupdate luci-app-ddns wget curl *
+Client: opkg install ddns-scripts ddns-scripts-nsupdate luci-app-ddns wget curl bind-nslookup ip-full (Reboot after installation)
 Server: opkg install bind-server bind-tools (bind-tools includes: bind-rndc bind-check, plus dependencies are all installed)**
-If it isn't obvious, the client and server software will not be installed on the same router as DNS server software such as BIND / NAMED rely on having a static IP Address assigned to the OS they're installed on.
+If it isn't obvious, the client software will be installed on different devices.  The Server will be running BIND / NAMED and should also have a static IP Address assigned to the WAN interface.
 See the BIND / NAMED section in this [[Linksys AC Series Router Configuration Tips for OpenWRT#DNS ( BIND / NAMED )|article]] for additional information on configuration.
@@ Line 34: / Line 34: @@
 <nowiki>*</nowiki> This OpenWRT [https://openwrt.org/docs/guide-user/services/ddns/client article] discusses and addresses several subjects related to WGET and CURL.
-<nowiki>**</nowiki> It is necessary to disable the DNS functionality of DNSMASQ for BIND / NAMED to function properly.  If DHCPD is used, and none of DNSMASQ's functionality is necessary, it is highly recommended to remove DNSMASQ instead of disabling it.  Odd issues seem to crop up if it remains installed, even if disabled.
+<nowiki>**</nowiki> It is necessary, on Server installation to disable the DNS functionality of DNSMASQ for BIND / NAMED to function properly.  If DHCPD is used, and none of DNSMASQ's functionality is necessary, it is highly recommended to remove DNSMASQ instead of disabling it.  Odd issues seem to crop up if it remains installed, even if disabled.
 ====Directories and Configuration File Locations====
@@ Line 423: / Line 423: @@
 Error loading shared library libbind9-9.18.7.so: No such file or directory (needed by /usr/bin/nsupdate)
 </syntaxhighlight>Try reinstalling the bind-libs package: opkg update bind-libs (or remove it and reinstall it, etc.)
+Also make sure nslookup is installed: opkg install bind-nslookup
+Oh, and just noticed (because generally BIND / NAMED is installed on all documented OpenWRT Routers, not DNSMASQ, it looks like full blown BIND / NAMED must be installed too with DNSMASQ disabled for the Network and Interface Method(s) to function.
 ===Script Error for NSUPDATE (and possibly other scripts too)===