[squid-users] Update from Squid 4 to Squid 5 :

[ngtech1ltd at gmail.com]

And just in case someone needs a demo how to remove netplan and install network manager on Ubuntu 22.04:
https://www.youtube.com/watch?v=dy9MxgGzTk4

(I had it prepared for a good friend last week)

Eliezer

----
Eliezer Croitoru
NgTech, Tech Support
Mobile: +972-5-28704261
Email: ngtech1ltd at gmail.com
Web: https://ngtech.co.il/
My-Tube: https://tube.ngtech.co.il/

-----Original Message-----
From: squid-users <squid-users-bounces at lists.squid-cache.org> On Behalf Of Bertrand Friconneau
Sent: Thursday, 15 December 2022 12:06
To: Bruno de Paula Larini <bruno.larini at riosoft.com.br>; squid-users at lists.squid-cache.org
Subject: Re: [squid-users] Update from Squid 4 to Squid 5 :

Hi,

Here is the content of my actual /etc/resolv.conf (ubuntu 20.04) :
------------------------------------------------------------------------------------------------
# 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
# 127.0.0.53 is the systemd-resolved stub resolver.
# run "systemd-resolve --status" to see details about the actual 
nameservers.

nameserver 172.20.0.1
nameserver 127.0.0.53
search stemarie-aizenay.local
------------------------------------------------------------------------------------------------

Bruno, thanks for the suggestions.

I will try after Christmas Hollidays.

Regards

Bertrand Friconneau





Le 14/12/2022 à 13:26, Bruno de Paula Larini a écrit :
> Em 13/12/2022 19:46, ngtech1ltd at gmail.com escreveu:
>> Hey,
>>
>> What is the content of:
>> /etc/resolv.conf
>> ?
>>
>> It could be something related to default systemd dns services.
>>
>> Eliezer
>> ----
>> Eliezer Croitoru
>> NgTech, Tech Support
>> Mobile: +972-5-28704261
>> Email: ngtech1ltd at gmail.com
>> Web: https://ngtech.co.il/
>> My-Tube: https://tube.ngtech.co.il/
>>
> Yep, I had the same issues when I upgraded from 4 to 5, because I also 
> upgraded the distro version along with it, and systemd-resolved is 
> enabled by default in some, such as Fedora and Ubuntu. It stopped 
> resolving local domain names for some reason.
> Instead of struggling to make it work on the new model, I simply 
> disabled systemd-resolved and went back to old resolv.conf style.
>
> I'll quote the solution I followed here: 
> https://askubuntu.com/questions/907246/how-to-disable-systemd-resolved-in-ubuntu
>
> ====
>
> This method works on the Ubuntu releases 17.04 (Zesty), 17.10 
> (Artful), 18.04 (Bionic), 18.10 (Cosmic), 19.04 (Disco) and 20.04 
> (Focal):
>
> Disable and stop the systemd-resolved service:
>
> sudo systemctl disable systemd-resolved
> sudo systemctl stop systemd-resolved
>
> Then put the following line in the [main] section of your 
> /etc/NetworkManager/NetworkManager.conf:
>
> dns=default
>
> Delete the symlink /etc/resolv.conf
>
> rm /etc/resolv.conf
>
> Restart NetworkManager
>
> sudo systemctl restart NetworkManager
>
> Also be aware that disabling systemd-resolvd might break name 
> resolution in VPN for some users. See this bug on launchpad (Thanks, 
> Vincent).
>
> ===

_______________________________________________
squid-users mailing list
squid-users at lists.squid-cache.org
http://lists.squid-cache.org/listinfo/squid-users