[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1064235:



On Thu, Apr 18, 2024 at 10:17:27AM +0200, Arthur LUTZ wrote:
>    Hi,
>    A small heads up on this issue, we have some minor impacts :
>    * sudo commands show a warning
> 
>  sudo: unable to resolve host example: Name or service not known
> 
>    On a more problematic side (but not breaking) we have filebeat that
>    generates a lot of logs with warnings  related to the change :
>    * Failed looking up CNAME: lookup ip-10-31-51-7 on [1]10.31.48.2:53: no
>    such host: failed looking up IP: lookup ip-10-31-51-7 on [2]10.31.48.2:53:
>    no such host, using hostname = ip-10-31-51-7 as FQDN
>    Our workaround so far is to install `libnss-resolve` in our packer build
>    of the AMI that is based on the debian bookworm AMI.

Indeed, we needed to install libnss-myhostname in addition to removing
libnss-resolve.  This will be fixed in a future release, but in the
meantime you can work around it by installing libnss-myhostname
yourself.

noah


Reply to: