npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

node-red-contrib-duckdns

v0.0.2

Published

Node-RED Node to update Dynamic DNS domains from DuckDNS

Downloads

22

Readme

node-red-contrib-duckdns

Node-RED node to update Dynamic DNS domains on DuckDNS, using its API.

Configuration

All the configuration for the node can be set up on the node itself, or as keys of the injected message (e.g. the "token" can be sent through msg.token). The message-provided configurations have more priority than those defined on the node itself.

  • token (required): the DuckDNS user token.
  • domains (required): the domains to update. Multiple domains can be updated at the same time, specifying them comma-separated. The domains do not need to have the ".duckdns.org" part.
  • ip: the destination IP for the domain/s. Can be a IPv4 or IPv6. When this property is not set, nor configured on the node, DuckDNS will autodetect the IP (from where the request was performed).
  • ipv6: the destination IPv6 for the domain/s. If set, the IP autodetection is disabled.
  • clear: if true, clear the IP address/es already assigned to the domain/s.
  • verbose: if true, make DuckDNS return a verbose response, which is returned as the payload output of the node.

Examples

DuckDNS

The typical configuration is based on calling the DuckDNS API periodically, providing just the token and the domain/s to update. The API will automatically detect our public IP address, and update our domains if the IP changes.

example1

The message injected into the DuckDNS node can contain configuration fields, which will replace those configurated on the node itself, if specified:

example1-configuration-msg

Public IP + DuckDNS (on change)

To be more efficient, we could use a GET Public IP service to get our public IP, and if it changes, ask DuckDNS to update our domain/s. This can be useful to also notify us (somehow) whenever the IP changes.

example2

Changelog

  • 0.0.2
    • fix "PublicIP + DuckDNS (on change)" example (reverse the msg.payload -> msg.ip variable assignment node)
    • update description in package.json to reference that this is a Node-RED Node
  • 0.0.1
    • initial release

TODO

  • Improve format of node configuration (HTML)
  • Return a parsed object message payload when verbose=true
  • Add tests