{"id":293,"date":"2009-12-19T16:59:18","date_gmt":"2009-12-19T15:59:18","guid":{"rendered":"http:\/\/signal.eu.org\/blog\/?p=293"},"modified":"2009-12-19T17:03:05","modified_gmt":"2009-12-19T16:03:05","slug":"google-internetactu-et-ovh","status":"publish","type":"post","link":"https:\/\/signal.eu.org\/blog\/2009\/12\/19\/google-internetactu-et-ovh\/","title":{"rendered":"Google, Internetactu et OVH&#8230;"},"content":{"rendered":"\n<div class=\"twitter-share\"><a href=\"https:\/\/twitter.com\/intent\/tweet?via=pbeyssac\" class=\"twitter-share-button\">Tweet<\/a><\/div>\n<p>Exemple v\u00e9cu ce jour, qui (m&#8217;)aide \u00e0 comprendre en quoi le <a href=\"http:\/\/signal.eu.org\/blog\/2009\/12\/04\/google-public-dns\/\">DNS Google<\/a> peut, \u00e9ventuellement, servir \u00e0 quelque chose. Les fournisseurs d&#8217;acc\u00e8s ont bon dos (il est de bon ton de leur tirer dessus, et ni Google ni OpenDNS ne se sont g\u00ean\u00e9s), mais souvent ce sont les sites d&#8217;origine qui ne g\u00e8rent pas correctement leur DNS.<\/p>\n<p>Ainsi, aujourd&#8217;hui tous les serveurs DNS du site <a href=\"http:\/\/www.internetactu.net\/\">internetactu.net<\/a> (deux serveurs DNS chez l&#8217;h\u00e9bergeur \u00e0 bas co\u00fbt <a href=\"http:\/\/www.ovh.net\/\">OVH<\/a>) sont actuellement en carafe :<\/p>\n<blockquote><p>% dig www.internetactu.net<br \/>\n;; -&gt;&gt;HEADER&lt;&lt;- opcode: QUERY, status: SERVFAIL, id: 17958<\/p>\n<p>% dig ns internetactu.net<br \/>\n;; -&gt;&gt;HEADER&lt;&lt;- opcode: QUERY, status: SERVFAIL, id: 14783<\/p>\n<p>% dig +norecurse ns internetactu.net<br \/>\n;; AUTHORITY SECTION:<br \/>\ninternetactu.net.\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 172652\u00a0 IN\u00a0\u00a0\u00a0\u00a0\u00a0 NS\u00a0\u00a0\u00a0\u00a0\u00a0 ns352862.ovh.net.<br \/>\ninternetactu.net.\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 172652\u00a0 IN\u00a0\u00a0\u00a0\u00a0\u00a0 NS\u00a0\u00a0\u00a0\u00a0\u00a0 sdns1.ovh.net.<\/p><\/blockquote>\n<p>Qu&#8217;en pense OpenDNS ?<\/p>\n<blockquote><p>% dig @208.67.222.222\u00a0 www.internetactu.net<br \/>\n;; connection timed out; no servers could be reached<\/p><\/blockquote>\n<p>Pas glorieux&#8230;<\/p>\n<p>Qu&#8217;en pense Google Public DNS ?<\/p>\n<blockquote><p>% dig @8.8.8.8 www.internetactu.net<br \/>\nwww.internetactu.net.\u00a0\u00a0 72852\u00a0\u00a0 IN\u00a0\u00a0\u00a0\u00a0\u00a0 A\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 91.121.87.216<\/p><\/blockquote>\n<p>La bonne r\u00e9ponse.<\/p>\n<p>La question \u00ab naturelle \u00bb que l&#8217;on peut se poser, et qui n&#8217;est pas neutre au vu de ce qui pr\u00e9c\u00e8de : est-ce un effet \u00ab normal \u00bb de cache DNS, ou Google effectue-il de la mise en cache \u00ab agressive \u00bb <em>et<\/em> au del\u00e0 des sp\u00e9cifications du DNS pour donner des r\u00e9ponses de meilleure qualit\u00e9 ? (la mise en cache agressive est av\u00e9r\u00e9e, elle a \u00e9t\u00e9 annonc\u00e9e lors de l&#8217;ouverture du service).<\/p>\n<p>Ironie supr\u00eame, j&#8217;ai d\u00e9couvert la panne qui pr\u00e9c\u00e8de en tentant d&#8217;aller consulter sur ledit site des articles sur <a href=\"http:\/\/www.internetactu.net\/2009\/12\/15\/une-societe-de-la-requete-14-de-la-googlisation-de-nos-vies\/\">la Googlisation de nos vies<\/a> (trouv\u00e9s via un article du <a href=\"http:\/\/standblog.org\/blog\/post\/2009\/12\/18\/En-vrac\">Standblog<\/a> trouv\u00e9 via <a href=\"http:\/\/www.bortzmeyer.org\/\">St\u00e9phane<\/a>).<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Exemple v\u00e9cu ce jour, qui (m&#8217;)aide \u00e0 comprendre en quoi le DNS Google peut, \u00e9ventuellement, servir \u00e0 quelque chose. Les fournisseurs d&#8217;acc\u00e8s ont bon dos (il est de bon ton de leur tirer dessus, et ni Google ni OpenDNS ne se sont g\u00ean\u00e9s), mais souvent ce sont les sites d&#8217;origine qui ne g\u00e8rent pas correctement &hellip; <a href=\"https:\/\/signal.eu.org\/blog\/2009\/12\/19\/google-internetactu-et-ovh\/\" class=\"more-link\">Continue reading <span class=\"screen-reader-text\">Google, Internetactu et OVH&#8230;<\/span> <span class=\"meta-nav\">&rarr;<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[15,13,4],"tags":[],"_links":{"self":[{"href":"https:\/\/signal.eu.org\/blog\/wp-json\/wp\/v2\/posts\/293"}],"collection":[{"href":"https:\/\/signal.eu.org\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/signal.eu.org\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/signal.eu.org\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/signal.eu.org\/blog\/wp-json\/wp\/v2\/comments?post=293"}],"version-history":[{"count":3,"href":"https:\/\/signal.eu.org\/blog\/wp-json\/wp\/v2\/posts\/293\/revisions"}],"predecessor-version":[{"id":295,"href":"https:\/\/signal.eu.org\/blog\/wp-json\/wp\/v2\/posts\/293\/revisions\/295"}],"wp:attachment":[{"href":"https:\/\/signal.eu.org\/blog\/wp-json\/wp\/v2\/media?parent=293"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/signal.eu.org\/blog\/wp-json\/wp\/v2\/categories?post=293"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/signal.eu.org\/blog\/wp-json\/wp\/v2\/tags?post=293"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}