Symlink for resolv.conf is wrong on fresh install

Bug #2043234 reported by Vitalii Sharapov
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
systemd (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Hello. Sorry for disturb, may I ask you please to confirm if im not doing anything wrong with new installation?
Its being a while since the problem exists AT LEAST IN MY CASE with "faulty path" for symlinc at resolv.conf
I believe its keep happening since 18.04 version and even now in 22.04
So, in the fresh install the path looks like this:
lrwxrwxrwx 1 root root 39 Feb 17 2023 resolv.conf -> ../run/systemd/resolve/stub-resolv.conf

but once im running :
sudo ln -sf /run/systemd/resolve/resolv.conf /etc/resolv.conf

everything works fine. By everything I mean when I run nslookup.

Regards,

Vitalii Sharapov

affects: ubuntu-docs (Ubuntu) → systemd (Ubuntu)
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in systemd (Ubuntu):
status: New → Confirmed
Revision history for this message
christophe hubert (ch-hubert) wrote :

Thank you Vitalii,

Your fix helped me a lot,

My Ubuntu was in 22.04 when this problem appeared : DNS domain search paths not updated when VPN started

Before your fix :

➜ ~ sudo ls -la /etc/resolv.conf
lrwxrwxrwx 1 root root 39 juin 23 12:37 /etc/resolv.conf -> ../run/systemd/resolve/stub-resolv.conf

So this symbolic link has been changed on june 23, 2023.

Revision history for this message
Nick Rosbrook (enr0n) wrote :

This symlink looks correct to me. If you are still having an issue, please provide a specific example and instructions on how to reproduce it in another bug report.

Changed in systemd (Ubuntu):
status: Confirmed → Invalid
Revision history for this message
Vitalii Sharapov (vsharapov) wrote :

@enr0n Nick, did you compare the full path of what i wrote? Also what do you mean if I could provide specific example? As i wrote in main question you dont need anything specific as i tried in fresh brand new Ubuntu 22.04. Just install fresh new operating system and try to resolve google.com and system wont resolve, as it appears, the path is wrong initially. If you read closely, the path that to resolv.conf in the OS has two dots, while it should have no dots in the beginning of the path. Thats why i tested and asked here thinking that there is a bug

Revision history for this message
Vitalii Sharapov (vsharapov) wrote :

In case if noone can find where is the problem just instal fresh OS and run nslookup google.com
Then check the validity of the symlink on resolv.conf

Revision history for this message
Nick Rosbrook (enr0n) wrote :

Yes, I am aware of the path. This is what I see on a fresh jammy install:

nr@clean-jammy-amd64:~$ readlink /etc/resolv.conf
../run/systemd/resolve/stub-resolv.conf
nr@clean-jammy-amd64:~$ nslookup google.com
Server: 127.0.0.53
Address: 127.0.0.53#53

Non-authoritative answer:
Name: google.com
Address: 142.251.40.142
Name: google.com
Address: 2607:f8b0:4006:80f::200e

Revision history for this message
Vitalii Sharapov (vsharapov) wrote :

Well, I guess, it was only me then =D
please close the ticket until issue will arise.
Thanks

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related questions

Remote bug watches

Bug watches keep track of this bug in other bug trackers.