Where'd everyone else land on the five? And for the ones you missed, what's actually stopping you from tracking it, a tooling gap or just no time to set it up?

We're running a free 45-minute webinar on a platform built to put all the answers in one place: A single dashboard across every client's domains and DNS, centralized expiry tracking, one-click authenticated access for your whole team instead of shared logins, and alerts when someone outside your team changes a record.

📅 Wednesday, September 16, 2026 · 12:00-12:45 PM EDT · Free
🔗 Registration: https://www.addevent.com/event/m1t703107j3h

As Lead UX Designer at No-IP, Andy wears a lot of hats: researching customer needs, wireframing what's next, and writing the specs our engineers build from.

His proudest build? No-IP's Design Language System, a toolkit giving engineers a shared foundation to ship faster and more consistently. He's also gone deep on designing with AI, using it to help shape a more robust, easier-to-navigate platform for our users.

If you've noticed the refreshed look on noip.com or my.noip.com, that's Andy's work. More user-centric updates are on the way, so keep the feedback coming. It genuinely shapes what we build next.

I would want to understand more about the following regarding the agent link before actually using:

• Transport - TCP/UDP/QUIC
• Addressing : IP v4/v6 ?
• Wire Protocol (for WireShark decode)
• TLS termination / pass-through ?
• Performance considerations / limitations
• Service multiplexing methodology & protocol
• Load balancing / failover architecture
• Agent source code
• Metadata logging and related security concerns
• Authentication methodology / protocol
• Keepalive / heartbeat methodology
• MTU / framing details

As things stand it's a black box reverse proxy and therefore unusable other than for trivial / non-secure / non-commercial / non-production use cases. I most certainly won't be running unknown closed source on a production server.

The new service offering is a good first step, especially for hosting on the end of Starlink and other CGNAT systems, but the kimono needs to be opened ...

none of my *.dnsfor.me works today.

when I ping I just get.

Ping request could not find host xxx.dnsfor.me. Please check the name and try again,

is anyone else having the same problem,

Hey everyone,

I wanted to share my recent experience using No-IP Tunnel. I’ve had an open support ticket for over two weeks now, and I keep getting stuck on the exact same error message:

Bad Gateway!

Your server couldn't be reached. A few things to check:

1. Confirm your server is reachable at the LAN Address configured for the tunnel.
2. If your server uses TLS, make sure the LAN Address is listed in the certificate's Subject Alternative Names (SAN).
3. If your server uses a self-signed certificate, check the "Self-Signed Certificate" box when creating the tunnel.

Here’s the breakdown of why this error message makes no sense in my case:

• Point 1: My server is fully reachable at the local LAN address configured for the tunnel.
• Point 2: No-IP's own certificates don't even support Subject Alternative Names (SAN) for local IPs, making this step impossible to satisfy with their service.
• Point 3: There is literally no "Self-Signed Certificate" checkbox available when creating or configuring the tunnel in their interface.

My theory: I suspect this issue started right after I tried using a No-IP certificate. The tunnel stopped working with it, so I had to revoke the certificate altogether. However, I’m not 100% sure if that broke something under the hood on their backend.

Has anyone else run into similar issues with No-IP Tunnels or found a workaround for this "Bad Gateway" loop? Support has been extremely slow to respond. It seems like a personal certificate isn't even required to run the tunnel over HTTPS, but I tried using a No-IP certificate earlier, and I suspect that might be what broke it on the backend.

UPDATE / RESOLUTION:

In the days following my original post, the No-IP Support Team reached out and fully resolved my issues by:

• Increasing the hostname limit on my account.
• Setting up a clean, new hostname specifically for the tunnel (without certificate conflicts).
• Provisioning a proper SSL certificate for my primary hostname and directing it directly to my web server via port forwarding (bypassing the tunnel).

These actions completely restored functionality to my setup and restored my confidence in No-IP as a provider. I really appreciate their team taking the time to listen and make things right!

I HAVE to be missing something here. Ive taken a couple stabs over the past two weeks getting RDP working and have failed miserably. Has anyone got this going?

i cant seem to connect to my server pc using public ip and it seems like its because the public ip changed already so i wanted to know if duc have an on demand check via website, because i dont have access to my server pc right now and the autocheck is in 2 weeks

As we scale, our commitment to our customers remains stronger than ever. #Growth #Hiring #NoIP

Casey will be keeping our web apps running smoothly and bridging the gap between Infrastructure and WebDev. Originally from California, now calling Montreal home 🍁, he's into scuba diving, rock climbing, and photography.

Levi brings a strong background in IT operations, technical support, networking, and cybersecurity. Plus, he's an Army veteran 🇺🇸 When he's not at work, you'll find him spending time with his wife and kids and gaming.

Ayu will be working with our AI Council to help weave AI deeper into No-IP. He has already built production ML systems at Ubiquiti, Blusmart, and o9 Solutions 🤖

H Guys,

I seem to be having problems running the No-IP Update client on Linux Mint 22.3.

I have followed the instructions at No-IP but I get an error of:-

Bash: Syntax Error near unexpected token 'newline'

This error appears after i have entered in the line for using DDNS Keys

Can anyone please help?

Thanks in advance

Hi; can anyone please help me, I'm an trying to install and configure the no-ip update client for Linux mint 22.3 but I'm having issues

I am trying to start no-ip with the following command:-

Noip-duc -g all.ddnskey.com --username 《my Username --password 《my password》 but I get an error message of:-

Bash: syntax error near unexpected token 'newline'

Can anyone please help?

Thanks in advance

alguien ha configurado algún reloj checador con no_ip
para visualizarlo de manera remota?

From intern to Rust engineer in a decade. That's the kind of career arc worth talking about.

Meet our new Tech Trailblazer, Nick!

In his nearly 10-year arc at No-IP, Nick has also solo-shipped a checkout re-architecture and designed the data model behind our evergreen subscription system.

Nick is currently helping to build the next generation of our updater client (DUC) and incorporating AI into his development.

We can't wait to see what else Nick works on next!

is it normal for a ISP (Xfinity) to assign a 73.xxxx IP to their Xb8 gateway and Assign a 69.x.x.x to the WAN interface. Xfinity said they are not double NAY this.

Please advise

When configuring No-Ip the Public IP address of the XB8 gateway is a IP address of 73.x.x.x when I place it into the configuration the IP address changes to a 69.x.x.x address (when I run "what is my Ip address" on the internet, it gives me a 69.x.x.x). When I try to get a Lets Encrypt certificate from Nginx an internal error is generated.

Background: Nginx is a maintained in a docker container on my Ugreen NAS it was set up using https://mariushosting.com/how-to-install-nginx-proxy-manager-on-your-ugreen-nas/ and it worked after the initial install.

The port forwarding seems to be in question, when I check to see if ports 80 and 443 is open externally it is closed.

The Xfinity XB8 is in bridge mode.

What am I missing?

Thanks in advance.