DerLinkman Check if you have a entry called search within the /etc/resolv.conf file.

Probably not everybody is happy (or can use) with this workaround:

Googled (but known):

"From man resolv.conf:

The search list is normally determined from the local domain name; by default, it contains only the local domain name. This may be changed by listing the desired domain search path following the search keyword with spaces or tabs separating the names. Resolver queries having fewer than ndots dots (default is 1) in them will be attempted using each component of the search path in turn until a match is found. For environments with multiple subdomains please read options ndots:n below to avoid man-in-the-middle attacks and unnecessary traffic for the root-dns-servers. Note that this process may be slow and will generate a lot of network traffic if the servers for the listed domains are not local, and that queries will time out if no server is available for one of the domains.

The search list is currently limited to six domains with a total of 256 characters."

This is helpful if you are part of a LAN environment that has its own DNS server so that people can type simple names to reach local resources. If you don’t have a home or corporate LAN with your own DNS server it’s nothing you really have to worry about.

I assume, in companies there are a number of mailcows in use with own DNS servers. In future IMVHO this should be fixed in a proper/better way.

    stefan21
    Does that apply actually?
    Which internal services of mailcow need to make use of additional configured search suffixes? I am not aware of any.

      cat /etc/debian_version
      12.4

      uname -r
      6.1.0-17-amd64

      cat /etc/apt/sources.list
      ##deb cdrom:[Debian GNU/Linux 12.2.0 Bookworm - Official amd64 NETINST with firmware 20231007-10:28]/ bookworm main non-free-firmware

      deb Index of /debian

      bookworm main non-free-firmware
      deb-src Index of /debian
      ftp-stud.hs-esslingen.de
      Index of /debian
      [ICO][PARENTDIR][DIR]
      bookworm main non-free-firmware

      deb Index of /debian-security

      bookworm-security main non-free-firmware
      deb-src Index of /debian-security
      security.debian.org
      Index of /debian-security
      [ICO][PARENTDIR][   ]
      bookworm-security main non-free-firmware

      ##bookworm-updates, to get updates before a point release is made;
      ##see Chapter 2. Debian package management


      deb Index of /debian
      ftp-stud.hs-esslingen.de
      Index of /debian
      [ICO][PARENTDIR][DIR]
      bookworm-updates main non-free-firmware
      deb-src Index of /debian
      ftp-stud.hs-esslingen.de
      Index of /debian
      [ICO][PARENTDIR][DIR]
      bookworm-updates main non-free-firmware

      cat /etc/apt/sources.list.d/docker.list
      deb [arch=amd64 signed-by=/etc/apt/keyrings/docker.gpg] Index of linux/debian/

      bookworm stable

      OS system is up-to-date.

      esackbauer Does that apply actually?

      Updating from described above mailcow 2023-12a to 2024-01a will end in the bug the OP described.

      esackbauer Which internal services of mailcow need to make use of additional configured search suffixes? I am not aware of any.

      Hmm, the resolv.conf is AFAIK system relevant for the OS. This file is not from mailcow. I’d like to stay as much as possible to the stock of debian. Just my thoughts.

        stefan21 the resolv.conf is AFAIK system relevant for the OS.

        According to what the user mendozal has written, its not about the resolv.conf in the OS, but the one inside the php-fpm container. So it should have no side effects to the host OS or other containers.

          jacotec
          No, it is about a bug in Alpine Linux and that is inside the containers.

            I misunderstood also. I’ll have a closer look into.
            Anyway - after the latest update (as I described above) the gui is not reachable.

            Thank you smart people for giving all the information needed to fix this until an update is there.
            What i did:
            docker exec -it mailcowdockerized-php-fpm-mailcow-1 /bin/bash

            vi /etc/resolv.conf
            -> Remove “search” entry

            docker exec -it mailcowdockerized-php-fpm-mailcow-1 kill -USR2 1

            esackbauer Yes and no.

            Yes it is inside Alpine Images using curl (partially) but it is influenced by the hosts resolv.conf.

              Updated to 2024-01b and all is working fine.
              So this issue seems to be resolved.

              DerLinkman Yes it is inside Alpine Images using curl (partially) but it is influenced by the hosts resolv.conf

              1. Uncomment (or delete) the search line in the underlying OS in /etc/resolv.conf
              2. docker exec -it mailcowdockerized-php-fpm-mailcow-1 /bin/bash
              3. delete in /etc/resolv.conf the search line (and save) and exit
              4. docker exec -it mailcowdockerized-php-fpm-mailcow-1 kill -USR2 1
              5. docker compose restart php-fpm-mailcow
              6. check if the workaround survived

              Otherwise the workaround will not survive if mailcow is restarted with docker.

              Personally I really don’t like to change files in the underlying OS while running docker. At a time this will end in errors.

              7 months later
              No one is typing