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.
Here's my weird problem.
I use a static IP for my linux nas-server.
Its been working great for many years.
This weeks something happened, don't know sure what.
I got no internet when i use my static IP 192.168.1.50
So I swtiched tot AUTO and i got internet.
Good speed and all pages open.
If i go back to static IP...
And here is the weird part.
I can ping google with:
ping 8.8.8.8 --> works fine
If i go to ww.google.nl it works, but very slow.
If I try to open a search result, like antoher page, i won't open.
Should be the nameserver the same as the dns in the network manager?
It certainly should.
"127.0.0.1" means you're querying a local DNS service on your system, one which may not be configured optimally (or at all). That would explain the delays and name resolution problems.
"127.0.0.1" means you're querying a local DNS service on your system, one which may not be configured optimally (or at all). That would explain the delays and name resolution problems.
Many tnx for your help and quick responce.
Now we know what the problem is, how can I solve it?
My setting in network manager are good.
It seems that network manager is not able to write the DNS into the /etc/resolv.conf files.
I have no idea why Network Manager doesn't put the DNS entries into the /etc/resolv.conf file.
Have you tried simply editing the file directly?
Yes I did.
But it already says in the config file:
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 127.0.0.1
I already tried reinstalling network manager, still same problem.
Even worse, now the problem is also on auto (DHCP)
I screwed up some file, I'm sure. But which one
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.