Am I missing something? I have enabled DNS Leak Protection (Which works well, by the way!) and as a result, my speed is slowed down to a tenth of what it was! Can you help?
Only for IPv4, as PIA doesn't support IPv6 at all. No need to restart, but you might want to reboot anyway if it doesn't work just in case.
Basically what happens is that Windows still tries to use your normal DNS despite PIA having set its own DNS on the TAP adapter. DNS Leak Protection blocks the DNS requests from going out, but depending on what Windows decided it feels like doing, it looks like it's still trying to use your ISP first and waits for this to fail before it uses PIA's ones. Setting PIA's DNS to the normal adapter forces it to use PIA's DNS as it will then have no other option in the first place, eliminating the delay.
Try just changing your DNS to PIA DNS. Do this in your windows NIC.
209.222.18.222 209.222.18.218
See if that does anything for you. Could be a server issue.
this is under the isp's network and not the pia tap driver correct? Also, If I have it changed to google's DNS would that be ok too or would that leak my ISP's dns somehow.
Try just changing your DNS to PIA DNS. Do this in your windows NIC.
209.222.18.222 209.222.18.218
See if that does anything for you. Could be a server issue.
this is under the isp's network and not the pia tap driver correct? Also, If I have it changed to google's DNS would that be ok too or would that leak my ISP's dns somehow.
Just the ISP's DNS should do.
I think using Google's DNS might be contributing to the issue but I haven't verified so. However, you have manually assigned DNS and automatically assigned DNS (on the TAP via PIA), so it would kinda make sense for Windows to pick the manually assigned DNS as a priority.
You can always put PIA's DNS on both and see if it helps and if it doesn't revert back.
Comments
209.222.18.222
209.222.18.218
See if that does anything for you. Could be a server issue.
Also, do I need to restart something when finished?
Basically what happens is that Windows still tries to use your normal DNS despite PIA having set its own DNS on the TAP adapter. DNS Leak Protection blocks the DNS requests from going out, but depending on what Windows decided it feels like doing, it looks like it's still trying to use your ISP first and waits for this to fail before it uses PIA's ones. Setting PIA's DNS to the normal adapter forces it to use PIA's DNS as it will then have no other option in the first place, eliminating the delay.
I think using Google's DNS might be contributing to the issue but I haven't verified so. However, you have manually assigned DNS and automatically assigned DNS (on the TAP via PIA), so it would kinda make sense for Windows to pick the manually assigned DNS as a priority.
You can always put PIA's DNS on both and see if it helps and if it doesn't revert back.