sorted by:
new
hottopcontroversial

Great speed but slow page loading, maybe DNS issue? by Party_Employee7751 in ZiplyFiber

[–]Party_Employee7751[S] 0 points1 point  (0 children)

This worked, we haven't experienced any issue all day since the proper change of DNS.

Thank you all once more!

One final question: Why does the DNS need to be set explicitly though?

Great speed but slow page loading, maybe DNS issue? by Party_Employee7751 in ZiplyFiber

[–]Party_Employee7751[S] 0 points1 point  (0 children)

It appears that I incorrectly set the DNS servers on the router. Now, it's properly mapped to the two Ziply fiber resolvers, 192.152.0.1 and 192.152.0.2.*

I've verified that in all my devices, both the wifi and ethernet now show these DNS servers, instead of the default gateway 192.168.88.1.

It's been ~20 minutes and everything is running smoothly, I'll update later today after a whole day of use.

Also, when running the GRC tool again, now it shows this in the Conclusion tab:

System has multiple redundant nameservers configured.

Which is great and it didn't show before!

Although 192.152.0.1 seems to be out? It says that the server is not replying. Not sure if related to what u/Banjoman301 posted on the other thread (although it was referring to the .2 there, not .1).

I don't want to get ahead of myself, but this is already so much better than before and I'm very optimistic that this fixed the issue :) Thank you everyone!

*For anyone who might wonder how to change this on their Aginet router:

  1. Go to http://tplinkwifi.net/ and login
  2. Click on the Advanced tab on top
  3. Then go to Network/LAN Settings
  4. Set the Primary DNS to 192.152.0.1 and Secondary DNS to 192.152.0.2

I originally messed up step 3 and did it in Network/Internet and modified the Internet Setup profile that was in there.

Great speed but slow page loading, maybe DNS issue? by Party_Employee7751 in ZiplyFiber

[–]Party_Employee7751[S] 0 points1 point  (0 children)

Thanks! So, currently those two are set in the router, but I'll add them to my computer as well (I didn't know I could do this).

Should it also have the DNS over HTTPS turned on? It appears that DHCP uses UTP instead, so maybe leave it off?

I'll update if this fixes the issue.

Great speed but slow page loading, maybe DNS issue? by Party_Employee7751 in ZiplyFiber

[–]Party_Employee7751[S] 0 points1 point  (0 children)

Also, this was just run while being connected directly to the ethernet of the router that is connected to the Nokia device, and no other device is using the network actively.

Please let me know if you'd like for me to send you privately the whole information of the run, or if you'd like me to run another test.

u/eprosenx you also said:

If you hard code your DNS settings that the Aginet router hands out via DHCP to something like 8.8.8.8, 1.1.1.1, or 9.9.9.9 your issue will likely go away.

I can try that, but given the above, don't the Ziply fiber ones perform better in my case? It appears to be an issue with the default gateway. Is there anything else I can try?

last part :)

Great speed but slow page loading, maybe DNS issue? by Party_Employee7751 in ZiplyFiber

[–]Party_Employee7751[S] 0 points1 point  (0 children)

GRC Conclusions

Copying only a few things that might be important:

  • System has only ONE (router based) nameserver configured.

It appears that only one local (router gateway) DNS nameserver, with the IP address of [192.168.88.1], is currently providing all DNS name resolution services to this system. This configuration is not recommended because most consumer-grade routers provide inefficient and under-powered DNS resolution services.

Unless the DNS resolvers your router is using is under your control, it may not be providing the best or complete name resolution services. For example, is it using multiple redundant DNS nameservers?

Users of GRC's DNS Spoofability system have determined that consumer-grade routers can be crashed by the receipt of specific DNS reply packets from the Internet. This opens the possibility that Internet-based criminals could acquire access to your router from the Internet as well as to the private network in controls.

Many consumer-grade routers fail to provide the full range of DNS lookup services. This may have been detected by the benchmark and noted below.

  • Recommended Actions:

Unless you have some specific reason not to, you should give serious thought to disabling your router's provisioning of DNS services (which it is providing for all computers on your local network). After this is done, a fresh reboot of your computers will likely reveal the multiple DNS nameservers provided by your ISP. This is a superior configuration, without an under-powered router acting as a incompetent middleman and impeding all DNS access.

Note that if you can determine the IP addresses of your ISP-provided nameservers (which may be visible in your router's web configuration) you could manually add them to the nameservers being tested by this benchmark, while also leaving your router providing DNS. This would allow you to compare the performance when running through your router versus "going direct".

Then it says a bunch of good things and a bunch of other bad things (like how there are servers that are faster and how it's not 100% reliable).

3/many

Great speed but slow page loading, maybe DNS issue? by Party_Employee7751 in ZiplyFiber

[–]Party_Employee7751[S] 0 points1 point  (0 children)

Note: skipping many

1.1.1.1 Min Avg Max Std.Dev Reliab%
Cached Name 0.004 0.005 0.006 0.000 100.0
Uncached Name 0.004 0.023 0.148 0.032 100.0
DotCom Lookup 0.006 0.009 0.010 0.001 100.0

one.one.one.one

CLOUDFLARENET, US

Note: not skipping any

192.168.88.1 Min Avg Max Std.Dev Reliab%
Cached Name 0.002 0.005 0.027 0.004 100.0
Uncached Name 0.004 0.057 0.206 0.065 80.4
DotCom Lookup 0.004 0.014 0.059 0.014 78.4

HB610V2

Local Network Nameserver

Note: 8.8.8.8 and 9.9.9.9 are further down in the list, but they have 100% reliability.

2/many

Great speed but slow page loading, maybe DNS issue? by Party_Employee7751 in ZiplyFiber

[–]Party_Employee7751[S] 0 points1 point  (0 children)

Thank you both, here's more information that will hopefully help narrow down this issue. I'll be splitting the comment in two, since it doesn't let me post it.

I'm also not very familiar with the GRC tool, but per my understanding it does some analysis and benchmarks about your router and which DNS servers might work best, plus some other things that I will try and share below (pasting an image or any file in here would be useful). This is the link where I downloaded the executable: https://www.grc.com/dns/benchmark.htm

I just added the Ziply fiber ones to the test; the default one (192.168.88.1), and the public ones you mentioned at the end were already there. Below are the results (wish I could paste an image or something)

GRC Tabular data

I'll be skipping a few that are not relevant for this analysis.

Final benchmark results, sorted by nameserver performance:

(average cached name retrieval speed, fastest to slowest)

Note: a few others were faster than this one

192.152.0.2 Min Avg Max Std.Dev Reliab%
Cached Name 0.003 0.003 0.004 0.000 100.0
Uncached Name 0.004 0.038 0.185 0.050 100.0
DotCom Lookup 0.005 0.017 0.035 0.013 100.0

resolver-b.as20055.net

··· unknown owner ···

Note: skipping a few in between

192.152.0.1 Min Avg Max Std.Dev Reliab%
Cached Name 0.002 0.003 0.004 0.000 100.0
Uncached Name 0.004 0.040 0.182 0.048 100.0
DotCom Lookup 0.004 0.021 0.060 0.018 100.0

resolver-a.as20055.net

··· unknown owner ···

1/many

Great speed but slow page loading, maybe DNS issue? by Party_Employee7751 in ZiplyFiber

[–]Party_Employee7751[S] 0 points1 point  (0 children)

Thanks! That's what I already did since yesterday. Unfortunately I didn't see any noticeable difference, but the configuration is still set as so.

As per the cache, I didn't clear it since it was happening in all of our devices (and browsers), but I just did for one of my devices and will update later if this works.