{"id":52324,"date":"2019-11-06T00:00:00","date_gmt":"2019-11-05T21:00:00","guid":{"rendered":"https:\/\/prohoster.info\/blog\/blog_prohoster\/hvatit-ispolzovat-smehotvorno-malyj-ttl-dlya-dns"},"modified":"2021-01-02T13:04:14","modified_gmt":"2021-01-02T11:04:14","slug":"hvatit-ispolzovat-smehotvorno-malyj-ttl-dlya-dns","status":"publish","type":"post","link":"https:\/\/prohoster.info\/hr\/blog\/administrirovanie\/hvatit-ispolzovat-smehotvorno-malyj-ttl-dlya-dns","title":{"rendered":"Prestani koristiti smije\u0161no malo TTL za DNS","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p>Niska latencija DNS-a klju\u010dni je faktor za brzu internetsku uslugu. Kako bismo je minimalizirali, va\u017eno je pa\u017eljivo odabrati DNS poslu\u017eitelje i <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/DNSCrypt\/dnscrypt-resolvers\/blob\/master\/v2\/relays.md\">anonimne rilee<\/a><\/noindex>. No, prvo se trebate rije\u0161iti beskorisnih upita.<\/p>\n<p>Zbog toga je DNS izvorno stvoren kao iznimno ke\u0161iran protokol. Administratori zona postavljaju vrijeme \u017eivota (TTL) za pojedina\u010dne zapise, a rezolutori koriste te informacije prilikom pohranjivanja zapisa u memoriju kako bi izbjegli nepotrebni promet.<\/p>\n<p>Je li ke\u0161iranje u\u010dinkovito? Prije nekoliko godina moje malo istra\u017eivanje pokazalo je da nije savr\u0161eno. Pogledajmo trenuta\u010dno stanje.<br \/>\n<noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><br \/>\nZa prikupljanje informacija ispravio sam <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/jedisct1\/encrypted-dns-server\">Encrypted DNS Server<\/a><\/noindex> da sa\u010duva vrijednost TTL-a za odgovor. Ona se definira kao minimalno TTL njegovih zapisa, za svaki dolazni upit. To pru\u017ea dobar pregled raspodjele TTL-a stvarnog prometa, uzimaju\u0107i u obzir i popularnost pojedinih upita. Ispravljena verzija poslu\u017eitelja radila je nekoliko sati.<\/p>\n<p>Rezultantni skup podataka sastoji se od 1&nbsp;583&nbsp;579 zapisa (ime, qtype, TTL, vremenska oznaka). Ovo je ukupna raspodjela TTL-a (osa X predstavlja TTL u sekundama):<\/p>\n<p><img decoding=\"async\" alt=\"Prestani koristiti smije\u0161no malo TTL za DNS\" src=\"\/wp-content\/uploads\/2019\/11\/ce19a1ceb07e1fd2f3b2284f86271eac.jpg\" style=\"display:block;margin: 0 auto;\"><\/p>\n<p>Ako ne ra\u010dunamo neznatan vrh na 86&nbsp;400 (uglavnom za SOA zapise), prili\u010dno je o\u010dito da su TTL-ovi u niskom rasponu. Pogledajmo bli\u017ee:<\/p>\n<p><img decoding=\"async\" alt=\"Prestani koristiti smije\u0161no malo TTL za DNS\" src=\"\/wp-content\/uploads\/2019\/11\/abbe48952b616e1c5bdb18c2dc103dc7.jpg\" style=\"display:block;margin: 0 auto;\"><\/p>\n<p>Dobro, TTL ve\u0107i od 1 sata statisti\u010dki nije zna\u010dajan. Tada se usredoto\u010dimo na raspon od 0-3600:<\/p>\n<p><img decoding=\"async\" alt=\"Prestani koristiti smije\u0161no malo TTL za DNS\" src=\"\/wp-content\/uploads\/2019\/11\/f8a88267e1868a55d9234f66ad8c5dee.jpg\" style=\"display:block;margin: 0 auto;\"><\/p>\n<p>Ve\u0107ina TTL-a je od 0 do 15 minuta:<\/p>\n<p><img decoding=\"async\" alt=\"Prestani koristiti smije\u0161no malo TTL za DNS\" src=\"\/wp-content\/uploads\/2019\/11\/aab650c806097513a5924e5262211ea5.jpg\" style=\"display:block;margin: 0 auto;\"><\/p>\n<p>Prema ve\u0107ini od 0 do 5 minuta:<\/p>\n<p><img decoding=\"async\" alt=\"Prestani koristiti smije\u0161no malo TTL za DNS\" src=\"\/wp-content\/uploads\/2019\/11\/736af4b33b745fb0d5070200fa511426.jpg\" style=\"display:block;margin: 0 auto;\"><\/p>\n<p>To nije ba\u0161 dobro.<\/p>\n<p>Kumulativna raspodjela \u010dini problem jo\u0161 o\u010diglednijim:<\/p>\n<p><img decoding=\"async\" alt=\"Prestani koristiti smije\u0161no malo TTL za DNS\" src=\"\/wp-content\/uploads\/2019\/11\/a3a4f03188dd6dbbf4558076b827f6a5.jpg\" style=\"display:block;margin: 0 auto;\"><\/p>\n<p>U polovici DNS odgovora TTL iznosi 1 minutu ili manje, a kod tri \u010detvrtine&nbsp;\u2014 5 minuta ili manje.<\/p>\n<p>No, pri\u010dekajte, u stvarnosti je situacija jo\u0161 gora. Naime, ovo su TTL-ovi od autoritativnih poslu\u017eitelja. Me\u0111utim, klijentski rezolutori (npr. usmjeriva\u010di, lokalne predmemorije) dobivaju TTL od vi\u0161ih rezolutora, a on se smanjuje svake sekunde.<\/p>\n<p>Dakle, klijent zapravo mo\u017ee koristiti svaki zapis, u prosjeku, tijekom polovice izvornih TTL-a, nakon \u010dega \u0161alje novi upit.<\/p>\n<p>Mo\u017eda se ti vrlo niski TTL-ovi odnose samo na neuobi\u010dajene upite, a ne na popularne web stranice i API-je? Pogledajmo:<\/p>\n<p><img decoding=\"async\" alt=\"Prestani koristiti smije\u0161no malo TTL za DNS\" src=\"\/wp-content\/uploads\/2019\/11\/2680f9669a90f449a593edcc84ca0dc8.jpg\" style=\"display:block;margin: 0 auto;\"><\/p>\n<p>Osa X&nbsp;predstavlja TTL, a osa Y&nbsp;popularnost upita.<\/p>\n<p>Na\u017ealost, najpopularniji upiti tako\u0111er su i najlo\u0161ije ke\u0161irani.<\/p>\n<p>Pribli\u017eno:<\/p>\n<p><img decoding=\"async\" alt=\"Prestani koristiti smije\u0161no malo TTL za DNS\" src=\"\/wp-content\/uploads\/2019\/11\/c670382b195169779743f43fd7b15827.jpg\" style=\"display:block;margin: 0 auto;\"><\/p>\n<p>Presuda: stvarno je lo\u0161e. Ve\u0107 je ranije bilo lo\u0161e, a sada je postalo jo\u0161 gore. DNS ke\u0161iranje je postalo prakti\u010dki beskorisno. Kako sve manje ljudi koristi DNS rezolver svog providera (iz razumnih razloga), pove\u0107anje latencije postaje sve primjetnije.<\/p>\n<p>DNS ke\u0161iranje je postalo korisno samo za sadr\u017eaj koji nitko ne posje\u0107uje.<\/p>\n<p>Tako\u0111er obratite pa\u017enju da softver mo\u017ee <noindex><a rel=\"nofollow\" href=\"https:\/\/00f.net\/2011\/11\/17\/how-long-does-a-dns-ttl-last\/\">na razli\u010dite na\u010dine<\/a><\/noindex> tuma\u010diti niske TTL.<\/p>\n<h1>Za\u0161to tako?<\/h1>\n<p>Za\u0161to se za DNS zapise postavlja tako mali TTL?<\/p>\n<ul>\n<li>Zastarjeli balansirnici optere\u0107enja ostali su s postavkama po defaultu.<\/li>\n<li>Postoje mitovi da DNS optere\u0107enje zavisi od TTL-a (to nije to\u010dno&nbsp;\u2014 od vremena Netscape Navigatora klijenti biraju nasumi\u010dnu IP adresu iz skupa RR-a i transparentno poku\u0161avaju drugu ako se ne mogu povezati)<\/li>\n<li>Administratori \u017eele da promjene budu primijenjene odmah, jer se tako lak\u0161e planira.<\/li>\n<li>Administrator DNS servera ili balansirnika optere\u0107enja vidi svoj zadatak u u\u010dinkovitoj implementaciji konfiguracije koju korisnici tra\u017ee, a ne u ubrzanju rada web stranica i servisa.<\/li>\n<li>Niski TTL pru\u017eaju du\u0161evni mir.<\/li>\n<li>Ljudi isprva postave niske TTL za testiranje i potom zaborave promijeniti.<\/li>\n<\/ul>\n<p>Nisam uklju\u010dio 'otklanjanje neuspjeha' jer je to sve manje relevantno. Ako je potrebno preusmjeriti korisnike na drugu mre\u017eu samo da bi se prikazala stranica s gre\u0161kom kada je sve ostalo potpuno pokvareno, mo\u017eda je prihvatljivo ka\u0161njenje od vi\u0161e od 1 minute.<\/p>\n<p>Osim toga, minutni TTL zna\u010di da ako autoritativni DNS serveri budu blokirani vi\u0161e od 1 minute, nitko vi\u0161e ne\u0107e mo\u0107i pristupiti ovisnim uslugama. I redundancija ne\u0107e pomo\u0107i ako je uzrok gre\u0161ka u konfiguraciji ili hakiranje. S druge strane, s razumnim TTL-ima mnogi klijenti \u0107e nastaviti koristiti prethodnu konfiguraciju i nikada ni\u0161ta ne primijetiti.<\/p>\n<p>Niske TTL znatno su rezultat CDN usluga i balansirnika optere\u0107enja, posebno kada kombiniraju CNAME s malim TTL i zapise s istim malim (ali neovisnim) TTL-ima:<\/p>\n<pre>$ drill raw.githubusercontent.com\nraw.githubusercontent.com.\t9\tIN\tCNAME\tgithub.map.fastly.net.\ngithub.map.fastly.net.\t20\tIN\tA\t151.101.128.133\ngithub.map.fastly.net.\t20\tIN\tA\t151.101.192.133\ngithub.map.fastly.net.\t20\tIN\tA\t151.101.0.133\ngithub.map.fastly.net.\t20\tIN\tA\t151.101.64.133<\/pre>\n<p>Svaki put kada istekne CNAME ili bilo koja od A zapisa, potrebno je poslati novi upit. Oba imaju TTL od 30 sekundi, ali se ne poklapaju. Stvarna prosje\u010dna TTL \u0107e biti 15 sekundi.<\/p>\n<p>Ali \u010dekajte! Situacija je jo\u0161 gora. Neki rezolva\u010di se vrlo lo\u0161e pona\u0161aju u takvoj situaciji s dva povezana niska TTL-a:<\/p>\n<pre>$ drill raw.githubusercontent.com @4.2.2.2\nraw.githubusercontent.com.\t1\tIN\tCNAME\tgithub.map.fastly.net.\ngithub.map.fastly.net.\t1\tIN\tA\t151.101.16.133<\/pre>\n<p>Level3 rezolva\u010d, vjerojatno, radi na BIND-u. Ako nastavite slati ovaj upit, uvijek \u0107e se vra\u0107ati TTL vrijednosti 1. U su\u0161tini, <code>raw.githubusercontent.com<\/code> nikada se ne ke\u0161ira.<\/p>\n<p>Evo jo\u0161 jednog primjera takve situacije s vrlo popularnom domenom:<\/p>\n<pre>$ drill detectportal.firefox.com @1.1.1.1\ndetectportal.firefox.com.\t25\tIN\tCNAME\tdetectportal.prod.mozaws.net.\ndetectportal.prod.mozaws.net.\t26\tIN\tCNAME\tdetectportal.firefox.com-v2.edgesuite.net.\ndetectportal.firefox.com-v2.edgesuite.net.\t10668\tIN\tCNAME\ta1089.dscd.akamai.net.\na1089.dscd.akamai.net.\t10\tIN\tA\t104.123.50.106\na1089.dscd.akamai.net.\t10\tIN\tA\t104.123.50.88<\/pre>\n<p>Ne manje od tri CNAME zapisa. Opa! Jedan ima pristojan TTL, ali to je potpuno beskorisno. U drugim CNAME-ima, po\u010detni TTL je 60 sekundi, dok za domene <code>akamai.net<\/code> maksimalni TTL iznosi 20 sekundi i nijedan od njih nije u fazi.<\/p>\n<p>\u0160to je s domenama koje neprestano upitavaju Apple ure\u0111aje?<\/p>\n<pre>$ drill 1-courier.push.apple.com @4.2.2.2\n1-courier.push.apple.com.\t1253\tIN\tCNAME\t1.courier-push-apple.com.akadns.net.\n1.courier-push-apple.com.akadns.net.\t1\tIN\tCNAME\tgb-courier-4.push-apple.com.akadns.net.\ngb-courier-4.push-apple.com.akadns.net.\t1\tIN\tA\t17.57.146.84\ngb-courier-4.push-apple.com.akadns.net.\t1\tIN\tA\t17.57.146.85<\/pre>\n<p>Ista situacija kao kod Firefoxa, i TTL ve\u0107inu vremena ostaje na 1 sekundi kada koristi Level3 rezolva\u010d.<\/p>\n<p>Dropbox?<\/p>\n<pre>$ drill client.dropbox.com @8.8.8.8\nclient.dropbox.com.\t7\tIN\tCNAME\tclient.dropbox-dns.com.\nclient.dropbox-dns.com.\t59\tIN\tA\t162.125.67.3\n\n$ drill client.dropbox.com @4.2.2.2\nclient.dropbox.com.\t1\tIN\tCNAME\tclient.dropbox-dns.com.\nclient.dropbox-dns.com.\t1\tIN\tA\t162.125.64.3<\/pre>\n<p>U zapisu <code>safebrowsing.googleapis.com<\/code> vrijednost TTL iznosi 60 sekundi, kao i kod domena Facebooka. I, opet, s gledi\u0161ta klijenta, te se vrijednosti smanjuju za polovicu.<\/p>\n<h1>\u0160to je s postavljanjem minimalnog TTL-a?<\/h1>\n<p>Koriste\u0107i ime, tip upita, TTL i izvorno spremljeni vremenski oznaku, napisao sam skriptu za simulaciju 1,5 milijuna upita prolaze\u0107i kroz ke\u0161iraju\u0107i rezolva\u010d, kako bih procijenio koli\u010dinu suvi\u0161nih upita poslanih zbog isteka zapisa iz ke\u0161a.<\/p>\n<p>47,4% upita bilo je poslanih nakon isteka postoje\u0107eg zapisa. To je neopravdano visoko.<\/p>\n<p>Kakav \u0107e biti utjecaj na ke\u0161iranje ako se postavi minimalni TTL?<\/p>\n<p><img decoding=\"async\" alt=\"Prestani koristiti smije\u0161no malo TTL za DNS\" src=\"\/wp-content\/uploads\/2019\/11\/3abd417d312450519b45f66865b23763.jpg\" style=\"display:block;margin: 0 auto;\"><\/p>\n<p>Os X su minimalne vrijednosti TTL-a. Zapisi s izvornih TTL-ova vi\u0161ih od ove vrijednosti nisu pogo\u0111eni.<\/p>\n<p>Os Y predstavlja postotak zahtjeva od klijenta koji ve\u0107 ima ke\u0161iranu anketu, \u010diji je rok istekao, i on \u0161alje novi zahtjev.<\/p>\n<p>Udjel \u201esuvi\u0161nih\u201c zahtjeva smanjuje se s 47% na 36% jednostavnom postavkom minimalnog TTL-a od 5 minuta. Kada se postavi minimalni TTL od 15 minuta, broj tih zahtjeva smanjuje se na 29%. Minimalni TTL od 1 sat smanjuje ih na 17%. Nezamjenjiva razlika!<\/p>\n<p>Kako je da ne mijenjamo ni\u0161ta na strani poslu\u017eitelja, a umjesto toga postavljamo minimalne TTL-e u klijentskim DNS ke\u0161ovima (usmjeriva\u010di, lokalni resolveri)?<\/p>\n<p><img decoding=\"async\" alt=\"Prestani koristiti smije\u0161no malo TTL za DNS\" src=\"\/wp-content\/uploads\/2019\/11\/107a2bd53797d421d65ac7260bf78dfe.jpg\" style=\"display:block;margin: 0 auto;\"><\/p>\n<p>Broj potrebnih zahtjeva smanjuje se s 47% na 34% postavljanjem minimalnog TTL-a od 5 minuta, na 25% s minimalnim od 15 minuta i na 13% s minimalnim od 1 sata. Mo\u017eda je optimalna vrijednost 40 minuta.<\/p>\n<p>Utjecaj ove minimalne promjene je ogroman.<\/p>\n<h1>Koje su posljedice?<\/h1>\n<p>Naravno, uslugu je mogu\u0107e prebaciti kod novog pru\u017eatelja oblaka, na novi poslu\u017eitelj, novu mre\u017eu, tra\u017ee\u0107i od klijenata da koriste najnovije DNS zapise. A dovoljno mali TTL poma\u017ee u glatkom i neprimjetnom prijelazu. No, s prijelazom na novu infrastrukturu, nitko ne o\u010dekuje da \u0107e klijenti pre\u0107i na nove DNS zapise unutar 1 minute, 5 minuta ili 15 minuta. Postavljanje minimalnog roka trajanja od 40 minuta umjesto 5 minuta ne\u0107e sprije\u010diti korisnike da pristupe usluzi.<\/p>\n<p>Me\u0111utim, to \u0107e zna\u010dajno smanjiti latenciju i pove\u0107ati povjerljivost i pouzdanost, izbjegavaju\u0107i suvi\u0161ne zahtjeve.<\/p>\n<p>Naravno, RFC-ovi govore da se strogo pridr\u017eavate TTL-a. Ali stvarnost je takva da je DNS sustav postao iznimno neu\u010dinkovit.<\/p>\n<p>Ako radite s autoritativnim DNS poslu\u017eiteljima, molimo vas provjerite svoje TTL-e. Trebate li zaista toliko smije\u0161no niske vrijednosti?<\/p>\n<p>Naravno, postoje dobri razlozi za postavljanje niskih TTL-a za DNS zapise. No ne za 75% DNS prometa koji se prakti\u010dki ne mijenja.<\/p>\n<p>A ako iz nekog razloga trebate koristiti niske TTL-e za DNS, tako\u0111er provjerite da li va\u0161a stranica nema uklju\u010deno ke\u0161iranje. Iz istih razloga.<\/p>\n<p>Ako imate lokalni DNS ke\u0161, poput <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/dnscrypt\/dnscrypt-proxy\">dnscrypt-proxy<\/a><\/noindex>, koji omogu\u0107ava postavljanje minimalnog TTL-a, koristite ovu funkciju. To je u redu. Ni\u0161ta lo\u0161e ne\u0107e se dogoditi. Postavite minimalni TTL otprilike izme\u0111u 40 minuta (2400 sekundi) i 1 sat. Sasvim razuman raspon.<\/p>\n<p>Izvor: <a content=\"nofollow\" rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/post\/474450\/\">habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"<p>\u041d\u0438\u0437\u043a\u0430\u044f \u0437\u0430\u0434\u0435\u0440\u0436\u043a\u0430 DNS \u2014 \u043a\u043b\u044e\u0447\u0435\u0432\u043e\u0439 \u0444\u0430\u043a\u0442\u043e\u0440 \u0434\u043b\u044f \u0431\u044b\u0441\u0442\u0440\u043e\u0439 \u0440\u0430\u0431\u043e\u0442\u044b \u0432 \u0438\u043d\u0442\u0435\u0440\u043d\u0435\u0442\u0435. \u0427\u0442\u043e\u0431\u044b \u0435\u0451 \u043c\u0438\u043d\u0438\u043c\u0438\u0437\u0438\u0440\u043e\u0432\u0430\u0442\u044c, \u0432\u0430\u0436\u043d\u043e \u0442\u0449\u0430\u0442\u0435\u043b\u044c\u043d\u043e \u043f\u043e\u0434\u043e\u0431\u0440\u0430\u0442\u044c DNS-\u0441\u0435\u0440\u0432\u0435\u0440\u044b \u0438 \u0430\u043d\u043e\u043d\u0438\u043c\u043d\u044b\u0435 \u0440\u0438\u043b\u0435\u0438. \u041d\u043e \u043f\u0435\u0440\u0432\u044b\u043c \u0434\u0435\u043b\u043e\u043c \u0441\u043b\u0435\u0434\u0443\u0435\u0442 \u0438\u0437\u0431\u0430\u0432\u0438\u0442\u044c\u0441\u044f \u043e\u0442 \u0431\u0435\u0441\u043f\u043e\u043b\u0435\u0437\u043d\u044b\u0445 \u0437\u0430\u043f\u0440\u043e\u0441\u043e\u0432. \u0418\u043c\u0435\u043d\u043d\u043e \u043f\u043e\u044d\u0442\u043e\u043c\u0443 DNS \u0438\u0437\u043d\u0430\u0447\u0430\u043b\u044c\u043d\u043e \u0441\u043e\u0437\u0434\u0430\u0432\u0430\u043b\u0441\u044f \u043a\u0430\u043a \u0441\u0438\u043b\u044c\u043d\u043e \u043a\u044d\u0448\u0438\u0440\u0443\u0435\u043c\u044b\u0439 \u043f\u0440\u043e\u0442\u043e\u043a\u043e\u043b. \u0410\u0434\u043c\u0438\u043d\u0438\u0441\u0442\u0440\u0430\u0442\u043e\u0440\u044b \u0437\u043e\u043d \u0443\u0441\u0442\u0430\u043d\u0430\u0432\u043b\u0438\u0432\u0430\u044e\u0442 \u0432\u0440\u0435\u043c\u044f \u0436\u0438\u0437\u043d\u0438 (TTL) \u0434\u043b\u044f \u043e\u0442\u0434\u0435\u043b\u044c\u043d\u044b\u0445 \u0437\u0430\u043f\u0438\u0441\u0435\u0439, \u0430 \u0440\u0435\u0437\u043e\u043b\u0432\u0435\u0440\u044b \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u0443\u044e\u0442 \u044d\u0442\u0443 \u0438\u043d\u0444\u043e\u0440\u043c\u0430\u0446\u0438\u044e \u043f\u0440\u0438 \u0445\u0440\u0430\u043d\u0435\u043d\u0438\u0438 \u0437\u0430\u043f\u0438\u0441\u0435\u0439 [&hellip;]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-52324","post","type-post","status-publish","format-standard","hentry","category-administrirovanie"],"aioseo_notices":[],"aioseo_head":"\n\t\t<!-- All in One SEO 5.0.4 - aioseo.com -->\n\t<meta name=\"description\" content=\"\u041d\u0438\u0437\u043a\u0430\u044f \u0437\u0430\u0434\u0435\u0440\u0436\u043a\u0430 DNS \u2014 \u043a\u043b\u044e\u0447\u0435\u0432\u043e\u0439 \u0444\u0430\u043a\u0442\u043e\u0440 \u0434\u043b\u044f \u0431\u044b\u0441\u0442\u0440\u043e\u0439 \u0440\u0430\u0431\u043e\u0442\u044b \u0432 \u0438\u043d\u0442\u0435\u0440\u043d\u0435\u0442\u0435.\" \/>\n\t<meta name=\"robots\" content=\"max-image-preview:large\" \/>\n\t<meta name=\"author\" content=\"Yuri Gagarin\"\/>\n\t<link rel=\"canonical\" href=\"https:\/\/prohoster.info\/hr\/blog\/administrirovanie\/hvatit-ispolzovat-smehotvorno-malyj-ttl-dlya-dns\" \/>\n\t\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.4\" \/>\n\t\t<meta property=\"og:locale\" content=\"hr_HR\" \/>\n\t\t<meta property=\"og:site_name\" content=\"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b\" \/>\n\t\t<meta property=\"og:type\" content=\"article\" \/>\n\t\t<meta property=\"og:title\" content=\"\ud83e\udd47\u0425\u0432\u0430\u0442\u0438\u0442 \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u0442\u044c \u0441\u043c\u0435\u0445\u043e\u0442\u0432\u043e\u0440\u043d\u043e \u043c\u0430\u043b\u044b\u0439 TTL \u0434\u043b\u044f DNS | ProHoster\" \/>\n\t\t<meta property=\"og:description\" content=\"\u041d\u0438\u0437\u043a\u0430\u044f \u0437\u0430\u0434\u0435\u0440\u0436\u043a\u0430 DNS \u2014 \u043a\u043b\u044e\u0447\u0435\u0432\u043e\u0439 \u0444\u0430\u043a\u0442\u043e\u0440 \u0434\u043b\u044f \u0431\u044b\u0441\u0442\u0440\u043e\u0439 \u0440\u0430\u0431\u043e\u0442\u044b \u0432 \u0438\u043d\u0442\u0435\u0440\u043d\u0435\u0442\u0435.\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/prohoster.info\/hr\/blog\/administrirovanie\/hvatit-ispolzovat-smehotvorno-malyj-ttl-dlya-dns\" \/>\n\t\t<meta property=\"og:image\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:secure_url\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:width\" content=\"350\" \/>\n\t\t<meta property=\"og:image:height\" content=\"350\" \/>\n\t\t<meta property=\"article:published_time\" content=\"2019-11-05T21:00:00+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2021-01-02T11:04:14+00:00\" \/>\n\t\t<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/prohoster\" \/>\n\t\t<meta property=\"article:author\" content=\"https:\/\/www.facebook.com\/prohoster\" \/>\n\t\t<!-- All in One SEO -->\n\n","aioseo_head_json":{"title":"\ud83e\udd47 Prestani koristiti sme\u0161no mali TTL za DNS | ProHoster","description":"Niska DNS latencija je klju\u010dni faktor za brzi rad interneta.","canonical_url":"https:\/\/prohoster.info\/hr\/blog\/administrirovanie\/hvatit-ispolzovat-smehotvorno-malyj-ttl-dlya-dns","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"hr_HR","og:site_name":"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b","og:type":"article","og:title":"\ud83e\udd47\u0425\u0432\u0430\u0442\u0438\u0442 \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u0442\u044c \u0441\u043c\u0435\u0445\u043e\u0442\u0432\u043e\u0440\u043d\u043e \u043c\u0430\u043b\u044b\u0439 TTL \u0434\u043b\u044f DNS | ProHoster","og:description":"\u041d\u0438\u0437\u043a\u0430\u044f \u0437\u0430\u0434\u0435\u0440\u0436\u043a\u0430 DNS \u2014 \u043a\u043b\u044e\u0447\u0435\u0432\u043e\u0439 \u0444\u0430\u043a\u0442\u043e\u0440 \u0434\u043b\u044f \u0431\u044b\u0441\u0442\u0440\u043e\u0439 \u0440\u0430\u0431\u043e\u0442\u044b \u0432 \u0438\u043d\u0442\u0435\u0440\u043d\u0435\u0442\u0435.","og:url":"https:\/\/prohoster.info\/hr\/blog\/administrirovanie\/hvatit-ispolzovat-smehotvorno-malyj-ttl-dlya-dns","og:image":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:secure_url":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:width":350,"og:image:height":350,"article:published_time":"2019-11-05T21:00:00+00:00","article:modified_time":"2021-01-02T11:04:14+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"52324","title":null,"description":"","keywords":"","keyphrases":null,"primary_term":null,"canonical_url":"","og_title":null,"og_description":null,"og_object_type":"default","og_image_type":"default","og_image_url":null,"og_image_width":null,"og_image_height":null,"og_image_custom_url":null,"og_image_custom_fields":null,"og_video":null,"og_custom_url":null,"og_article_section":null,"og_article_tags":null,"twitter_use_og":false,"twitter_card":"default","twitter_image_type":"default","twitter_image_url":null,"twitter_image_custom_url":null,"twitter_image_custom_fields":null,"twitter_title":null,"twitter_description":null,"schema":{"blockGraphs":[],"customGraphs":[],"default":{"data":{"Article":[],"Course":[],"Dataset":[],"FAQPage":[],"Movie":[],"Person":[],"Product":[],"ProductReview":[],"Car":[],"Recipe":[],"Service":[],"SoftwareApplication":[],"WebPage":[]},"graphName":"","isEnabled":true},"graphs":[]},"schema_type":null,"schema_type_options":null,"pillar_content":false,"robots_default":true,"robots_noindex":false,"robots_noarchive":false,"robots_nosnippet":false,"robots_nofollow":false,"robots_noimageindex":false,"robots_noodp":false,"robots_notranslate":false,"robots_max_snippet":null,"robots_max_videopreview":null,"robots_max_imagepreview":"large","priority":null,"frequency":null,"local_seo":null,"seo_analyzer_scan_date":"2026-01-24 03:14:21","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-02-28 20:45:29","updated":"2026-01-24 03:14:21","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/posts\/52324","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/comments?post=52324"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/posts\/52324\/revisions"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/media?parent=52324"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/categories?post=52324"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/hr\/wp-json\/wp\/v2\/tags?post=52324"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}