Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
This tells me that you HAD a local DNS server at 192.168.1.241, and another in a different subnet at 192.168.7.1. Since those are non-routable addresses, they were NOT out on the internet. Since you HAVE network and can ping an external DNS server (8.8.8.8) we know you have a proper route to the world. IT is as if your local DNS servers are down, or you can no longer reach them.
Do this, make the first entry on your /etc/resolv.conf file read
Code:
nameserver 8.8.8.8
so you can resolve public names. That will get you some action while you investigate what happened to your local name servers.
PS: 127.0.0.1 is your loopback address. IT is generally registered as the LO (not ETHx) interface, and provides a way to test that your networking system is running. Since it is your own machine, it gives no information about your external connections.
.... Do this, make the first entry on your /etc/resolv.conf file read
Code:
nameserver 8.8.8.8
so you can resolve public names. That will get you some action while you investigate what happened to your local name servers.
It works. Thank You. But... how should I investigate "what happened to your local name servers" ?
It all started after having installed some VPN packages to ssh-access (succesfully) to "eng.myemployer.com". Now of course I cannot access anything at all.
Among the running processes I see [/usr/sbin/sshd -D] and [/usr/bin/ssh-agent ......]
It works. Thank You. But... how should I investigate "what happened to your local name servers" ?
Need a lot more information from you to answer that. Those DNS servers are non-standard. You, or somebody else, had to manually configure them somewhere. The question is why? Were there ever machines at those IPs? What happened to them? What does your network look like? And why did you feel it necessary to install VPN in order to SSH somewhere? Those are two completely different protocols.
Last edited by suicidaleggroll; 07-05-2016 at 10:31 AM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.