Having no success creating a 2 level DDNS domain using PFsense and Namecheap
-
I am trying to set up dynamic dns for a namecheap account. I have filled in the forms on both the namecheap site and pfsense. However, when I save the pfsense information, it shows that the DDNS entry is invalid (see image 1). I am trying to create a 2 layer subdomain, that is, the domain name is xxxxx.com (where xxxxx stands for the actual domain name) and I want a dynamic domain that matches *.home.xxxxx.com. I filled out the DDNS entry on Namecheap and it seemed happy with it. However, when I filled out the DDNS information on PFsense, it wasn't happy. Image 2 shows the Namecheap configuration and image 3 shows the PFsense configuration.
Can anyone suggest why this isn't working?
Thanks.
-
@dnessett Did you find the System Patches package and its patch "Fix Namecheap Dynamic DNS response processing (Redmine #12816)"? Namecheap has a bug in the response encoding causing it to be detected as invalid XML.
I have a hostname like that, xxx.yyy.example.com, with no issues. In Namecheap my domain is yyy.example.com and the host is xxx. If you're actually going for a wildcard (*.yyy.example.com) it looks like Namecheap lets you create a * hostname but have to point it to an IP. Perhaps you can create something else (dummyrecord.example.com) and create *.yyy.example.com as a CNAME for dummyrecord.example.com?
-
@SteveITS Thanks for the info. I am new to Netgate and PFSense (I just bought a Netgate 2100, which replaces an old router that I was using). So, I am unfamiliar with "System Patches", how you find them and how to apply them. Is there a tutorial on these topics?
-
@dnessett System/Packages in the menu, install System Patches. Then it’s on the System menu. They just very recently added a list of recommended patches.
https://docs.netgate.com/pfsense/en/latest/development/system-patches.html
-
@steveits Thanks!
-
@steveits Well, I applied the patch and tried once again to save the Dynamic DNS client configuration. However, I still get the red cross-out icon. Not sure how to proceed from here.
-
@dnessett What does it say in the system logs?
-
@steveits The error was: <Err1>No Records updated. A record not Found;</Err1>. I had changed "*.home" to simply "home" earlier in the day and got the same error. But, it took a while for the DNS cached entry to timeout. I waited for an hour and the configuration update succeeded.
-
@steveits Very helpful thank you. This got me going!