What's new

Router is Showing Repeated Hostname in DDNS

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

sne3zy

Occasional Visitor
I am beginner to intermediate on web architecture topics like DNS and DDNS, so I know what a certificate is, but I don't know what it actually is... if you know what I mean. Anyways, now that I've set the expectations for my knowledge level, I have an Asus GT-AX6000 running merlin 386.7_2. I've thrown spaces in the sample names because it wouldn't stop linking them.
  • I own my own domain, let's call it domain. tld
  • My registrar (namecheap) has DNS record management, and I created 'A' records + DDNS in order to perform DDNS on hosts 'www' and '*' for wildcard.
  • My router has namecheap as one of the default options in the DDNS menu for 'server'
  • I've configured the router's DDNS to use:
    • server = www. namecheap. com
    • host name = www. domain. tld
    • domain name = domain. tld
  • I've used the correct DDNS key
So, with all of this I can get the free certificate from Let's Encrypt, and it shows as status = active and expires next year. The certificate is issued to www. domain. tld and the SAN field is www. domain. tld. SAN is storage area network, right? So I don't know why that's in there.

Now, on the router homepage, it shows:
  • Internet Status: connected
  • WAN IP: it has an IP
  • DDNS: www. domain. tld. domain. tld
I would figure this means I shouldn't set the host name as 'www. domain. tld' in the DDNS settings, but should set it as just 'www', in this case where I'm calling the router as the 'www' host. But if I do that, Let's Encrypt won't issue a certificate, and the status for the Webui SSL certificate shows as 'authorizing' and never resolves.
 
Last edited:
I don't know if this is just a bug in Asuswrt or merlin for how the DDNS is displayed on the home page, because when I browse to my domain on the http port, using just 'http://www. domain. tld: httpport', the traffic appears to be routed correctly. It also appears to be routed correctly when using https as 'https://www. domain. tld: httpsport'
 
Last edited:
All my Let’s Encrypt certificates are only valid for 90 days.

How did you get one that expires in a year?
 
Mine is for 90 days also. 90 days from now is in 'next year', so technically my word choice was correct. ;)
 
I am beginner to intermediate on web architecture topics like DNS and DDNS, so I know what a certificate is, but I don't know what it actually is... if you know what I mean. Anyways, now that I've set the expectations for my knowledge level, I have an Asus GT-AX6000 running merlin 386.7_2. I've thrown spaces in the sample names because it wouldn't stop linking them.
  • I own my own domain, let's call it domain. tld
  • My registrar (namecheap) has DNS record management, and I created 'A' records + DDNS in order to perform DDNS on hosts 'www' and '*' for wildcard.
  • My router has namecheap as one of the default options in the DDNS menu for 'server'
  • I've configured the router's DDNS to use:
    • server = www. namecheap. com
    • host name = www. domain. tld
    • domain name = domain. tld
  • I've used the correct DDNS key
So, with all of this I can get the free certificate from Let's Encrypt, and it shows as status = active and expires next year. The certificate is issued to www. domain. tld and the SAN field is www. domain. tld. SAN is storage area network, right? So I don't know why that's in there.

Now, on the router homepage, it shows:
  • Internet Status: connected
  • WAN IP: it has an IP
  • DDNS: www. domain. tld. domain. tld
I would figure this means I shouldn't set the host name as 'www. domain. tld' in the DDNS settings, but should set it as just 'www', in this case where I'm calling the router as the 'www' host. But if I do that, Let's Encrypt won't issue a certificate, and the status for the Webui SSL certificate shows as 'authorizing' and never resolves.

I haven't used namecheap DDNS, but my guess is host name should just be www, that's why you're getting duplicate domains.

The reason it is working is because you have wildcard enabled most likely, or you're just using your local DNS and resolving using your internal IP.

On my DDNS provider it only asks for domain which is the whole A record, it looks like namecheap is splitting it up. Try it with just www in hostname and domain.tld in domain name.

SAN is Subject Alternative Name, it is a field that lets you have multiple hosts/domains in a single certificate, in your case you only have one so that is fine (that field could be empty but most populate it with the same as the certificate even when there are no additional names needed).
 

Similar threads

Latest threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top