[crows]

Since changing from openvpn to wireguard my ddns is not working as it use to. The problem I have is when the ddns updates it uses the vpn IP rather than my wan IP.
I have a R7000 router running the latest firmware build


Thanks in advance

[egc]

Latest is a bit ambiguous, for me the latest build is 51937

DDNS can be set to use the external IP address (which can be the address of the tunnel) or to use the routers WAN address.
It is a setting in the DDNS interface: 'Use External IP Check'

[crows]

Thanks, I say latest because I updated today.

[dale_gribble39]

Still ambiguous, we will presume that you mean that you updated to 51937.

https://ftp.dd-wrt.com/dd-wrtv2/downloads/betas/2023/03-05-2023-r51937/netgear-r7000/

[crows]

I'm still having trouble, when my ip address changes the ip changes to my wan address and you can see it in the DDNS status area but it fails to connect to server or resolves hostname. I've updated to build 52006 and its the same. I've also tried another DDNS provider with the same problem.
It's a bit of hit and miss but it appears that if I disable wireguard the server updates.My wireguard has only one IP using VPN via PBR. Is there anything else I can try?

Thanks in advance

[egc]

It is not totally clear how you have setup.

As you are talking about PBR it looks like you have setup a WireGuard client to a commercial VPN provider?

Not clear what DDNS has to do with that other then that you should disable external IP check on the DDNS page, otherwise you run the risk that the DDNS is using your VPN IP address.

For what is DDNS used?

Please show a screenshot of your WireGuard setup

[crows]

Wireguard has been disabled for the last 3hrs, I rebooted my router which acquired a new WAN Ip
The DDNS updated to the new IP, so I believe wireguard is the culprit.

I have attached my wireguard setup, minus my keys.....i did follow the wireguard sticky setup and the VPN DNS sticky if that helps.

The single IP address(PBR) you see in my config is for my desktop computer.

The DDNS service is used for my security cameras, IP 192.168.1.90 if that helps

[egc]

WireGuard looks fine.

Unrelated but as you use Split DNS you can remove the DNS server from the "DNS Servers via tunnel" field (103.68.96.100), furthermore make sure the DNS server you are using for Split DNS (9.9.9.9) is not used elsewhere e.g. in Static DNS 1,2,3

I setup exactly the same as you did (although to Keepsolid) and my NoIP DDNS service updates fine, so at this moment I cannot reproduce your problem.

Note there can be up to 15 minutes between updates and it can take another 15 to 20 minutes before the DDNS provider has send your changed DDNS address to upstream resolvers.

[crows]

Thanks for looking over my config, I dont think its wireguard related, I think rebooting the router made me think it was wireguard but in reality wireguard tunnel probably didnt have enough time to bootup.

Anyway the issue is there even if I diasable wireguard all together, Ive been using this DDNS service without any issues for 5 years. Ive attached my DDNS config and the status report says cannot resolve hostname.

The last time this was working was when I was on build that stared with a 4, is it worthwhile downgrading to one of those builds to see if it works. The only other thing I did was to follow the VPN DNS sticky document and did the very basic configs (The ones that I understood)

On the off chance I upgraded to build 52020, I did mention I have a R7000 router.

Edit 1:- I have completely reset my router from scratch, the only details I have entered were my internet login details and the DDNS settings and its exactly the same.(Failed to resolve hostname) My question is it safe to downgrade to much earlier build? or can I add my ddns hostname somewhere in the config to make it recognise?

Edit 2:- I downgraded to build 50012 and it worked, Ill see if I can go up in builds before it breaks.

Edit 3 :- All builds after 50500 break my DDNS, I tested each build by factory reseting loading each build with default settings, entering my internet login details and DDNS settings until it broke. Hope there is a fix otherwise I'm stuck on this build.

Thanks in advance

[egc]

We have got a new Inadyn (DDNS) version, so things have changed.

I do not know if the wiki has been updated but for FreeDNS you do not need the "special key".
You just need username, password and hostname (the DDNS domain name) that is all.

If your router is connected directly to the internet you do not need "Use External IP Check" so set this to No.

My frustration:
It would have been much easier to detect if you could change the loglevel of Inadyn then Inadyn would point you to the problem.

A very small patch could do that but unfortunately it was turned down, I include it to show what simple patch could solve these kind of problems quickly.

[crows]

It actually did the same thing when using dynu systems...Anyway you saying I should be able to upgrade build to make those small changes and it should work.

[egc]

Yes that works for me and I am also using FreeDNS

[crows]

Thanks for your help, Ive updated and followed your instructions and it works.....what do I do with the startup script....where does it go and do I need it?

Thanks

[egc]

You do not need the startup script it is a patch you use when making your own builds, so you are good as it is