How can it be that nslookup and ping see the domain and Google Chrome does not?

Question

Domain Name System

The essence of the problem:
I'm trying to raise the local DNS (Bind9) to play with my domains on the local machine (there are not enough /etc/hosts capabilities) I raised it

locally on the Bind9 machine and set up my ubuntu.dev domain zone - everything seems to be OK
ping and nslookup perfectly understand that any *.ubuntu.dev domain is on 127.0.0.1
wget " asdasd.ubuntu.dev " also works fine

Google Chrome gives ERR_CONNECTION_REFUSED error

Google Chrome doesn't have any proxy settings or anything like that...
Preload pages for faster browsing and searching disabled

It turns out that Firefox has the same problem

. And what's wrong with it?

Answer 1

Bringing up something in the dev zone is a bad idea.
This is an existing zone with an https-only policy. https://ma.ttias.be/chrome-force-dev-domains-https...
So either create certificates or choose another zone.
Upd: in fact, I'm 99.99% sure that they see the domain, but they are trying to connect via https, and you most likely don't have it.

Answer 2

maybe the problem is in the bastard async dns in chrome?
With a dns adblock on a pichole, I suffered with it,
try it in mozilla