Cloudflare pokrenuo besplatni, a k tome i najbrži

kako ovdje nema komentara?

ovo mi se baš čini zanimljivim.

ako je netko voljan da ovo malo objasni valjalo bi..

 Cloudflare vec ima profitabilan biznis model, DNS je samo bi-produkt njihove infrastrukture, koji su odlucili podijeliti sa narodom.

Goodwill, i besplatna reklama.

Pa nisu oni prvi besplatni. Imaš puno takvih ponuđača

“DNS Resolvers Performance compared: CloudFlare x Google x Quad9 x OpenDNS”https://medium.com/@nykolas.z/dns-resolvers-performance-compared-cloudflare-x-google-x-quad9-x-opendns-149e803734e5

 A i cloudflare ima servere u Zagrebu (ne znam jel tu i DNS)

https://blog.cloudflare.com/dobar-dan-hrvatska-announcing-cloudflares-zagreb-data-center/

Inace, cloudflare mi je dosta interesantna firma te i sam koristim njihove (free) usluge za svoje domene.

Cak sam krenio pisati neki CLI "frontend" za njihove API-e i jednostavnije koristenje (jednom komandom mjenjanje DNS-a da pokazuje na trenutnu public IP adresu), no ogorcen cinjenicom da nemam public IP adresu na Optimi nego sam iza NAT-a sam prestao.

Ahm... Upitno je koliko su bolji od svih ostalih.

WHAT INFORMATION DOES THE CLOUDFLARE RESOLVER COLLECT?

Cloudflare will collect only the following anonymized DNS query data that is sent to the Cloudflare Resolver:

• Timestamp
• IP Version (IPv4 vs IPv6)
• Resolver IP address + Destination Port
• Protocol (TCP, UDP, TLS or HTTPS)
• Query Name
• Query Type
• Query Class
• Query Rd bit set
• Query Do bit set
• Query Size
• Query EDNS enabled
• EDNS Version
• EDNS Requested Max Buffer Size
• EDNS Nsid
• Response Type (normal, timeout, blocked)
• Response Code
• Response Size
• Records in Response
• Response Time in Milliseconds
• Response served from Cache
• DNSSEC Validation State (secure, insecure, bogus, indeterminate)
• PoP ID
• Server ID

pade mi na pamet, ako oni vrte dns servere, sto ja ne bih mogao vlastiti, na svom kompu? Samo za moje potribe?

recimo ovako nes?

Možda grešim, ali letimičnim pregledom liste bih rekao da ne čuvaju apsolutno ništa vezano za pošiljaoca DNS upita, osim tehnikalija tipa verzije IP protokola i da li se radilo o TCP, UDP ili nekom drugom protokolu. Dakle, na kraju nekog perioda, imaće da je preko njih izvršeno xyz DNS upita gde je destinacija bio Google, Bug.hr, razni info portali, PornHub itd, ali neko sa uvidom u tu bazu neće imati pojma ko je te upite pravio.

 + u linku gore (onaj blog post sto je kolega stavio) ima i objasnjeno da cuvaju 24h iz razloga: "While we need some logging to prevent abuse and debug issues, we couldn't imagine any situation where we'd need that information longer than 24 hours."

Pa i nije baš najbrži s naše lokacije.

Ping 1.1.1.1 - 34ms

Ping 8.8.8.8 - 29ms

Ping t-comov - 20ms

Iz Cloudflarea su rekli kako je DNS anycast sa svih lokacija, što znači da se koriste i serveri u Zagrebu. Napravi traceroute (cmd -> tracert 1.1.1.1 -> enter) i vidi preko čega ti sve ide da dođe do DNS-a. 

Ja idem preko Beča.

Ali mi puno brže otvara stranice.

 Što se tiče surfanja, bez DNS-a ne možeš ništa!

Njega dobija tvoj router prilikom povezivanja s providerom, najčešće onaj od samog providera.

Ali, sama tehnologija DNSa je jako razgranata. 

