Problem w/ local name resolution (/etc/hosts)

ylanglais

Apparently, vivaldi doesn't use native name resolution (nsswitch.conf) and ignores hosts defined in /etc/hosts.

Hence, different local aliases for sites under development appear to be unreachable.

Gwen-Dragon

@ylanglais said in Problem w/ local name resolution (/etc/hosts):

vivaldi doesn't use native name resolution (nsswitch.conf) and ignores hosts defined in /etc/hosts

Cant reproduce this. Mapping of a testdomain to a IP be works for me f.ex. on Linux Mint.

Mapping used on my PC:
192.168.0.100 zzz
Vivaldi zzz/ calls the router's web ui at 192.168.0.100

different local aliases for sites under development appear to be unreachable

And which URIs?

ylanglais

test.yla 127.0.0.1
doesn't work for me.
I have a http server properly configured. It works fine w/ firefox.
The no_proxy variable contains .yla but is apparently not taken into account.

Doesn't work w/ chromium either.

Gwen-Dragon

@ylanglais said in Problem w/ local name resolution (/etc/hosts):

test.yla 127.0.0.1

Wrong format!
http://www.tldp.org/LDP/solrhe/Securing-Optimizing-Linux-RH-Edition-v1.3/chap9sec95.html
https://www.tecmint.com/setup-local-dns-using-etc-hosts-file-in-linux/

ylanglais

Yes, but it is correct in my /etc/hosts else it wouldn't work at all and it actually works.

127.0.0.1 localhost ylan test.yla www.test-yla1.yla www.test-yla2.yla suivi rewrite.yla admin.rewrite.yla pfwk.yla suivi.yla test.yla 16x50.yla oak.yla divers.yla ws.yla md5.yla mysql-test.yla ldap.yla ldap-master.yla tdb.yla dtdb.yla

By the way, I found this about Chormium :
https://superuser.com/questions/723703/why-is-chromium-bypassing-etc-hosts-and-dnsmasq

Gwen-Dragon

Works on my Ubuntu apache2.

/etc/hosts

127.0.0.1	test.yla localhost
127.0.1.1	minze

# The following lines are desirable for IPv6 capable hosts
::1     ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters

/etc/nsswitch.conf

# /etc/nsswitch.conf
#
# Example configuration of GNU Name Service Switch functionality.
# If you have the `glibc-doc-reference' and `info' packages installed, try:
# `info libc "Name Service Switch"' for information about this file.

passwd:         compat
group:          compat
shadow:         compat
gshadow:        files

hosts:          files mdns4_minimal [NOTFOUND=return] dns
networks:       files

protocols:      db files
services:       db files
ethers:         db files
rpc:            db files

netgroup:       nis

Entering test.yla opens local Apache main page

ylanglais

Well that's the way I work on serveral sites under development for quite some years now with a lot of success.
However, it doesn't work for me. Since I use different proxies, my bet is that the no_proxy variable is only partially taken into account, maybe because of the non standard .yla domain since chrome://net-internals/#proxy shows all no_proxy variable content except the .yla.

Gwen-Dragon

I do not know you proxy configuration.
no_proxy? Where do you set this?

Can you please test with some proxy commandline switches?
https://www.chromium.org/developers/design-documents/network-settings

ylanglais

Problem solved, thank you for your help.
The $no_proxy variable is not used by chromium/vivaldi.
I had to add the '.yla' in dconf & network control center in cinnamon.

Gwen-Dragon

I guess a correctly tailored local proxy.pac file should work for you, too!

Gwen-Dragon

@ylanglais said in Problem w/ local name resolution (/etc/hosts):

The $no_proxy variable is not used by chromium/vivaldi.

Perhaps a bug in newer Chromium code or the Chromium devs removed the use of environment vars.

ylanglais

Apparently, it is more seen as feature to integrate chrome/vivaldi to the desktop with destop configuration tools.

The KISS paradigm depends on who sees things (end-user orientation vs old unix techy narrow view).

Gwen-Dragon

@ylanglais said in Problem w/ local name resolution (/etc/hosts):

Apparently, it is seen as feature to integrate chrome/vivaldi to the desktop configuration tools.

How to make a feature request for Vivaldi

If you think your problem can be solved by a missing feature, please add a single request at https://forum.vivaldi.net/topic/22411/feature-requests-for-vivaldi-1-14/ by hitting the green Reply button at the bottom of the page — not the blue reply link below each post.

Please search the Feature Requests thread (replacing topic with your topic) first and upvote it if it exists.
Add one line in bold as a short title for the feature and 2-3 lines to describe the wanted feature.
Do not discuss features, bugs, or support issues in the thread.
If you need to, please open a new thread in the other Vivaldi forums.
If you want to ask or tell users something, please contact them by chat via their forum profile.

Moderators may remove off-topic posts.