Bug#859092: systemd-resolved : does not return fully qualified host name for local host name
Michael Biebl
biebl at debian.org
Tue Jul 5 19:24:43 BST 2022
Control: tags -1 + moreinfo upstream
On Thu, 30 Mar 2017 10:38:45 +0200 Laurent Bonnaud
<L.Bonnaud at laposte.net> wrote:
> Package: systemd
> Version: 233-5
>
>
> Dear maintainer,
>
> here are 2 DNS queries that illustrate the problem:
>
> - when I query a "real" DNS server (bind) I get the expected answer "irancy.iut2.upmf-grenoble.fr"
>
> - when I query systemd-resolved I get the short answer "irancy"
>
> root at irancy:~# host 192.168.141.13 193.55.51.34
> Using domain server:
> Name: 193.55.51.34
> Address: 193.55.51.34#53
> Aliases:
>
> 13.141.168.192.in-addr.arpa domain name pointer irancy.iut2.upmf-grenoble.fr.
>
> root at irancy:~# host 192.168.141.13 127.0.0.53
> Using domain server:
> Name: 127.0.0.53
> Address: 127.0.0.53#53
> Aliases:
>
> 13.141.168.192.in-addr.arpa domain name pointer irancy.
>
>
> This a problem for apache who complains about its ServerName.
>
In case you can still reproduce the issue with an up-to-date version of
systemd (i.e. v250 or v251), please report this upstream at
https://github.com/systemd/systemd/issues
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20220705/8cc68b64/attachment.sig>
More information about the Pkg-systemd-maintainers
mailing list