canonical / canonical/cloud-init

Debian 10/9/8 DNS configuration bug

Open
#3,486 8 comments 1 reaction 0 assignees View on GitHub
bug launchpad
Dominant language
Python
Stars
3.8k
Forks
1.1k
Avg merge
2d 23h
Merged PRs (30d)
18

Description

This bug was originally filed in Launchpad as [LP: #1850310](https://bugs.launchpad.net/cloud-init/+bug/1850310)

Launchpad details

affected_projects = []

assignee = None
assignee_name = None
date_closed = None
date_created = 2019-10-29T12:45:21.422366+00:00
date_fix_committed = None
date_fix_released = None
id = 1850310
importance = medium
is_complete = False
lp_url = https://bugs.launchpad.net/cloud-init/+bug/1850310
milestone = None
owner = dshemin
owner_name = Dmitry Shemin
private = False
status = triaged
submitter = dshemin
submitter_name = Dmitry Shemin
tags = []
duplicates = []

_Launchpad user **Dmitry Shemin(dshemin)** wrote on 2019-10-29T12:45:21.422366+00:00_

I use cloud-init with NoCloud data source for configuring my VM's and got strange bug with DNS configuration on official Debian images like https://cdimage.debian.org/cdimage/openstack/current-10/debian-10-openstack-amd64.qcow2.

My network config:

```
version: 2
ethernets:
  eth0:
    set-name: eth0
    match:
      macaddress:
    addresses: [ ]
    gateway4:
    nameservers:
      addresses: [8.8.8.8,8.8.4.4]
```

After creating new VM I got next configuration in /etc/network/interfaces.d/50-cloud-init.cfg which is seems ok:

```
auto lo
iface lo inet loopback

auto eth0
iface eth0 inet static
    address 10.52.240.11/16
    dns-nameservers 8.8.8.8 8.8.4.4
    gateway 10.52.1.1
```

But /etc/resolv.conf contains:

```
nameserver 127.0.0.1
```

Which leads to the fact that I can’t resolve any domain name, for example:
```
# ping google.com
ping: google.com: Temporary failure in name resolution
```

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.