# Comment puis-je me débarrasser de "No symbolic link to /etc/resolvconf/run/resolv.conf" l'avertissement?

**URL:** https://forum.yunohost.org/t/comment-puis-je-me-debarrasser-de-no-symbolic-link-to-etc-resolvconf-run-resolv-conf-lavertissement/12066
**Category:** Support
**Tags:** french
**Created:** [July 7, 2020, 7:48am UTC](https://forum.yunohost.org/t/comment-puis-je-me-debarrasser-de-no-symbolic-link-to-etc-resolvconf-run-resolv-conf-lavertissement/12066 "2020-07-07T07:48:34Z")
**Posts on this page:** 9
**Page:** 1

<div class="post-metadata">

### Author: ![folaht](https://forum.yunohost.org/user_avatar/forum.yunohost.org/folaht/32/794_2.png) [@folaht](https://forum.yunohost.org/u/folaht)
#### Post date: [July 7, 2020, 7:48am UTC](https://forum.yunohost.org/t/comment-puis-je-me-debarrasser-de-no-symbolic-link-to-etc-resolvconf-run-resolv-conf-lavertissement/12066/1 "2020-07-07T07:48:34Z")

</div>

### Mon serveur “VouNébergezPa”

**Matériel:** Pi “Framboisier” 3  
**Version VouNébergezPa:** 3.8.4.9  
**Accès:** “SDS”, Session à distance sécurisée (SSH)  
**modifié?:** Non.

La création manuelle du lien n’a aucun effet.

```auto
 0: 
    description: Connectivité Internet
    id: ip
    items: 
      details: Le fichier /etc/resolv.conf doit être un lien symbolique vers /etc/resolvconf/run/resolv.conf lui-même pointant vers 127.0.0.1 (dnsmasq). Si vous souhaitez configurer manuellement les résolveurs DNS, veuillez modifier /etc/resolv.dnsmasq.conf.
      status: WARNING
      summary: La résolution DNS semble fonctionner, mais il semble que vous utilisez un /etc/resolv.conf personnalisé.

```

---

<div class="post-metadata">

### Author: ![Aleks](https://forum.yunohost.org/user_avatar/forum.yunohost.org/aleks/32/1704_2.png) [@Aleks](https://forum.yunohost.org/u/Aleks)
#### Post date: [July 7, 2020, 11:42am UTC](https://forum.yunohost.org/t/comment-puis-je-me-debarrasser-de-no-symbolic-link-to-etc-resolvconf-run-resolv-conf-lavertissement/12066/2 "2020-07-07T11:42:21Z")

</div>

> [@folaht](#):
>
> La création manuelle du lien n’a aucun effet.

Tu veux dire que tu as essayé de faire un

```auto
rm /etc/resolv.conf
ln -s /etc/resolvconf/run/resolv.conf /etc/resolv.conf

```

?

---

<div class="post-metadata">

### Author: ![folaht](https://forum.yunohost.org/user_avatar/forum.yunohost.org/folaht/32/794_2.png) [@folaht](https://forum.yunohost.org/u/folaht)
#### Post date: [July 7, 2020, 11:52am UTC](https://forum.yunohost.org/t/comment-puis-je-me-debarrasser-de-no-symbolic-link-to-etc-resolvconf-run-resolv-conf-lavertissement/12066/3 "2020-07-07T11:52:08Z")

</div>

> [@Aleks](#):
>
> Tu veux dire que tu as essayé de faire un

Oui,

```auto
mkdir -p /etc/resolvconf/run
cp /etc/resolv.conf /etc/resolv.conf.vieu
mv /etc/resolv.conf /etc/resolvconf/run/resolv.conf
ln -s /etc/resolvconf/run/resolv.conf /etc/resolv.conf

```

---

<div class="post-metadata">

### Author: ![Aleks](https://forum.yunohost.org/user_avatar/forum.yunohost.org/aleks/32/1704_2.png) [@Aleks](https://forum.yunohost.org/u/Aleks)
#### Post date: [July 7, 2020, 11:55am UTC](https://forum.yunohost.org/t/comment-puis-je-me-debarrasser-de-no-symbolic-link-to-etc-resolvconf-run-resolv-conf-lavertissement/12066/4 "2020-07-07T11:55:50Z")

</div>

> [@folaht](#):
>
> `mv /etc/resolv.conf /etc/resolvconf/run/resolv.conf`

C’est pas comme ça que ca marche … ce fichier est censé être généré par resolvconf (le service)

Donc je ferais

```auto
rm /etc/resolvconf/run/resolv.conf
systemctl restart resolvconf

```

et s’assurer que le fichier /etc/resolvconf/run/resolv.conf existe …

---

<div class="post-metadata">

### Author: ![folaht](https://forum.yunohost.org/user_avatar/forum.yunohost.org/folaht/32/794_2.png) [@folaht](https://forum.yunohost.org/u/folaht)
#### Post date: [July 7, 2020, 12:25pm UTC](https://forum.yunohost.org/t/comment-puis-je-me-debarrasser-de-no-symbolic-link-to-etc-resolvconf-run-resolv-conf-lavertissement/12066/5 "2020-07-07T12:25:49Z")

</div>

Resolvconf fonctionne maintenant sans problème, mais l’avertissement persiste.

---

<div class="post-metadata">

### Author: ![Aleks](https://forum.yunohost.org/user_avatar/forum.yunohost.org/aleks/32/1704_2.png) [@Aleks](https://forum.yunohost.org/u/Aleks)
#### Post date: [July 7, 2020, 12:26pm UTC](https://forum.yunohost.org/t/comment-puis-je-me-debarrasser-de-no-symbolic-link-to-etc-resolvconf-run-resolv-conf-lavertissement/12066/6 "2020-07-07T12:26:24Z")

</div>

Et donc est-ce que quand tu fais `cat /etc/resolv.conf` tu as bien

`nameserver 127.0.0.1`

---

<div class="post-metadata">

### Author: ![folaht](https://forum.yunohost.org/user_avatar/forum.yunohost.org/folaht/32/794_2.png) [@folaht](https://forum.yunohost.org/u/folaht)
#### Post date: [July 7, 2020, 12:27pm UTC](https://forum.yunohost.org/t/comment-puis-je-me-debarrasser-de-no-symbolic-link-to-etc-resolvconf-run-resolv-conf-lavertissement/12066/7 "2020-07-07T12:27:55Z")

</div>

```auto
$ cat /etc/resolv.conf
# 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
nameserver 127.0.0.1
search fritz.box

```

---

<div class="post-metadata">

### Author: ![Aleks](https://forum.yunohost.org/user_avatar/forum.yunohost.org/aleks/32/1704_2.png) [@Aleks](https://forum.yunohost.org/u/Aleks)
#### Post date: [July 7, 2020, 12:29pm UTC](https://forum.yunohost.org/t/comment-puis-je-me-debarrasser-de-no-symbolic-link-to-etc-resolvconf-run-resolv-conf-lavertissement/12066/8 "2020-07-07T12:29:09Z")

</div>

Et même si tu fais “re-run diagnosis” (dans la webadmin) tu as encore l’avertissement …?

---

<div class="post-metadata">

### Author: ![system](https://forum.yunohost.org/uploads/default/original/2X/f/f59fe8e3ee6b100b4f574d30d6e30479c68b89f0.png) [@system](https://forum.yunohost.org/u/system)
#### Post date: [July 22, 2020, 12:29pm UTC](https://forum.yunohost.org/t/comment-puis-je-me-debarrasser-de-no-symbolic-link-to-etc-resolvconf-run-resolv-conf-lavertissement/12066/9 "2020-07-22T12:29:12Z")

</div>

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.
