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

[Bertrand Friconneau]

Hi everyone,

My problem is fixed.

And my Squid server up to date (Ubuntu 22.04 LTS).

Finaly my problem was not about squid but about DNS.

Ubuntu could'nt find any more my AD server.

Solution :
Modify 2 files :
/etc/resolvconf/resolv.conf.d/head
/etc/resolv.conf

And put in it this line :
nameserver <ip of my AD/DNS server>

After serveral reboot/restart, the configuration is always in use.

Thanks for the help

Regards

Bertrand Friconneau





Le 15/12/2022 à 11:06, Bertrand Friconneau a écrit :
> 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).
>>
>> ===
>