HEADS UP: DynDNS changes need testing (mostly Namecheap)


  • Rebel Alliance Developer Netgate

    In order to resolve #4366 (Namecheap Dynamic DNS updates fail on subdomain formatted domains), I had to split the Namecheap DynDNS fields up in the GUI so they get a separate hostname and domain part.

    The changes touched a lot of areas in the DynDNS code due to many places assuming that there was only a hostname, so it will be helpful to get feedback from all types.

    The splitting of the host domain for existing Namecheap entries will be done automatically on upgrade. Future entries will need them entered separately.

    Note that the Domain Name field is what Namecheap believes it to be, meaning it's more like a zone name.

    If you have delegated a subdomain to Namecheap, then use the full subdomain in the Domain Name field. If you have a plain domain name at Namecheap (not a sub), and you want to update a "subdomain" style record you made up, that must still be placed in the hostname (e.g. myhost.sub / example.com, rather than myhost / sub.example.com )

    What it boils down to is, if you look in the Namecheap DNS config on their site, the hostname portion of the record must match the hostname field in the entry on pfSense.

    Hopefully that should take care of the last of the edge cases people had with updating Namecheap entries.



  • Just tried the update.  I use NameCheap for DynDNS.

    The widget on the front page shows:

    WAN Namecheap home N/A 15:57:00

    This doesn't seem right?

    But the DynDNS status page show my entries as green.


  • Rebel Alliance Developer Netgate

    Ah, the widget, I knew I'd forget something!

    I'll fix that up.


  • Rebel Alliance Developer Netgate

    Just pushed a fix. Should be OK once it's in a snap (or gitsync in a few minutes to get it)



  • Looks good to me.  My NameCheap DynDNS appears to be all working as it should.

    Thanks


  • Rebel Alliance Developer Netgate

    great, thanks!

    Now I just need to hear from some others that don't have Namecheap, or someone that has a subdomain forwarded to namecheap like in the original post.



  • just tested with No-IP (free), working fine



  • I added entries for Google Domains and HE.net DNS (not tunnelbroker)… Google Domains caused a NGINX Gateway timed out message when saving (though it did save) and the web gui was slow to respond for a bit after... HE.net DNS seemed to go fine. I haven't added the widget to my dashboard. I know Google Domains is new to 2.3... so maybe there's something up there unrelated to your changes.


  • Rebel Alliance Developer Netgate

    Hmm, well unless you had them in at a point before you upgrade to a snap with this code it's not as useful to know, since it's not clear if the issue was already there.