ddns – Purchasing a domain name and pointing to a dynamic IP

I designed a small hardware device that will need to periodically check for updates over wifi. I am looking into getting a proper domain name, as currently I am using one of the free ones from noip that requires confirming every 30 days.

The free domain from noip works well as my modem/router has support for their services built in. Looking through their site, it’s not immediately evident if purchasing a top level domain will allow me to have it updated when my IP changes as the free one does.

I am wondering if I am comparing apples with oranges here… Is the “free hostname” the same as a paid domain name in terms of supporting dynamic dns?

When I look into their “enhanced dynamic dns” service, I still have to pick from a list of subdomains, I can’t seem to enter my own .org. Then when I click on the “domains” service, I can enter exactly the domain name I would like.

What am I missing?

linux – How do I configure subdomains with NGINX and DDNS

I have registered a ddns subdomain on No-IP:example.ddns.net
I configured No-IP to map to my router’s IP which forwards the port to my NGINX web server. I want to have a separate web server that I hosted on web1.example.ddns.net which points to /var/www/web1. What I don’t know is how to tell NGINX to point to /var/www/web1 when calling from web1.example.ddns.net. Can anyone give me a detailed explanation on how to configure my server?

Below is my configuration for example.ddns.net this config is located at /etc/nginx/sites-available/ there is a link to /etc/nginx/sites-enabled.

server {
        listen 80 default_server;
        listen [::]:80 default_server;
       
        root /var/www/example.ddns.net;

        server_name example.ddns.net;

        location / {
                # First attempt to serve request as file, then
                # as directory, then fall back to displaying a 404.
                try_files $uri $uri/ =404;
        }

}

Below is my configuration for web1.example.ddns.net this config is located at /etc/nginx/sites-available/ there is a link to /etc/nginx/sites-enabled.

server {
        listen 80 default_server;
        listen [::]:80 default_server;
       
        root /var/www/web1.example.ddns.net;

        server_name web1.example.ddns.net;

        location / {
                # First attempt to serve request as file, then
                # as directory, then fall back to displaying a 404.
                try_files $uri $uri/ =404;
        }

}

These are the only files I have changed. The following NGINX server is hosted on Ubuntu Server and I am accessing the server via ssh and accessing the webpage through a separate computer.
Can any one give some instructions on how to fix this problem?

Does my ISP give me free DDNS service?

Recently when doing a reverse IP lookup on my own ip address I noticed that my hostname was set as [insertAccountNameWithISPhere].plus.com when I go to plus.com it redirects to Plusnet who is my ISP. Seeing as we have a static ip address and when I turn on my router then turn it off again the link still redirects to my ip address.

Note: I have redacted the account name for privacy.

Do other ISPs provide this service? Are they mandated to in the United Kingdom? Why do they do this?

Thanks

Domain Name System – Configure ddns and slave master zones with update-policy

I'm trying to configure ddns and master-slave zones and I wondered how to do this with the update-policy directive in the link configuration. I read bind docs and configure this:

zone "tech.com" {
master type;
allow-transfer {192.168.155.2;};
update-policy {
grant dnsupdate. name _acme-challenge.tech.com txt;
attribution 192.168.155.2 name * A;
};
notify yes;
file "/var/lib/bind/tech.com";
};

Is this the correct config? This zone is external, maybe I should use the public IP address for the DNS update?

I need the 192.168.151.1 master to send serials and zone updates to 192.168.155.2. And also certbot obtains certs with the dnsupdate key.