DNS resolver is slow

[ajb]

[ajb]

Katon 0.7.0, Yosemite, Google Chrome.

[typicode]

After spending a few hours downloading Yosemite, finally got my hand on it :)
Will try to reproduce.

[typicode]

I've got the same problem. I've noticed that with Chrome, I'm getting 2 DNS requests for the same host every time.

[typicode]

I've updated the firewall script based on the recent Pow update. It seems to have fixed it.
It's available in v0.8.1

[ajb]

just installed v0.8.1, still seeing this issue 😢

[typicode]

Going back to code and tests then 😅 and sorry again

[typicode]

I'm running out of ideas on this one.

So if someone wants to help or have ideas, I'd really appreciate.

[ajb]

Would you be willing to ping folks from other projects? Maybe someone from a similar project would be willing to help out. Have you talked to the DNS resolver folks, too?

[assaf]

At least in Yosemite, .ka domains don't get cached locally. If you run curl -I -v you will see this in the console:

* Hostname was NOT found in DNS cache
*   Trying 127.0.0.1...

This may be related to the fact that nslookup, host and dig can't resolve .ka domains either.

Basically, every single page load is always trying to resolve the hostname. It starts with Katon, gets hold of the A record, and then runs through all the remaining DNS servers looking for an AAAA record, eventually gives up and settles on using the A record.

With this change, it gets both A and AAAA records from Katon, and immediately resolves the lookup.

[ajb]

👍 thank you, @assaf!

[typicode]

It works, thanks a lot 👍

[jfirebaugh]

It still doesn't work for me in 0.8.4. Loading .ka domains in Chrome, Yosemite 10.10.1 takes many minutes, with Chrome stuck on "Resolving host..."

[jfirebaugh]

False alarm. After restarting Chrome it works much better.

[typicode]

@jfirebaugh cool :) just in case, you may want to update to 0.8.5 it includes another fix from @assaf on DNS #53