OpenSSL problems

Yeah, if it works. Why not.

You might be able to find another server which gives you a better response time though.
236 msec is quite a lot (although maybe that’s not too bad with your wireless router thing) :man_shrugging:

https://public-dns.info/

You have to tell me though, why it does work in windows. That should use your router too :wink:

well, i absolutely don’t know…
I only know that i leave Ubuntu because i was get things like this.

On Ubuntu it was worse, because i was able to browse around some popular sites like Google, Youtube, Facebook etc. but when i try to check out some less popular sites, i was getting exactly this.

No internet connection

… apparently, it wasn’t Ubuntu’s fault
still odd why windows works while it doesn’t work here.

A vpn might help - it’s usually not free but for a fee
If you are sufficiently annoyed … you might go for it. :wink:
I have had no need for it until and as of now.
So I have no experience with that.

Where in the world are you?
Where do they do such things …?
From your profile - your timezone is the same as mine.
I’m in Europe/Germany - but you could just as well be in South Africa …

I will mark @Nachlese 's post as solution since it is a DNS thing and he provided instructions for changing it. The fact that either your router is too stupid to route those lower address ranges or your ISP is blocking them is yet another issue… :wink:

I have a problem again.

For this to work, added public DNS in /etc/resolv.conf

nameserver 208.67.222.222

Now my local sites cannot load.

So the only solution is to change back that to:

nameserver 127.0.0.1

So how can i make it serve both local sites and internet sites?

By the way adding this to `Network connection settings does not work

Did you tried to use your gateway IP (so the router)?
You can grab it’s IP from the following command in Terminal:

route -n | grep 'UG[ \t]' | awk '{print $2}'

At least, to be sure that everything should work to default settings.

If you are using NetworkManager
then editing /etc/resolv.conf directly is not the proper way to do things.
Use NetworkManager and it’s interface
or disable it and then try your thing.

you didn’t describe the problem
… or I somehow missed that …

127.0.0.1 is your local machine. Which DNS server are you running?

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.