Postoji 13 (ako se ne varam) glavnih (korijenskih) DNS poslužitelja na svijetu. 

"ispod" svakog je ogroman broj imenskih poslužitelja za .com, .hr, .gov, .....

I onda ispod svakog od njih lokalni DNS poslužitelji, npr od većih firmi, npr Amazonovi koji imaju svoje DNS servere po različitim kontinentima, za web, mail...

I takve server imaju i internet provideri.

Ti hoćeš pristupiti www.bug.hr, i onda tvoj komp pogleda adresu DNSa (koju je pokupio iz routera), na nju pošalje upit i ako je tamo, počinje uspostavljanje veze..

Ako nije, onda taj DNS server uputi poziv prema korijensom DNS-u... pa ga ovaj uputi na imenski, pa ga ovaj uputi... itd...

I na kraju ti dobiješ adresu servera na kojeg možeš ići.

Ovo je tehnologija koja ima potencijalne velike mogućnosti da bude meta napada. Padnu svi glavni DNS serveri i nema više interneta.

Ali, toliko je razgranato, ima mnogo kopija servera, da se još nikad nije dogodilo da padne jedan od korijeskih servera.

Ako nisi drugačije upisao, tvoj PC ima zapisanu adresu DNS servera iz routera.

Ako hoćeš ručno upisati DNS server, onda prati ove korake:

https://www.windowscentral.com/how-change-your-pcs-dns-settings-windows-10

Kako kome, trebao bi pokrenut namebench, al mi se trenutno ne instalirava.

ante@Ratatoskr ~ % ping 1.1.1.1
PING 1.1.1.1 (1.1.1.1) 56(84) bytes of data.
64 bytes from 1.1.1.1: icmp_seq=1 ttl=57 time=4.02 ms
64 bytes from 1.1.1.1: icmp_seq=2 ttl=57 time=4.29 ms
64 bytes from 1.1.1.1: icmp_seq=3 ttl=57 time=4.45 ms
64 bytes from 1.1.1.1: icmp_seq=4 ttl=57 time=4.51 ms
^C
--- 1.1.1.1 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3004ms
rtt min/avg/max/mdev = 4.028/4.322/4.516/0.187 ms

ante@Ratatoskr ~ % ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=54 time=20.9 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=54 time=21.0 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=54 time=20.3 ms
64 bytes from 8.8.8.8: icmp_seq=4 ttl=54 time=20.3 ms
64 bytes from 8.8.8.8: icmp_seq=5 ttl=54 time=20.1 ms
^C
--- 8.8.8.8 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4006ms
rtt min/avg/max/mdev = 20.141/20.550/21.008/0.365 ms

ante@Ratatoskr ~ % ping 8.8.4.4
PING 8.8.4.4 (8.8.4.4) 56(84) bytes of data.
64 bytes from 8.8.4.4: icmp_seq=1 ttl=54 time=21.4 ms
64 bytes from 8.8.4.4: icmp_seq=2 ttl=54 time=19.9 ms
64 bytes from 8.8.4.4: icmp_seq=3 ttl=54 time=19.5 ms
64 bytes from 8.8.4.4: icmp_seq=4 ttl=54 time=20.6 ms
^C
--- 8.8.4.4 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3005ms
rtt min/avg/max/mdev = 19.584/20.406/21.454/0.721 ms

ante@Ratatoskr ~ % ping 1.0.0.1
PING 1.0.0.1 (1.0.0.1) 56(84) bytes of data.
64 bytes from 1.0.0.1: icmp_seq=1 ttl=57 time=3.74 ms
64 bytes from 1.0.0.1: icmp_seq=2 ttl=57 time=4.05 ms
64 bytes from 1.0.0.1: icmp_seq=3 ttl=57 time=3.38 ms
64 bytes from 1.0.0.1: icmp_seq=4 ttl=57 time=4.35 ms
64 bytes from 1.0.0.1: icmp_seq=5 ttl=57 time=5.63 ms
^C
--- 1.0.0.1 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4005ms
rtt min/avg/max/mdev = 3.387/4.234/5.630/0.770 ms

