Arch Linux

dreivier

Member

Registered: 2016-04-07

Posts: 36

[SOLVED] No dns resolve in cli but works in Chrome

While ethernet connections work just fine I'm having trouble with dns resolve in my terminal.

I can ping addresses just fine but can't ping urls. I have a working connection in my browser and can get any url resolved in chrome.

I have my router's address in my resolv.conf and looked through earlier forum posts but the solutions seem to address different problems altogether.

is there some service I need to start in order to get wifi dns resolving working? (tried networkd and resolvd but had no real idea if this is actually a starting point).

Last edited by dreivier (2016-06-16 18:31:22)

x33a

Forum Fellow

Registered: 2009-08-15

Posts: 4,587

Re: [SOLVED] No dns resolve in cli but works in Chrome

I am not sure how that's possible. Perhaps chrome is using cached DNS entries. Try purging chrome's cache and see if it still works.

dreivier

Member

Registered: 2016-04-07

Posts: 36

Re: [SOLVED] No dns resolve in cli but works in Chrome

Works with unused dns entries, too. Also in Firefox. I'm confused.

x33a

Forum Fellow

Registered: 2009-08-15

Posts: 4,587

Re: [SOLVED] No dns resolve in cli but works in Chrome

Forget ping, see if you can use wget or curl from the command line.

Test with something like

curl -I https://www.archlinux.org

elkoraco

Member

Registered: 2013-02-18

Posts: 140

Re: [SOLVED] No dns resolve in cli but works in Chrome

YOu most likely have ip6 disabled in the kernel command line or by some other means. Can oyu ping with

ping -4 www.google.com

dreivier

Member

Registered: 2016-04-07

Posts: 36

Re: [SOLVED] No dns resolve in cli but works in Chrome

ok, I switched networks and with my home wifi everything works as expected. So far I only had wifi enabled at work and in a cafe today.

I will check my work connection once again tomorrow and see what causes it.

Thank you so far.

dreivier

Member

Registered: 2016-04-07

Posts: 36

Re: [SOLVED] No dns resolve in cli but works in Chrome

This automagically resolved. Probably some misconfiguration of a network package or maybe a firmware issue that has been resolved with the latest updates. Tag with [solved]?