You're wrong. People getting angry at West and talking about war. Including nuclear.
I have no idea what happened.
They work on it https://github.com/WireGuard/wireguard-windows/commits/maste....
> 802.11ac is a 5-GHz-only technology https://www.cisco.com/c/dam/en/us/products/collateral/wirele...
Aren't o-o.myaddr.l.google.com is intended for troubleshooting and should show correct ECS? o-o.myaddr.test.l.google.com always show correct ECS.
dig @9.9.9.11 +short ;; connection timed out; no servers could be reached dig @9.9.9.12 +short ;; connection timed out; no servers could be reached
Should, but does not. dig @8.8.8.8 o-o.myaddr.test.l.google.com txt +short "74.125.46.11" "edns0-client-subnet 94.181.44.185/32" dig @9.9.9.10 o-o.myaddr.test.l.google.com txt +short "2620:171:57::240"
I have static public /32. My ISP intercepting DNS traffic for censorship purposes. But i strongly doubt that this traffic is forwarded somewhere. [user@v-fed-1 ~]$ dig txt o-o.myaddr.test.l.google.com @8.8.8.8 +short…
Load balancing of ECS?
I think i have questions to Google: [user@v-fed-1 ~]$ dig txt o-o.myaddr.l.google.com @8.8.8.8 +short "74.125.46.8" "edns0-client-subnet 92.223.114.166/32" [user@v-fed-1 ~]$ dig txt o-o.myaddr.l.google.com @8.8.8.8…
ISP can do anything with you DNS traffic. That's why Cloudflare DNS support DNS-over-TLS.
Quad9 not friendly to CDN. $ dig +short @8.8.8.8 icnerd-1e5f.kxcdn.com p-rumo00.kxcdn.com. 188.42.31.172 $ dig +short @1.1.1.1 icnerd-1e5f.kxcdn.com p-rumo00.kxcdn.com. 188.42.31.172 $ dig +short @9.9.9.9…
It does. $ dig @9.9.9.10 +dnssec +short verisignlabs.com 72.13.58.64 A 8 2 3600 20180413202737 20180330202737 31485 verisignlabs.com. KrnT9i6qytaYWDZWThBmBwc6anOmawNxJTxmSlpaY3L7Yfupga9FS70l…
Not exactly the answer to your question but Cloudflare DNS support DNS-over-TLS. You can use Stubby (getdns) to encrypt your DNS queries.
Don't know about other OEMs but Xiaomi's implementation is awful.
You're wrong. People getting angry at West and talking about war. Including nuclear.
I have no idea what happened.
They work on it https://github.com/WireGuard/wireguard-windows/commits/maste....
> 802.11ac is a 5-GHz-only technology https://www.cisco.com/c/dam/en/us/products/collateral/wirele...
Aren't o-o.myaddr.l.google.com is intended for troubleshooting and should show correct ECS? o-o.myaddr.test.l.google.com always show correct ECS.
dig @9.9.9.11 +short ;; connection timed out; no servers could be reached dig @9.9.9.12 +short ;; connection timed out; no servers could be reached
Should, but does not. dig @8.8.8.8 o-o.myaddr.test.l.google.com txt +short "74.125.46.11" "edns0-client-subnet 94.181.44.185/32" dig @9.9.9.10 o-o.myaddr.test.l.google.com txt +short "2620:171:57::240"
I have static public /32. My ISP intercepting DNS traffic for censorship purposes. But i strongly doubt that this traffic is forwarded somewhere. [user@v-fed-1 ~]$ dig txt o-o.myaddr.test.l.google.com @8.8.8.8 +short…
Load balancing of ECS?
I think i have questions to Google: [user@v-fed-1 ~]$ dig txt o-o.myaddr.l.google.com @8.8.8.8 +short "74.125.46.8" "edns0-client-subnet 92.223.114.166/32" [user@v-fed-1 ~]$ dig txt o-o.myaddr.l.google.com @8.8.8.8…
ISP can do anything with you DNS traffic. That's why Cloudflare DNS support DNS-over-TLS.
Quad9 not friendly to CDN. $ dig +short @8.8.8.8 icnerd-1e5f.kxcdn.com p-rumo00.kxcdn.com. 188.42.31.172 $ dig +short @1.1.1.1 icnerd-1e5f.kxcdn.com p-rumo00.kxcdn.com. 188.42.31.172 $ dig +short @9.9.9.9…
It does. $ dig @9.9.9.10 +dnssec +short verisignlabs.com 72.13.58.64 A 8 2 3600 20180413202737 20180330202737 31485 verisignlabs.com. KrnT9i6qytaYWDZWThBmBwc6anOmawNxJTxmSlpaY3L7Yfupga9FS70l…
Not exactly the answer to your question but Cloudflare DNS support DNS-over-TLS. You can use Stubby (getdns) to encrypt your DNS queries.
Don't know about other OEMs but Xiaomi's implementation is awful.