qkdfrrrz Posted October 6, 2016 Share Posted October 6, 2016 Hi. I've a new Lan Turtle that works perfectly fine on a home PC but when it's connected to a network that serves a 3 tier namespace - like "hostname.sub.zone.com" the host computer fails at sub.zone.com and zone.com DNS resolution. I can see that the host computer's DNS server is set to the IP address of the Lan Turtle, and the Lan Turtle /etc/resolv.conf is set to itself (127.0.0.1). All other external domain names resolve fine though. Anyone else seeing this? Quote Link to comment Share on other sites More sharing options...
skippy7 Posted October 8, 2016 Share Posted October 8, 2016 On 10/7/2016 at 3:22 AM, qkdfrrrz said: Hi. I've a new Lan Turtle that works perfectly fine on a home PC but when it's connected to a network that serves a 3 tier namespace - like "hostname.sub.zone.com" the host computer fails at sub.zone.com and zone.com DNS resolution. I can see that the host computer's DNS server is set to the IP address of the Lan Turtle, and the Lan Turtle /etc/resolv.conf is set to itself (127.0.0.1). All other external domain names resolve fine though. Anyone else seeing this? When connect lan turtle it seems changes your dns server to lan turtle IP address. You may try open cmd prompt and type nslookup before plug your lan turtle and after. My solution I just plug lan cable to the lan turtle so you can resolve the dns after that. Quote Link to comment Share on other sites More sharing options...
qkdfrrrz Posted October 10, 2016 Author Share Posted October 10, 2016 The LAN cable is plugged into the Lan Turtle. The problem is that the LT itself doesn't seem to be able to forward the requests for *.sub.zone.com up to the authoritative DNS servers, but will for all other external zones. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.