Slow dns resolution

dgrant88 · 03-10-2019, 10:01 PM

I've tried feverishly to work with Linux. I came from Windows and for about 2 months and I do mean months....tried to resolve this slowwwww dns resolution due to that stupid dnsmasq. I modified my resolv.conf, did the #dnsmasq, modified the interfaces file, played with the dhclient.conf...different distros from Mint, Ubuntu, Arch, Lite, Fedora. All I was searching for was a distro whose name resolution was not jacked. The little blue web browsers circle just turns and turns and turns, stops, ends the search and on occasion starts again with the blue circle and finally, and I do mean finally...resolves the page. I like Linux, I really do but I just can't take their solution to dns. It sucks! Period. Returning to Windows rather reluctantly I might add. I tried to embrace, I really have so if anyone has a solution...oh yeah, I also removed network manager as well. What version am I using you ask...ALL OF THEM. Sure, Linux is my choice hands down but I'd really like to enjoy my online experience without having to wait and wait and wait and so on. ....research this, modify, configure and reconfigure that.....know what, Windows just works. Blazing speed resolving web pages even with their over-coded severely bloated Edge browser.

rtmistler · 03-11-2019, 07:00 AM

Nice to hear from you dgrant88,

It is difficult to determine what you're trying to do and also why you're using dnsmask at all.

Dnsmask is a lightweight DNS forwarder and DHCP server. Something you'd use if your ISP does not provide these services, or if you are hosting a small network. Most ISPs provide adequate network services where you do not need to host DNS. Therefore any explanation why you are using dnsmask would be helpful.

An initial guess is that you are using a single PC and you are trying to surf the web using your ISP's provided network services.

If this is so, then all of the distribution names you have mentioned, should just work.

How are you attaching to the internet?

JeremyBoden · 03-11-2019, 09:23 AM

dnsmasq is a way of holding an in-core DNS cache.

Try installing dig (if not already loaded).
For some reason xx.com, xxxx.com etc for virtually any number of x's are valid domains

To use dig, either let it use your default DNS setup

Code:

dig xxxxxxxxxxxxxxxxxxxxxx.com

; <<>> DiG 9.10.3-P4-Debian <<>> xxxxxxxxxxxxxxxxxxxxxx.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 62351
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1452
;; QUESTION SECTION:
;xxxxxxxxxxxxxxxxxxxxxx.com.	IN	A

;; ANSWER SECTION:
xxxxxxxxxxxxxxxxxxxxxx.com. 300	IN	A	91.195.240.126

;; Query time: 42 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Mon Mar 11 14:10:58 GMT 2019
;; MSG SIZE  rcvd: 71

or you can specify a specific DNS server

Code:

dig xxxx.com @1.1.1.1
; <<>> DiG 9.10.3-P4-Debian <<>> xxxx.com @1.1.1.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 19888
;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1452
;; QUESTION SECTION:
;xxxx.com.			IN	A

;; ANSWER SECTION:
xxxx.com.		60	IN	A	54.239.164.235
xxxx.com.		60	IN	A	54.239.164.39
xxxx.com.		60	IN	A	54.239.164.145
xxxx.com.		60	IN	A	54.239.164.224

;; Query time: 13 msec
;; SERVER: 1.1.1.1#53(1.1.1.1)
;; WHEN: Mon Mar 11 14:09:00 GMT 2019
;; MSG SIZE  rcvd: 101

If you repeat the same domain twice, the second lookup should be instant(ish) - if your DNS is configured correctly.
Common domains should respond much more quickly than these xxx..xxx.com domains.