Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Parser fails with search -- #31

Open
Minkiu opened this issue Jan 23, 2023 · 0 comments
Open

Parser fails with search -- #31

Minkiu opened this issue Jan 23, 2023 · 0 comments

Comments

@Minkiu
Copy link

Minkiu commented Jan 23, 2023

Hey,

been re-directed from NewsFlash Issues , seems like resolve-conf trips when the /etc/resolve.conf file contains search --:

$ cat -p /etc/resolv.conf 
# This is /run/systemd/resolve/stub-resolv.conf managed by man:systemd-resolved(8).
# Do not edit.
#
# This file might be symlinked as /etc/resolv.conf. If you're looking at
# /etc/resolv.conf and seeing this text, you have followed the symlink.
#
# This is a dynamic resolv.conf file for connecting local clients to the
# internal DNS stub resolver of systemd-resolved. This file lists all
# configured search domains.
#
# Run "resolvectl status" to see details about the uplink DNS servers
# currently in use.
#
# Third party programs should typically not access this file directly, but only
# through the symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a
# different way, replace this symlink by a static file or a different symlink.
#
# See man:systemd-resolved.service(8) for details about the supported modes of
# operation for /etc/resolv.conf.

nameserver 127.0.0.53
options edns0 trust-ad
search --

I think this is the most relevant part:
error reading DNS system conf: Error parsing resolv.conf: ProtoError { kind: Msg(\"Malformed label: --\") }

Cheers,
Oscar.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant