Name resolution fails on a fresh install in virtualbox [solved]

Rillian · 2018-11-18 14:21:21

Ping returns: Name resolution failed on domain names but works fine on ip addresses

Last edited by Rillian (2018-11-18 15:16:28)

Rillian · 2018-11-18 14:25:15

I tried installing guest additions via chroot, no difference.

seth · 2018-11-18 14:36:01

Welcome to the forum. Please take the time to read the stickies in the newbie corner.
In particular:
- don't bump, use the edit link
- you'll have to provide more details on your network configuration; in this case a major question is whether you're using systemd-resolved, but also your resolve.conf and nsswitch.conf matter.

Rillian · 2018-11-18 14:41:45

Yes!! Unlike many people I started using Linux after systemd became widespread so I have nothing against it. So when I did pacstrap I chose systemd-resolvconf

seth · 2018-11-18 14:45:15

This has nothing to do w/ systemd or having something "against" it, systemd-resolved is inherently broken for anything but the most simplistic DNS setups, but even then it significantly deviates from traditional resolvers and requires accommodation:
https://wiki.archlinux.org/index.php/Sy … figuration

Rillian · 2018-11-18 14:51:27

Due to you saying about systemd-resolvd I looked in the arch wiki and did "resolvectl status".
It returned: Failed to get global data: Unit dbus-org.freede...
It also said something about installing network manager. I will do this but is there a way to make it work without network manager.

Rillian · 2018-11-18 14:53:32

seth wrote:

This has nothing to do w/ systemd or having something "against" it, systemd-resolved is inherently broken for anything but the most simplistic DNS setups, but even then it significantly deviates from traditional resolvers and requires accommodation:
https://wiki.archlinux.org/index.php/Sy … figuration

Is there some way I can disable systemd-resolved?

Trilby · 2018-11-18 15:04:16

Rillian, you were directed right off the bat to some stickied threads about posting exact output. Right after than you referred to output as saying "something about ..." rather than posting the output. Worse yet, you were explicitly told to edit your post rather than repeatedly bumping. Then you do just the opposite again. This is not a good start on the forums.

As for how to disable the service, even the most trivial search of the wiki (the page for this service specifically) would have given you the answer. Don't expect to have your hand held here - make *some* effort.

Last edited by Trilby (2018-11-18 15:05:26)

Rillian · 2018-11-18 15:15:57

Sorry I thought bumping was using quick reply I was wrong.
I didn't do the exact output as I cannot copy from virtualbox. In the future I will ether use ssh or type it out fully.
And finally you are correct about me not looking in the wiki.

Thanks for the correction

Last edited by Rillian (2018-11-18 15:17:35)

Trilby · 2018-11-18 15:19:23

You're welcome. I glad that worked and thanks for marking the thread as solved.

Arch Linux

#1 2018-11-18 14:21:21

Name resolution fails on a fresh install in virtualbox [solved]

#2 2018-11-18 14:25:15

Re: Name resolution fails on a fresh install in virtualbox [solved]

#3 2018-11-18 14:36:01

Re: Name resolution fails on a fresh install in virtualbox [solved]

#4 2018-11-18 14:41:45

Re: Name resolution fails on a fresh install in virtualbox [solved]

#5 2018-11-18 14:45:15

Re: Name resolution fails on a fresh install in virtualbox [solved]

#6 2018-11-18 14:51:27

Re: Name resolution fails on a fresh install in virtualbox [solved]

#7 2018-11-18 14:53:32

Re: Name resolution fails on a fresh install in virtualbox [solved]

#8 2018-11-18 15:04:16

Re: Name resolution fails on a fresh install in virtualbox [solved]

#9 2018-11-18 15:15:57

Re: Name resolution fails on a fresh install in virtualbox [solved]

#10 2018-11-18 15:19:23

Re: Name resolution fails on a fresh install in virtualbox [solved]

Board footer