# Odd custom /etc/resolv.conf warning **URL:** https://forum.yunohost.org/t/odd-custom-etc-resolv-conf-warning/27713 **Category:** Support **Tags:** diagnosis, warnings, french **Created:** [December 21, 2023, 7:48pm UTC](https://forum.yunohost.org/t/odd-custom-etc-resolv-conf-warning/27713 "2023-12-21T19:48:32Z") **Posts on this page:** 8 **Page:** 1
### Author: ![srohde](https://forum.yunohost.org/letter_avatar_proxy/v4/letter/s/e5b9ba/32.png) [@srohde](https://forum.yunohost.org/u/srohde) #### Post date: [December 21, 2023, 7:48pm UTC](https://forum.yunohost.org/t/odd-custom-etc-resolv-conf-warning/27713/1 "2023-12-21T19:48:32Z")
**Hardware:** Old laptop or computer **YunoHost version:** 11.2.8.2 **I have access to my server :** Through SSH + through the webadmin + direct access via keyboard / screen **Are you in a special context or did you perform some particular tweaking on your YunoHost instance ?** : no Hello everyone 👋 Since yesterday I started getting a warning in my daily diagnosis, saying: "[WARNING] DNS resolution seems to be working, but it looks like you’re using a custom /etc/resolv.conf. - The file /etc/resolv.conf should be a symlink to /etc/resolvconf/run/resolv.conf itself pointing to 127.0.0.1 (dnsmasq). If you want to manually configure DNS resolvers, please edit /etc/resolv.dnsmasq.conf." Thing is, to my knowledge, I shouldn’t have anything like that since I am using one of the automatic domains provided by the yunohost project. Does anyone have an idea how can I resolve this issue? The only thing I can think of is that I have updated the yunohost version from 11.2.5 (afair) a couple of days before getting the warning and the day before I didn’t have internet connection during diagnosis so the errors were different. Don’t know if that helps… Thanks in advance for any help!! ---
### Author: ![srohde](https://forum.yunohost.org/letter_avatar_proxy/v4/letter/s/e5b9ba/32.png) [@srohde](https://forum.yunohost.org/u/srohde) #### Post date: [December 22, 2023, 10:57am UTC](https://forum.yunohost.org/t/odd-custom-etc-resolv-conf-warning/27713/2 "2023-12-22T10:57:38Z")
A quick look at the abovementioned file, /etc/resolv.conf, shows it has the following : ```auto # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN # 127... is the systemd-resolved stub resolver. # run "resolvectl status" to see details about the actual nameservers. ``` In case that helps anyone in helping me… ---
### Author: ![wbk](https://forum.yunohost.org/letter_avatar_proxy/v4/letter/w/e0b2c6/32.png) [@wbk](https://forum.yunohost.org/u/wbk) #### Post date: [January 10, 2024, 10:36pm UTC](https://forum.yunohost.org/t/odd-custom-etc-resolv-conf-warning/27713/3 "2024-01-10T22:36:25Z")
> [@srohde](#): > > A quick look at the abovementioned file, /etc/resolv.conf, shows… Actually, the warning states: > [@srohde](#): > > The file /etc/resolv.conf should be a symlink On my Yunohost, it looks like this: ```auto # ls -l /etc/resolv.conf lrwxrwxrwx 1 root root 31 Oct 28 2021 /etc/resolv.conf -> /etc/resolvconf/run/resolv.conf ``` The → behind `/etc/resolv.conf` indicates a symlink. Is it there, in your case? ---
### Author: ![srohde](https://forum.yunohost.org/letter_avatar_proxy/v4/letter/s/e5b9ba/32.png) [@srohde](https://forum.yunohost.org/u/srohde) #### Post date: [January 11, 2024, 7:30pm UTC](https://forum.yunohost.org/t/odd-custom-etc-resolv-conf-warning/27713/4 "2024-01-11T19:30:18Z")
Hello @wbk First of all many thanks for getting back to me! So I followed your instructions and this is what I get when I run the `ls -l` command: ```auto lrwxrwxrwx 1 root root 29 Aug 12 13:23 /etc/resolv.conf -> ../run/resolvconf/resolv.conf ``` The odd thing is that when I try to find the abovementioned path (/etc/run/resolvconf/resolv.conf), it turns out there is no such file or directory (/etc/run). I don’t know if that helps with anything or not. ---
### Author: ![wbk](https://forum.yunohost.org/letter_avatar_proxy/v4/letter/w/e0b2c6/32.png) [@wbk](https://forum.yunohost.org/u/wbk) #### Post date: [January 11, 2024, 11:36pm UTC](https://forum.yunohost.org/t/odd-custom-etc-resolv-conf-warning/27713/5 "2024-01-11T23:36:08Z")
> [@srohde](#): > > there is no such file or directory (/etc/run) Strange … the symlink is not correct. It should point to `/etc/resolvconf...`, not to `/etc/run...` You could ```auto $ ls /etc/resolvconf/run/resolv.conf # check that there is a result below: /etc/resolvconf/run/resolv.conf $ sudo rm /etc/resolv.conf $ sudo ln -s /etc/resolvconf/run/resolv.conf /etc/ $ ls -l /etc/resolv.conf # check for the correct output: lrwxrwxrwx 1 root root 31 Jan 12 2024 /etc/resolv.conf -> /etc/resolvconf/run/resolv.conf ``` As always when copy/pasting commands from the internet: check that you understand what they do 🙂 ---
### Author: ![srohde](https://forum.yunohost.org/letter_avatar_proxy/v4/letter/s/e5b9ba/32.png) [@srohde](https://forum.yunohost.org/u/srohde) #### Post date: [January 12, 2024, 7:11pm UTC](https://forum.yunohost.org/t/odd-custom-etc-resolv-conf-warning/27713/6 "2024-01-12T19:11:56Z")
Hello again 😁 Once I got back my machine (see the other post), yunohost was already up to date and running version 11.2.9.1. This somehow also fixed this issue and now I don’t get these warnings anymore. Hopefully it’ll stay like that 🤞 Thanks for all the help, highly appreciated!! ---
### Author: ![wbk](https://forum.yunohost.org/letter_avatar_proxy/v4/letter/w/e0b2c6/32.png) [@wbk](https://forum.yunohost.org/u/wbk) #### Post date: [January 12, 2024, 8:21pm UTC](https://forum.yunohost.org/t/odd-custom-etc-resolv-conf-warning/27713/7 "2024-01-12T20:21:48Z")
That is nice to read, thanks for reporting back! ---
### Author: ![system](https://forum.yunohost.org/uploads/default/original/2X/f/f59fe8e3ee6b100b4f574d30d6e30479c68b89f0.png) [@system](https://forum.yunohost.org/u/system) #### Post date: [February 11, 2024, 8:21pm UTC](https://forum.yunohost.org/t/odd-custom-etc-resolv-conf-warning/27713/8 "2024-02-11T20:21:55Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.