Ja ću još neko vrijeme nastaviti koristiti Google Public DNS dok 1.1.1.1 ne srede do kraja. Čitao sam na njihovom forumu da neke domene ne resolva npr. .mil, stranice s tim nastavkom se ne otvaraju, moguće je da ima još više tih domena. Danas je DNS na neko vrijeme prestao s radom (iz nekog razloga). Za Google-ove sam siguran da stalno rade i nikad nisam imao ni najmanjih problema s njihovim DNS-ovima.

Što se tiče Google-ove politike privatnosti:

"Google Public DNS stores two sets of logs: temporary and permanent. The temporary logs store the full IP address of the machine you're using. We have to do this so that we can spot potentially bad things like DDoS attacks and so we can fix problems, such as particular domains not showing up for specific users.

We delete these temporary logs within 24 to 48 hours.

In the permanent logs, we don't keep personally identifiable information or IP information. We do keep some location information (at the city/metro level) so that we can conduct debugging, analyze abuse phenomena. After keeping this data for two weeks, we randomly sample a small subset for permanent storage.

We don't correlate or combine information from our temporary or permanent logs with any personal information that you have provided Google for other services.

Finally, if you're interested in knowing what else we log when you use Google Public DNS, here is the full list of items that are included in our permanent logs:

• Request domain name, e.g. www.google.com
• Request type, e.g. A (which stands for IPv4 record), AAAA (IPv6 record), NS, MX, TXT, etc.
• Transport protocol on which the request arrived, i.e. TCP, UDP, or HTTPS
• Client's AS (autonomous system or ISP), e.g. AS15169
• User's geolocation information: i.e. geocode, region ID, city ID, and metro code
• Response code sent, e.g. SUCCESS, SERVFAIL, NXDOMAIN, etc.
• Whether the request hit our frontend cache
• Whether the request hit a cache elsewhere in the system (but not in the frontend)
• Absolute arrival time in seconds
• Total time taken to process the request end-to-end, in seconds
• Name of the Google machine that processed this request, e.g. machine101
• Google target IP to which this request was addressed, e.g. one of our anycast IP addresses (no relation to the user's IP)"

U često postavljenim pitanjima piše ovo:

"Does Google Public DNS offer the ability to block or filter out unwanted sites?

- No. Google Public DNS is purely a DNS resolution and caching server; it does not perform any blocking or filtering of any kind, except that it may not resolve certain domains in extraordinary cases if we believe this is necessary to protect Google’s users from security threats. But we believe that blocking functionality is usually best performed by the client. If you are interested in enabling such functionality, you should consider installing a client-side application or browser add-on for this purpose."

"Are there any cross-product dependencies with Google Public DNS?

- Google Public DNS is an independent service."

"Do I need a Google Account to use Google Public DNS?

- No."

"Will Google Public DNS be used to serve ads in the future?

- No. We are committed to preserving the integrity of the DNS protocol. Google Public DNS will never return the address of an ad server for a non-existent domain."

"What information does Google log when I use the Google Public DNS service?

- The Google Public DNS privacy page has a complete list of information that we collect. Google Public DNS complies with Google's main privacy policy, available at our Privacy Center.

Your client IP address is only logged temporarily (erased within a day or two), but information about ISPs and city/metro-level locations are kept longer for the purpose of making our service faster, better, and more secure."

"Is any of the information collected stored with my Google account?

- No."

"Does Google share the information it collects from the Google Public DNS service with anyone outside Google?

- No, except in the limited circumstances described in Google's privacy policy, such as legal processes and enforceable governmental requests. (See also Google's Transparency Report on user data requests.)"

"Does Google correlate or combine information from temporary or permanent logs with any personal information that I have provided Google for other services?

- No."

https://developers.google.com/speed/public-dns/privacy

https://developers.google.com/speed/public-dns/faq