No DNS cache

[paul1149]

Though it has been better than it was, the regression lasted all day, and I was getting delays on maybe half the sites.

On a hunch, I entered the OpenDNS address directly in the network properties applet, rather than referring the network to the router's DNS spec, then cycled the network off and on. The result was instant, and in every case my lookups were lightning fast.

So I'm not sure what's at play here. Either the router is defective and the anomalies between linux and windows box performance were just coincidence, or windows is doing a better job of talking to the router.

[torreydale]

It shouldn't be this way.  As a workaround, I mentioned manually entering the OpenDNS servers in an earlier post (reply #3).  The resolv.conf file might show those OpenDNS server addresses now instead of 127.0.0.1.

Perhaps you can summarize your experience and report this as a Linux Lite bug.

[paul1149]

Thanks. Resolve.conf still shows the 127.... ip, so the network connections / ipv4 DNS setting evidently does not affect that. Before I would file a bug I think I would need to double check the performance of the windows boxes, and also try a different router. I will do that if I can, but I'm not sure when that would be.

(congrats on your promotion, BTW!)
BW

[torreydale]

Mine still says 127.0.0.1.  My mistake on that.  In reflection on my reply #3, that was the reason I had to manually enter in an Additional DNS Server.  My change to that file wouldn't stay persistent.  So I added 8.8.8.8 as suggested by the folks at OpenVPN Access Server support.

[paul1149]

I finally got a chance to double-check a windows box on this LAN, and it has no problem using the router-configured DNS servers. So I think we have a bug here. But I don't see where to file it.

Basically, I expected leaving the DNS server blank in Network Connections would cause LL to look to the default gateway for DNS specs. But doing so yields no ability to find DNS at all. The DNS server must be specced in LL's Network Connections.

And speccing the default gateway, the router, as the DNS server in Network Connections works, but only with a lot of "resolving host" delays. As soon as I enter the ultimate DNS server in Network Connections, lookups are instant.

I'm on LL 2.8 x64, using an ethernet connection.

[LL-user]

Hi paul1149,

If I'm not mistaken, I can't see in the whole thread mentioned - and therefore maybe not considered/looked at? - the DNS cache that is actually used in Ubuntu and as far as I know also in LL: dnsmasq

Have you checked this?

Hope that helps solve the riddles

[paul1149]

Hi LL-user,

Isn't that for setting up a DNS server? And if it were the problem here, wouldn't placing the remote DNS server directly in Network Connections not make a difference?

[torreydale]

You can report a bug by going to the main Linux Lite website (www.freecinema2022.gq).  Under the Support section, there is a link for Bugs.

[Valtam]

There's no need to report this in our 'Bugs' section. The answer lies at the user end or with the actual software ( Ubuntu maintainer)

[paul1149]

Ok. too late. I just filed it.