OPNsense 23.7.1-amd64 - Dynamic DNS client still broken (MULTI-WAN)

[Sakata_T]

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.

[AhnHEL]

For Namecheap:

Your hostname should be written with the domain ...... ip2.domain.com

Your username will just be the TLD......... domain.com

[Sakata_T]

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

[AhnHEL]

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

[franco]

> It's just putting the wrong IP in. Look at pics again.

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

[axsdenied]

If it helps, I'm using freedns as the Check ip method and it works

[Sakata_T]

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

[franco]

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.


Cheers,
Franco

[Sakata_T]

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.

[Sakata_T]

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

[dcol]

I use Cloudflare and it is working, but the 'Current IP' and 'Updated fields' are still blank. Never got them working.
Not sure why.

[AhnHEL]

@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.

[Sakata_T]

@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.

[franco]

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

[Sakata_T]

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?