Why can't I use Linked IP with my configuration for my router?
I set up my Huawei router's DNS to NextDNS and changed DDNS to No-IP.com and configured it with NextDNS. But I'm still getting the message "This device is using NextDNS with another configuration". Anyone knows how to fix this?
I'm having same issue and pretty much the same setup. I am visiting wife's family overseas and decided to secure the network and improve performance. This is a new use case and I am really excited to use NEXTDNS - if it worked!
They have Huawei router: HG8245H.
1) I've tried DDNS with NO-IP to no avail. The Huawei interface shows UP status in the Huawei config portal under DDNS settings and the IP is properly managed in NO-IP web portal when it changes.
With that said..To me, everything checks out except NEXTDNS.
2) I've also tried just the two NEXTGEN primary/secondary DNS entry settings the old school way with no luck. These are the correct DNS servers after building the profile in the NEXTGEN portal.
There is one tidbit that hopefully helps NEXTDNS support team resolve our issue is that within NEXTGEN portal where the linkedIP and noIP DDNS entry sync properly and allow me to register accordingly. All my tinkering around I was making a ton of changes and noticed there was a lag time between router, noIP, and NEXTDNS synching new IPs on the NEXTDNS side of the house. Sometimes it wouldn't update at all indicating DNS cache. Since nothing was working at all, I deleted profiles and recreated using the new DNS entries and then updated the router with the new DNS IPs..still no go.
All the other devices pointed directly at NEXTDNS work just fine when assigned locally on windows, macos, and android. This is also when they are on the network via the Huawei connected behind the router because those devices have their own profile and are OK directly. However, I really would like the router level dns sinkhole stuff working for all unmanaged devices on the network as that is the main objective and why I purchased the new NEXTDNS service. That and I don't want to run my own pihole..
thank. you James. I am glad I stumbled into the post.
NEXTDNS support please advise?
FWIW, I removed the noIP DDNS from the picture altogether
Now both the linked IP updates along with the https://link-ip.nextdns.io/1a2b3c4d/e6f7g8 showing the google my IP they do match.
I guess that narrows it down to just noIP not respecting the DDNS config on the router to some fashion, because when turned back on the DDNSon huawei. the router public IP is. sync'd to noIP which then syncs to nextDNS OK, but its not the my 'google ip' , but the IP on the router shown here for #2 under WAN info is the one that shows up and sync'd
In either situation with or without dyndns it shows
This device is using NextDNS with no configuration.Make sure to link your IP address in the Linked IP section below. , but without noIP dyndns i have the greenlit check and the proper IP matching my google IP. where as with dyndns both nextDNS and noIP have the public interface IP in screenshot, instead of the different googled "my ip"
my next step is going to try the other ddns service. unfortunately my namecheap domain DDNS isn't supported by Huawei so I will try. another. duckdns doesnt show up in the Huawei drop down for DDNS either. i need to wait until EoD before I can test again with gnudip
Just curious, are you sure you're getting a public IP address instead of a CGN (carrier grade NAT) private IP address? if the later case is true, there's a chance that the IP address has already been binded by someone else sharing the same public IP. Binding IP address is always the last resort becasue it can easily go wrong and terribly hard to diagnose.
I wish I can can remove all my dumb comments. Although, this has been a great learning experience.
I restored my openWRT to fresh, got it back on the network, opkg update and ran the steps in the article you provided. https://github.com/nextdns/nextdns/wiki/OpenWRT
heres what I see in. log after going thru:
Unfortunately. still s tates: This device is using NextDNS with no configuration.Make sure you set the configuration ID shown below in the app settings.
confirmed in openWRT GUI under Services -> NextDNS is my config ID populated
Within OpenWRT, I can curl the programmatically update your linked IP by calling:
https://link-ip.nextdns.io/###### successfully showing my ip, but not greenlit still =(
thank ya peeps!
I got it! appreciate all your help!!
The noIP or duckDNS for DDNS on the newfi 3 running openWRT didn't work, same as attempting DDNS on Huawei HG8245H itself. Thanks to the comment about carrier grade NAT IP putting the DDNS wasn't working on either for that reason.
So the working solution:
huawei is bridged via LAN port to the openWRT. Huawei has the NextDNS IPs on the Huawei admin portal. DHCP running on huawei. Wifi disabled on the huawei and wifi running on openWRT instead. NextDNS happily running on the openWRT which was easy as you said. thanks again!
all unmanaged devices now pushed thru NextDNS. Agentless!! Are there benefits to running the NextDNS agent locally for additional security features?
On ANdroid, the NextDNS app wouldn't autostart or autoconnect. I managed to use macrodroid to autostart the app and then upon seeing text string "CONNECT" to make a UI interacted hand gesture. It was working fine, but decided to just use the private DNS mode in case someone closed the app.
thank you again!!!
may the force be with you