TL-R605 with OC200 cannot resolve internal network names

TL-R605 with OC200 cannot resolve internal network names
TL-R605 with OC200 cannot resolve internal network names
2021-01-31 13:45:28
Hardware Version: V1
Firmware Version: Rel. 36519

Hi,

right now I only have one internal LAN (even on the standard VLAN). If I use the DHCP of the TL-R605 I get on the connected machines also the IP Adress of the TL-R605 as DNS Server (which is default if you set DNS to auto). But the TL-R605 is not able to resolve hostnames to which he gave IP adresses via DHCP. How to enable such a behavior?

As a workaround I am using now a Raspi with DNSMasq for DHCP and DNS but is this really the only solution?

Thanks and Kind Regards

Marco

11
11
#1
Options
18 Reply
Re:TL-R605 with OC200 cannot resolve internal network names
2021-05-24 14:36:05

@MarcoE I have the exact same issue and I'm rather surprised that this functionality seems to be missing!

1
1
#2
Options
Re:TL-R605 with OC200 cannot resolve internal network names
2021-08-15 18:08:51

@MarcoE Is this still what you have to use? Or was it ever added as a feature?

0
0
#3
Options
Re:TL-R605 with OC200 cannot resolve internal network names
2021-12-18 04:14:01

@MarcoE 

I too am looking for a similar solution., I need to see my web server/web site through my OpenVPN client but I am unable to resolve the web site name when the tunnel is connected. I can resolve sites in the WWAN like Bing and Google but not my intranet site. When I use nslookup, I get a DNS server timeout error after 2 seconds from the gateway IP. I subscribed and set up DDNS with a TP-Link approved provider which I am still configuring. When I trace route and ping the servers, that works fine. The issue is whether there is a DNS server on the ER605 router that works as it should. I am using a Windows server system for DNS/DHCP which I have configured on the ER605 under advanced settings that works fine as long as I am not on the VPN. Does anyone know if there is a DNS server on this router? If not, is there a way to allow the VPN tunnel to see the Windows DNS server?

0
0
#4
Options
Re:TL-R605 with OC200 cannot resolve internal network names
2021-12-18 12:46:50

@jkexbx yes still after nearly one year the same silly situation. The products work very stable but useful features? Forget it.

0
0
#5
Options
Re:TL-R605 with OC200 cannot resolve internal network names
2021-12-18 15:09:04

@MarcoE 

It is starting look like I will need to revert my network back to pre-TP-Link standards as my previous Netgear router did have a good DNS server on it and the ability to set up an OpenVPN server (I think) on it. I had struggled with it trying to get it set up correctly but maybe I need to go back to it and try again. The idea of a enterprise level router not having a viable DNS server on it to support VPN tunnels is just beyond the pale. I am just upset that I spent a lot of my IT budget purchasing TP-Link hardware in the last couple of months only to have the main component turn out to be a bust over one simple thing, lack of a DNS server. I like the the Omada control system and the SDN EAP I bought. I just purchased a SDN capable switch but I have yet o open the box due to this issue with the ER605. If I end up reverting back to my original system configuration over this issue of the on board DNS server, I will send the switch back unopened as I already have two other switches I can use with my previous router. Such a shame that a company like TP-Link, with such a large market share, could fail so badly over this one piece that almost every other company can provide with little to no issue. Does anyone know if TP-Link has a different model router that is SDN capable with better DNS capabilities? I would also need OpenVPN access server capabilities.

0
0
#6
Options
Re:TL-R605 with OC200 cannot resolve internal network names
2022-01-18 18:41:20

Just pinging on this thread in case any progress has been made here (unlikely as it seems).

0
0
#7
Options
Re:TL-R605 with OC200 cannot resolve internal network names
2022-01-19 00:11:07

@ThomG 

All is good now. I fixed my network issues by utilizing the tech support pages and tweaking what they wrote against my system and managed to get it all to start working like it's supposed. It was a long endeavor but I learned a lot about TP-Link network products in the process. The answer was for me to use the built in DHCP server in the controller system for each new subnet I had configured rather than trying to get the router to route across the different subnets. Once I set that up for each leg, I applied the port configurations to the switches and everything is green and going. Thank you for asking.

0
0
#8
Options
Re:TL-R605 with OC200 cannot resolve internal network names
2022-01-19 04:37:25

@todonal glad to hear it, though I'm mostly interested in the internal DNS resolution without the controller. I see no evidence that support for this has been added to the firmware, but the thread is also a bit old, so maybe I missed something.

0
0
#9
Options
Re:TL-R605 with OC200 cannot resolve internal network names
2022-01-19 07:11:47

@todonal can you tell us exactly what settings you have done to get internal network names resolved? For me it is still not working and the support is definitely not helpful at all.

 

Kind Regards
Marco

0
0
#10
Options
Re:TL-R605 with OC200 cannot resolve internal network names
2022-01-19 15:40:10
It's surprising internal DNS resolution isn't available in prosumer devices like the TL-R605 and OC200. I haven't found another solution other than running a separate DNS server. Is it possible to raise the priority of this feature request?
1
1
#11
Options