LAN DNS fails to configure - OC220 with adopted ER707-M2
Hi all, LAN DNS stopped working potentially after upgrading ER707-M2 v1.20 to 1.3.1 Build 20251009 Rel.67687 but cant be sure.
I also got the error below in the configuration, confirming that LAN DNS was nto configured. Any ideas?

- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
This happens a lot with v6 with gateway configurations. Just hit the "Apply Again" button and it usually sorts it.
- Copy Link
- Report Inappropriate Content
This happens a lot with v6 with gateway configurations. Just hit the "Apply Again" button and it usually sorts it.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
unfortunately it did not work. I am fairly confident the feature stopped working in the latest update. What is more, routing policies do not work anymore either. I will find the right place in the forum to notify tp link.
- Copy Link
- Report Inappropriate Content
On the early v6 builds, i did find a way to completely resolve it but its a bit of a pain
On the global dashboard, copy the site and call it like "zzzTest"
Then, move the gateway to the copied site. Once it finishes adopting and configuring there, you can move it back and all the failures should permenantly go away
Note - this will reset all the Port PVIDs on the gateway if you have set custom ones
- Copy Link
- Report Inappropriate Content
I followed the recommendation, which must have been useful somehow because in the network topology I got my failover WAN visible which wasnt before (see attached). I did get a cnfiguration error about LAN DNS again when tried to reenable an entry. I also still have no working policy routing (nor LAN DNS)..
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 66
Replies: 6
Voters 0
No one has voted for it yet.
