Messages

https://forum.opnsense.org/index.php?topic=34139.0

What I find odd is that the ddclient interface seems to indicate it *does* see the different IP addresses.
I'm guessing that on the backend it is getting IP information from somewhere that is disconnected from the rest of the UI?

I'm having a similar issue and got referred over here.

@tiermutter -- did your interface show the correct IPs while having the issue, but still update the provider incorrectly?

I'm having the same issue on namecheap being updated with the wrong address, but I'm not 100% sure it's the same issue under the hood (I think they've done some updating to the client?). See the screenshot - they show correctly on it.

I'll still give the workaround you supplied a shot - wondering if the plugin is presenting data one way and getting it wrong during submission.

@Sakata_T

Using Namecheap myself and its working and updating all 4 of my Opnsense sites correctly within Opnsense AND Namecheap.  Something is misconfigured or just different on your end with the Dual WAN.  Cheers.


Edited to note response was to @Sakata_T.

Do you have more than one WAN? Your screenshot seems to indicate you have one WAN.

I think that the plugin, despite showing the correct information, is updating namecheap with just one of the WAN IPs which is not desired - I have two WANs and while they do have failover, they're generally dedicated for specific purposes under normal operation.

Before the plugin change, this fucntionality worked as expected without any issue.

Any update to this, or is the service to remain broken?

No no no, the pic make more sense without your "it's the wrong IP" because the IPs seem to be the same as updated and shown.

So either the picture is right and you are wrong or the picture is wrong and you are right, but it's unclear what separates the first case from the second.

You will have to make an effort for a reproducible bug report.

And here I'd hoped that the pictures would make this easier, as they look pretty obvious.

Picture 1 is of the WAN IPs from the dashboard. They are as expected, correct.

Picture 2 is from Services: Dynamic DNS: Settings. Note that ip1 is listed with wan1's IP, starting with 71.77 and ip2 is listed with wan2's IP of 162.203. They are also correct, so the plugin knows what the hosts are supposed to be.

Picture 3 is from Namecheap. Despite the plugin showing the correct values for ip1 and ip2, the plugin updated namecheap with both values pointing to wan1 IP. Which is incorrect. (Nothing updates the root, which is why @ is 'correct' - it was manually set)

I'd hoped that before the change removing the older DDNS client (that worked fine), this one would be working. Hopefully this regression can be resolved soon.

Did it occur to you that you have it not configured correctly? Probably wrong "Check ip method"...

It did occur to me. In the pics (assuming it occurred to actually look at them) the IPs are correct. I'd have had a completely different set of questions if the plugin itself didn't show the correct IPs indicating that it is aware of the correct IP addresses....

I'm thinking in Namecheap Advanced DNS, I would remove the @ symbol for Host entry so your subdomains can individually update their IPs.

If I remove @, then I can't resolve the root domain. It isn't a wildcard, FYI. Just points to mydomain.net, not anything.mydomain.net

Yeah, I know this. It is working and updating.
It's just putting the wrong IP in. Look at pics again.

Keeping on top of this as it's still busted and I'd really like for it to be fixed:
Attached screenshots that describe the issue much more clearly than words, without a dissertation.

Update - apparently dissertation was needed. Also updated the topic to indicate that this affects multi-wan setups, not single-wan.

Picture 1 is of the WAN IPs from the dashboard. They are as expected, correct.

Picture 2 is from Services: Dynamic DNS: Settings. Note that ip1 is listed with wan1's IP, starting with 71.77 and ip2 is listed with wan2's IP of 162.203. They are also correct, so the plugin knows what the hosts are supposed to be.

Picture 3 is from Namecheap. Despite the plugin showing the correct values for ip1 and ip2, the plugin updated namecheap with both values pointing to wan1 IP. Which is incorrect. (Nothing updates the root, which is why @ is 'correct' - it was manually set)

I'd hoped that before the change removing the older DDNS client (that worked fine), this one would be working. Hopefully this regression can be resolved soon.

Since last topic got hijacked with VPN stuff that doesn't seem related to this issue, and the issue persists several updates since, remaking this post as a new one.

Since the update to 23.1 early May, the Dynamic DNS is not functioning as it should.

I have 2 WANs, from different carriers. Both are DHCP. I do a lot of work where I'm not in the office, and need to be able to reach the correct WAN reliably.

The Current IP is showing correctly on the status page of the service, but the IPs that are sent to NameCheap are
incorrect. Despite the correct IPs being listed on the settings page for the service, NameCheap is being updated for both "ip1.myoffice.net" and "ip2.myoffice.net" with the IP of WAN1.

I've now lost access to access to WAN2 several times. Each time was due to thinking that an update that was recently pushed has hopefully resolved this issue, turned the DynDNS service back on, and then having it set the records for IP2 to WAN1 instead of WAN2.  Since it often shows that the service appears to be working correctly when I turn it on, I leave it - only to find that at some point it decides to do... whatever it's doing when it breaks.

Is this on the radar to be fixed soon?

Just server instance. No clients

Wondering if my posts for this thread are going through, I'm seeing the IP correct now in the panel but when the thing updates my DNS record, it still assigns the wrong IP.

Not sure that this is related to the OpenVPN stuff that is mentioned, but for me at least it seems that the ddns system is choosing a different IP even if the plugin is working for detecting the right IP, at some point in the process it isn't using the data it already has.

Hoping this is being looked into?  If there is any information I can provide, I'm happy to do so, just let me know what is needed.
Manually editing the nameserver by hand is not exactly optimal, as I'm depending on the firewall already being updated for roadwarrior VPN which I can't exactly do without getting my IP to connect to first.
Thankfully I have an annoying but usable workaround, but would at least like to know this is on someone's radar to be re-fixed.

I think something else is also going on. I reboot the firewall again, and I noted in the logs that despite having NameCheap selected, it keeps showing this in logs:

Code Select Expand

CONNECT: dynamicdns.park-your-domain.com
WARNING: cannot connect to dynamicdns.park-your-domain.com:443 socket: Name does not resolve IO::Socket::IP configuration failed


Not sure where that comes from...

Also at some point the thing did manage to update the WAN2 DNS to WAN1 IP... again.

switched the setting to 'freedns' which seems to have worked, but now the service shows as not running, and 'starting' it doesn't work. Interestingly, the logs show it is running...

It's been set to interface since switching to the new DDNS system, and has worked thusfar.