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

No DNS Lookups possible in rescue system when resolvconf package is installed #520

Closed
vaporup opened this issue Dec 19, 2014 · 0 comments
Closed
Assignees
Labels
bug The code does not do what it is meant to do
Milestone

Comments

@vaporup
Copy link

vaporup commented Dec 19, 2014

Hi,

we use ReaR with a bunch of Ubuntu Systems and it works great so far.
Many thanks for this great project and keep up the good work.

Usually we put an IP address in local.conf or site.conf
and then rear recover works just fine in the rescue system.

But lately I used the DNS Name instead of the IP address because the Backup target used DNS Round Robin.

While testing the recover, the backup source could not be mounted because the hostname was not resolvable.

I checked /etc/ for resolv.conf and it was there, but a cat on it failed complaining it could not find the file.

I also checked the code if resolv.conf gets copied over to the rescue system.

In /usr/share/rear/rescue/GNU/Linux/30_dns.sh the variable COPY_AS_IS actually does this

The problem is, that /etc/resolv.conf is a symlink to /run/resolvconf/resolv.conf and that file was not copied over.

/etc/resolv.conf -> ../run/resolvconf/resolv.conf

Cause is the resolvconf package which dynamically creates the resolv.conf in /run/resolvconf/resolv.conf and symlinks it to /etc.

http://packages.ubuntu.com/trusty/resolvconf
http://en.wikipedia.org/wiki/Resolvconf

@gdha gdha added the bug The code does not do what it is meant to do label Dec 23, 2014
@gdha gdha added this to the Rear v1.17 milestone Dec 23, 2014
@gdha gdha self-assigned this Dec 23, 2014
@gdha gdha closed this as completed in 8c295c7 Jan 7, 2015
gdha added a commit that referenced this issue Feb 16, 2017
…k to /run/resolvconf/resolv.conf

Issue reported in #1200 and #520 (in #520 it was badly fixed). Now we remove the linked file and copy
the real content to /etc/resolv.conf
This should fix #1200 and #520 - waiting on confirmation before closing
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug The code does not do what it is meant to do
Projects
None yet
Development

No branches or pull requests

2 participants