ER605 v2.0 (Firmware 2.0.1) DNS Server Auto - not working

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

ER605 v2.0 (Firmware 2.0.1) DNS Server Auto - not working

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
ER605 v2.0 (Firmware 2.0.1) DNS Server Auto - not working
ER605 v2.0 (Firmware 2.0.1) DNS Server Auto - not working
2022-09-29 00:41:27
Tags: #NAT #DHCP Service #DNS Server auto
Model: ER605 (TL-R605)  
Hardware Version: V2
Firmware Version: 2.0.1

I bought this router to get to know the omada system.

 

Right from the beginning, I had issues as all devices told "no internet connection" - ping to a IP address worked, however the dns service didn't (if the default option is used).

 

Only when I manually entered DNS Servers to be used for the local Networks, this system started to work as intended.

 

my setup:

I have a 4G router for internet. The ER605 is connected via the wan port to the 4g router. (the 4g router works without problems - DNS, WIFI, LAN...)

On the ER605 (omada):

Site Settings > Wired Networks > LAN > Create New LAN

I enter VLAN, Gateway/Subnet and leave DNS Server to Auto

 

-> when I connect a PC to this lan: The pc complains about missing internet access.

received dhcp settings: ip address from the DHCP Range and DNS is the Ip-Address of the Gateway as configured earlier) -> so far so good -> but DNS seams to cause a problem!

On web-pages - i receive ERR: Name not resolved ...

 

Solution: change the settings of "DNS Server" from auto to static ones -> entering the gateway ip address from the 4G router is already sufficient!

 

This problem solving took me 2 days, Could you please solve the issue with the aut DNS Server as this is a really bad behavior for such a product!

 

There was already a similar topic: https://community.tp-link.com/en/business/forum/topic/269830

Is this still a problem of the router?

 

 

  1      
  1      
#1
Options
9 Reply
Re:ER605 v2.0 (Firmware 2.0.1) DNS Server Auto - not working
2022-09-29 04:57:20

  @herwig 

 

That's a common issue for double NAT network. If you make your Modem as a pure modem them no issue on this thing.

 

But yes I also agree there could be some improvement on the router page, like a warning or suggestion

  1  
  1  
#2
Options
Re:ER605 v2.0 (Firmware 2.0.1) DNS Server Auto - not working
2022-09-29 11:25:12 - last edited 2022-10-13 10:06:04

EDIT

  1  
  1  
#3
Options
Re:ER605 v2.0 (Firmware 2.0.1) DNS Server Auto - not working
2022-09-30 19:01:04

  @Somnus thx for the info.

 

It is really weird that by default the ip address of the gateway is published to the clients and the gateway does not run a DNS Server.

Forwarding the ip of the upstream DNS would be a solution for most cases, however if you want to have multiple WANs, there is no way around a local DNS Server.

 

Using the router as a "Switch" is no option either -> in this case, there is no need for the router at all...

 

It is strange that this basic functionality is not managed by tp-link as this is a vital feature which all - even the cheapest routers - provide ...

 

What I also find confusing is that I watched a lot of setup videos before selecting omada and I do not remember that this issue has ever been addressed ...

 

I guess the most vise setup would be to have a raspberry with Pihole and the omada controller running ... -> would be cheaper than the OC200 and support the "special" functionality of having a local DNS server

 

really strange move from tp-link ...

 

this is not the easy setup that I expected ...

  1  
  1  
#4
Options
Re:ER605 v2.0 (Firmware 2.0.1) DNS Server Auto - not working
2022-09-30 19:09:07

  @btx thx for your answer.

 

I totally agree, it is a shame that such a vital functionality does not even not run out of the box but that it is not even mentionied that there is a problem.

 

concerning the auto dns in LAN:

 

This is the case that I use. In this case, the devices receive the ip-address of the gateway as dns-server -> which is very strange as there is - as you mention - no dns server running ... -> does not look like a professional solution to me!

 

Using the router as a switch does not make any sense as this would eliminate the whole failover and routing functionality - which is one of the main reasons for this architecture.

 

very disappointed ...

  1  
  1  
#5
Options
Re:ER605 v2.0 (Firmware 2.0.1) DNS Server Auto - not working
2022-10-01 22:29:15 - last edited 2022-10-13 10:06:14

EDIT

  1  
  1  
#6
Options
Re:ER605 v2.0 (Firmware 2.0.1) DNS Server Auto - not working
2022-10-02 16:02:36

  @btx 

to be honest, I still believe that I miss something - such basic functions should work out of the box ... specially for a company with networking knowledge and capabilities like TP-link

 

their consumer products do support all these features. There is absolutely no reason why the business devices have less capabilities!

 

 

  0  
  0  
#7
Options
Re:ER605 v2.0 (Firmware 2.0.1) DNS Server Auto - not working
2022-10-03 04:26:04 - last edited 2022-10-13 10:06:22

EDIT

  0  
  0  
#8
Options
Re:ER605 v2.0 (Firmware 2.0.1) DNS Server Auto - not working
2022-10-09 11:39:27

My solution:

 

I run the omada controller on a vps - nothing fancy is required (in my case I have a local vps with 2CPUs, 2GB Ram and 10GB HDD).

 

The omada controller is installed as a docker instance.

In addition to the omada controller, I also run a pihole with the docker-compose file as described here: https://hub.docker.com/r/pihole/pihole

I configured the primary DNS to be the ip of my omada controller (which is also the pihole). The secondary DNS Server is configured to be the one from cloudflair.

 

So far this setup works good ... no problem so far.

 

regards

 

  Herwig

  0  
  0  
#9
Options
Re:ER605 v2.0 (Firmware 2.0.1) DNS Server Auto - not working [software but] [workaround found]
2022-10-25 22:02:17

 @Somnus 

@btx 

 

I got suggestions for further testings ... What I figured out is that if you set 1.1.1.1 and 8.8.8.8 as DNS-Servers for the WAN interface, also the LANs (which are set to DNS auto) work without a problem - the router does forward the DNS requests correctly - as it should!!

 

In my case, after the test as described earlier, I set the WAN DNS-Server to the IP of the standard gateway from the WAN interface (which was also provided by DHCP) which is connected to the WAN interface of the omada router. -> this worked as well ...

 

After this test, I deleted the (optional) DNS-Setting from the WAN interface -> which defaulted back to the IP of the upstream gateway again -> and also this setting worked now!!!

 

There seams to be a software bug that in some cases, this setting works and in other cases, it does not ... -> I hope a developer will find this thread to solve the problem in near future!

 

Suggested workaround if you encounter the issue that DNS seams not to work:

1. set the WAN DNS-Server to static IP addresses e.g. 1.1.1.1 or 8.8.8.8 (or both) -> apply changes and verify if they work

2. remove these (optional) settings -> apply changes and verify if this works ...

  3  
  3  
#10
Options

Information

Helpful: 1

Views: 4303

Replies: 9

Tags

NAT DHCP Service
DNS Server auto
Related Articles