{"id":123574,"date":"2022-12-23T13:22:13","date_gmt":"2022-12-23T12:22:13","guid":{"rendered":"https:\/\/blog.wedos.cz\/?p=123574"},"modified":"2023-04-11T11:00:11","modified_gmt":"2023-04-11T09:00:11","slug":"wedos-online-a-monitorovani-webu","status":"publish","type":"post","link":"https:\/\/blog.wedos.com\/cs\/wedos-online-a-monitorovani-webu","title":{"rendered":"WEDOS OnLine a monitorov\u00e1n\u00ed webu"},"content":{"rendered":"\n

WEDOS OnLine<\/a> je na\u0161e slu\u017eba pro monitorov\u00e1n\u00ed a kontrolov\u00e1n\u00ed dom\u00e9n, web\u016f, server\u016f a dal\u0161\u00edch slu\u017eeb. Sami ji vyu\u017e\u00edv\u00e1me pro hromadnou kontrolu v\u0161ech hostingov\u00fdch slu\u017eeb na\u0161ich z\u00e1kazn\u00edk\u016f a agregovan\u00e9 v\u00fdstupy m\u016f\u017eete sledovat na status.wedos.hosting<\/a>. U\u0161et\u0159ila n\u00e1m spoustu probl\u00e9m\u016f a \u010dasu. V\u011b\u0159\u00edme, \u017ee se jedn\u00e1 o jednu z nejzaj\u00edmav\u011bj\u0161\u00edch slu\u017eeb v na\u0161\u00ed nab\u00eddce. a proto dostala tak\u00e9 pat\u0159i\u010dnou prioritu<\/a>. <\/p>\n\n\n\n

Dnes se pod\u00edv\u00e1me, jak ji m\u016f\u017eete vyu\u017e\u00edt pro kontrolu dostupnosti va\u0161eho webu, a\u0165 jej m\u00e1te kdekoliv.<\/p>\n\n\n\n\n\n\n\n

Kontrola dostupnosti p\u0159es HTTP(S) <\/h2>\n\n\n\n

Jedn\u00e1 se o z\u00e1kladn\u00ed a nejobl\u00edben\u011bj\u0161\u00ed kontrolu WEDOS OnLine. Vyu\u017e\u00edv\u00e1 j\u00ed 80,65 % aktivn\u00edch u\u017eivatel\u016f<\/strong> a m\u00e1 pod\u00edl 58,75 % na v\u0161ech kontrol\u00e1ch<\/strong>. V intervalu 1 a\u017e 45 minut m\u016f\u017eete kontrolovat konkr\u00e9tn\u00ed URL. Vytvo\u0159it si ji m\u016f\u017eete zde<\/a>.<\/p>\n\n\n

\n
\"\"<\/figure>\n<\/div>\n\n\n

Jej\u00edm hlavn\u00edm c\u00edlem je zjistit, zda-li je URL dostupn\u00e1, a jak dlouho trv\u00e1 odezva. U\u017eivatel m\u00e1 mo\u017enost nastavit si, kdy m\u00e1 b\u00fdt upozorn\u011bn na pomalou odpov\u011b\u010f anebo ukon\u010dit spojen\u00ed.<\/p>\n\n\n\n

Zat\u00edmco 2000 ms m\u016f\u017ee b\u00fdt u webov\u00e9 str\u00e1nky d\u016fvod k ozna\u010den\u00ed za pomal\u00e9, tak t\u0159eba u API pot\u0159ebujte odpov\u011b\u010f o dost rychlej\u0161\u00ed.<\/p>\n\n\n\n

\"\"<\/figure>
\n

TIP: V\u011bd\u011bli jste, \u017ee kdy\u017e ponech\u00e1te hodnotu pr\u00e1zdnou, tak rychlost odpov\u011bdi se nebude vyhodnocovat? Nebudete tak dost\u00e1vat ani varov\u00e1n\u00ed, \u017ee je web pomal\u00fd.<\/p>\n<\/div><\/div>\n\n\n\n

Nov\u011b si m\u016f\u017eete u t\u00e9to kontroly nastavit, jak\u00e9 odpov\u011bdi server (stavov\u00e9 k\u00f3dy) maj\u00ed b\u00fdt pova\u017eovan\u00e9 kontrolou za spr\u00e1vn\u00e9. Jednotliv\u00e9 k\u00f3dy m\u016f\u017eete odd\u011blit \u010d\u00e1rkou (200,301) a\/nebo pou\u017e\u00edt rozsah (300-307).<\/p>\n\n\n\n

Kontrola p\u0159itom prob\u00edh\u00e1 z v\u00edce lokalit. Nejd\u0159\u00edve od n\u00e1s z Hlubok\u00e9 nad Vltavou, a pokud je zji\u0161t\u011bna nedostupnost, tak n\u00e1sleduje ov\u011b\u0159en\u00ed z dal\u0161\u00edch lokalit. Prozat\u00edm se vyu\u017e\u00edvaly servery t\u0159et\u00edch stran, ale s t\u00edm, jak roste WEDOS Global, tak za\u010dneme vyu\u017e\u00edvat n\u00e1\u0161 vlastn\u00ed hardware po cel\u00e9m sv\u011bt\u011b.<\/p>\n\n\n\n

Pokud dojde k n\u011bjak\u00e9 chyb\u011b, tak o tom budete informov\u00e1n\u00ed e-mailem, p\u0159\u00edpadn\u011b jinou notifikac\u00ed (Mettermost, Rocket.Chat, Slack, Pushover, Webhook). Zaj\u00edmav\u00e9 vyu\u017eit\u00ed maj\u00ed Webhooky, ale o tom si pov\u00edme n\u011bkdy p\u0159\u00ed\u0161t\u011b.<\/p>\n\n\n\n

A jak\u00e9 informace n\u00e1m tato kontrola um\u00ed poskytnout (najdeme je v Historii chyb)?<\/p>\n\n\n\n

Datum\t15.12.2022 20:59:57\nStav\tpomal\u00e9\nOdezva\t2588 ms\nDetaily\t200\nIP adresa\t2a0e:acc0::c27<\/code><\/pre>\n\n\n\n
Asi nej\u010dast\u011bj\u0161\u00ed informace, kter\u00e1 informuje o tom, \u017ee test p\u0159ekro\u010dil nastavenou hodnotu „Pomal\u00e9“<\/strong>.  Zjist\u00edm kdy, jak dlouho trval po\u017eadavek, jak\u00fd byl stavov\u00fd k\u00f3d a jak\u00e1 IP adresa byla kontrolov\u00e1na.<\/p>\n\n\n\n
Tato kontrola automaticky preferuje IPv6 p\u0159es IPv4 (pokud je dostupn\u00e1). M\u016f\u017eete si v\u0161ak zalo\u017eit dv\u011b kontroly. Jednu na IPv4 a druhou na IPv6. Aktu\u00e1ln\u011b nedostupnost p\u0159es IPv6 nen\u00ed velk\u00fd probl\u00e9m, ov\u0161em pokud bude pomalej\u0161\u00ed m\u016f\u017ee to ukazovat na n\u011bjak\u00fd slo\u017eit\u011bj\u0161\u00ed probl\u00e9m.<\/p>\n\n\n\n
Datum\t12.12.2022 03:37:43\nStav\tbez odpov\u011bdi\nDetaily\tOperation timed out after 10001 milliseconds with 0 bytes received\nIP adresa\t2a02:2b88:1:4::bc\nReverz. z\u00e1znam\thc1-wd332.wedos.net<\/code><\/pre>\n\n\n\n
Toto je druh\u00fd nej\u010dast\u011bj\u0161\u00ed probl\u00e9m. Jedn\u00e1 se o chybu „bez odpov\u011bdi“<\/strong>, kdy za p\u0159edem nastaven\u00fd \u010das nedo\u0161lo k odpov\u011bdi. 10 vte\u0159in je ve WEDOS OnLine standardn\u011b nastaveno jako v\u00fdpadek (vy\u0161\u0161\u00ed hodnota nastavit nejde). Nicm\u00e9n\u011b pokud je v\u00e1\u0161 server pod velk\u00fdm n\u00e1porem, tak \u0159ad\u00ed po\u017eadavky do fronty a zahazuje je teprve kdy\u017e je fronta pln\u00e1 (vrac\u00ed se v\u011bt\u0161inou 503). <\/p>\n\n\n\n
Kontrola obsahuje i reverzn\u00ed z\u00e1znam serveru, podle kter\u00e9ho m\u016f\u017eete u n\u00e1s dohledat stav serveru na status.wedos.hosting<\/a>. Zjist\u00edte tak, zda-li se chyba aktu\u00e1ln\u011b t\u00fdk\u00e1 jen V\u00e1s anebo cel\u00e9ho serveru.<\/p>\n\n\n\n
\"\"<\/figure>\n\n\n\n
V\u0161echny chyby na status.wedos.hosting  v posledn\u00edch 24 hodin\u00e1ch se tak\u00e9 zaznamen\u00e1vaj\u00ed u n\u00e1s do RSS v XML<\/a> a JSON<\/a> form\u00e1tu.<\/p>\n\n\n\n
\n
\"\"
Historie probl\u00e9m\u016f a v\u00fdpadk\u016f v XML (RSS)
https:\/\/status.wedos.hosting\/cs\/rss\/all.rss<\/figcaption><\/figure>\n\n\n\n
\"\"
Historie probl\u00e9m\u016f a v\u00fdpadk\u016f v JSON
https:\/\/status.wedos.hosting\/cs\/json\/incidents.json<\/figcaption><\/figure>\n<\/figure>\n\n\n\n
Pokud nem\u00e1te slu\u017eby u n\u00e1s, tak informace o n\u00e1zvu serveru v\u00e1m pomohou dohledat probl\u00e9m, p\u0159\u00edpadn\u011b kdy\u017e budete komunikovat se z\u00e1kaznickou podporu, tak jim snadno sd\u011bl\u00edte, na jak\u00e9m serveru m\u00e1te slu\u017eby, bez nutnosti hledat to v administraci, co\u017e urychl\u00ed \u0159e\u0161en\u00ed probl\u00e9mu.<\/p>\n\n\n\n
Kontrolovat d\u016fv\u011bryhodnost a expirace certifik\u00e1tu<\/h3>\n\n\n\n
Tato podkrontrola je sou\u010d\u00e1st\u00ed HTTP kontroly a je voliteln\u00e1. Pokud pou\u017e\u00edv\u00e1te HTTPS tak byste j\u00ed m\u011bli m\u00edt aktivn\u00ed. Upozorn\u00ed v\u00e1s na bl\u00ed\u017e\u00edc\u00ed se expiraci certifik\u00e1tu, co\u017e se opravdu hod\u00ed. Upozorn\u00ed tak\u00e9 na p\u0159\u00edpadn\u00e9 chyby s certifik\u00e1tem. V\u011bt\u0161ina spr\u00e1vc\u016f server\u016f m\u00e1 proces prodlou\u017een\u00ed platnosti certifik\u00e1t\u016f automatizovan\u00fd (v\u010detn\u011b n\u00e1s), ale v\u017edy se m\u016f\u017ee n\u011bco pokazit. U\u017e jsme zaznamenali i probl\u00e9my p\u0159\u00edmo u certifika\u010dn\u00ed autority.<\/p>\n\n\n\n
Certifik\u00e1ty se opravdu vyplat\u00ed hl\u00eddat, proto\u017ee jakmile jsou neplatn\u00e9, tak jsou na to upozorn\u011bni u\u017eivatel\u00e9 prohl\u00ed\u017ee\u010dem, a to celkem d\u016frazn\u011b. <\/p>\n\n\n\n
Notifikace v p\u0159\u00edpad\u011b probl\u00e9mu vypad\u00e1 n\u00e1sledovn\u011b:<\/p>\n\n\n\n
N\u00e1zev: N\u00e1zev m\u00e9ho testu\nC\u00edl: https:\/\/www.dom\u00e9na.cz\/index.php\nPo\u010det varov\u00e1n\u00ed: 1\n\n1. Bl\u00ed\u017e\u00ed se expirace certifik\u00e1tu - 2020-04-29 23:44 GMT<\/code><\/pre>\n\n\n\n
\"\"<\/figure>
\n
TIP: Pokud pot\u0159ebujete upravit po\u010det dn\u00ed, kdy za\u010dnou chodit varov\u00e1n\u00ed na expiruj\u00edc\u00ed certifik\u00e1t sta\u010d\u00ed upravit polo\u017eku Varov\u00e1n\u00ed certifik\u00e1t:<\/em>. Lze nastavit 1 – 30 dn\u016f.<\/p>\n<\/div><\/div>\n\n\n\n
Kontrolovat block\/black list\u016f<\/h3>\n\n\n\n
Block listy (d\u0159\u00edve blacklisty) jsou ve\u0159ejn\u00e9 anebo priv\u00e1tn\u00ed seznamy probl\u00e9mov\u00fdch IP adres anebo dom\u00e9n, kter\u00e9 jsou podez\u0159el\u00e9 z neleg\u00e1ln\u00edho anebo \u0161kodliv\u00e9ho chov\u00e1n\u00ed. Nej\u010dast\u011bji se jedn\u00e1 o spamov\u00e1n\u00ed, DDoS \u00fatoky, phishing a nebo dal\u0161\u00ed formy kybernetick\u00e9 kriminality.<\/p>\n\n\n\n
Tyto seznamy pak mohou vyu\u017e\u00edvat spr\u00e1vci server\u016f, poskytovatel\u00e9 slu\u017eeb anebo internetov\u00e9ho p\u0159ipojen\u00ed a omezovat z nich provoz. Jak provoz omez\u00ed je \u010dist\u011b na nich. Mohou omezit jen ur\u010dit\u00e9 porty anebo v\u0161echny po\u017eadavky z nich zcela zak\u00e1zat (zahazovat.) Nejedn\u00e1 se tedy jen o p\u0159\u00edstup na web, ale t\u0159eba i automatick\u00e9 zahazov\u00e1n\u00ed p\u0159ijat\u00fdch e-mailov\u00fdch zpr\u00e1v.<\/p>\n\n\n\n
Pokud se IP adresa dostane na ve\u0159ejn\u00fd blacklist, m\u016f\u017ee b\u00fdt obt\u00ed\u017en\u00e9 ji odstranit. N\u011bkter\u00e9 blacklisty poskytuj\u00ed mo\u017enost nahl\u00e1sit chybu anebo se odvolat proti p\u0159id\u00e1n\u00ed (pou\u017e\u00edv\u00e1 se to, pokud provozovatel nap\u00ed\u0161e, \u017ee probl\u00e9m vy\u0159e\u0161il). Nicm\u00e9n\u011b to m\u016f\u017ee trvat dny i t\u00fddny. Spr\u00e1vce blacklistu ji tam m\u016f\u017ee ponechat schv\u00e1ln\u011b, aby se ujistil, \u017ee u\u017e nedoch\u00e1z\u00ed k dal\u0161\u00ed neleg\u00e1ln\u00ed \u010dinnosti. <\/p>\n\n\n\n
Je t\u0159eba si uv\u011bdomit, \u017ee z\u00e1kladem je v\u011bd\u011bt, \u017ee na n\u011bjak\u00e9m ve\u0159ejn\u00e9m blacklistu v\u016fbec jste, proto\u017ee pak teprve m\u016f\u017eete jednat. Va\u0161e e-maily odeslan\u00e9 ze serveru mohou padat dlouh\u00e9 m\u011bs\u00edce do spamu, jen kv\u016fli tomu, \u017ee n\u011bkde jste na blacklistu.<\/p>\n\n\n\n
WEDOS OnLine nab\u00edz\u00ed kontrolu dom\u00e9ny a IP adresy serveru, zdali se nenach\u00e1z\u00ed na blacklistech DNSBL (DNS Blacklist) a URIBL (Uniform Resource Identifier Blacklist). <\/p>\n\n\n\n
Pokud je IP adresa anebo dom\u00e9na nalezena na n\u011bkter\u00e9m blacklistu, dostanete o tom n\u00e1sleduj\u00edc\u00ed informaci:<\/p>\n\n\n\n
N\u00e1zev: Moje kontrola dom\u00e9ny domena.tld\nC\u00edl: https:\/\/dom\u00e9na.cz\/\nPo\u010det varov\u00e1n\u00ed: 1\n\n1. IP na blacklistu - AAA.BBB.C.DDD - cbl.abuseat.org - Blocked - see http:\/\/www.abuseat.org\/lookup.cgi?ip=AAA.BBB.C.DDD\nAAA.BBB.C.DDD - zen.spamhaus.org - https:\/\/www.spamhaus.org\/query\/ip\/AAA.BBB.C.DDD<\/code><\/pre>\n\n\n\n
\"\"<\/figure>
\n
TIP: Do varov\u00e1n\u00ed se sna\u017e\u00edme d\u00e1vat i odkaz na z\u00e1znam na konkr\u00e9tn\u00edm blacklistu, kde v\u011bt\u0161inou najdete i mo\u017enost \u0159e\u0161it probl\u00e9m. Ov\u0161em n\u011bkdy je nutn\u00e9, aby o odstran\u011bn\u00ed po\u017e\u00e1dal p\u0159\u00edmo spr\u00e1vce serveru (hosting).<\/p>\n<\/div><\/div>\n\n\n\n
DNS servery<\/h2>\n\n\n\n
Kontrola stavu a zdrav\u00ed DNS server\u016f je t\u0159et\u00ed nejobl\u00edben\u011bj\u0161\u00ed kontrolou aktivn\u00edch u\u017eivatel\u016f WEDOS OnLine. Pou\u017e\u00edv\u00e1 ji v\u00edce jak 6 % u\u017eivatel\u016f<\/strong> a pod\u00edl\u00ed se na 7,42% aktivn\u00edch kontrol<\/strong>. Z\u0159\u00eddit si ji m\u016f\u017eete zde<\/a>.<\/p>\n\n\n
\n
\"\"<\/figure>\n<\/div>\n\n\n
Po zad\u00e1n\u00ed dom\u00e9ny jsou ka\u017ed\u00fdch 1 – 45 minut kontrolov\u00e1ny DNS servery, kter\u00e9 jsou nastaven\u00e9 u dom\u00e9ny a kter\u00e9 rozhoduj\u00ed, kam dom\u00e9na sm\u011b\u0159uje, a to nejen obsah, ale i nap\u0159\u00edklad e-maily. <\/p>\n\n\n\n
\"\"<\/figure>
\n
TIP: Pokud si za\u0161krtnete upozor\u0148ovat na zm\u011bny DNS server\u016f, tak budete informov\u00e1n\u00ed i o zm\u011bn\u011b DNS. To v\u00e1s upozorn\u00ed na mo\u017enou kr\u00e1de\u017e dom\u00e9ny (nasm\u011brov\u00e1n\u00ed dom\u00e9ny jinam). Nov\u00fd DNS server tak\u00e9 nemus\u00ed m\u00edt v\u0161echny NS z\u00e1znamy spr\u00e1vn\u011b.<\/p>\n<\/div><\/div>\n\n\n\n
DNS servery jsou kritickou sou\u010d\u00e1st\u00ed internetu, a proto ka\u017ed\u00fd hosting vyu\u017e\u00edv\u00e1 minim\u00e1ln\u011b dva, pro p\u0159\u00edpad selh\u00e1n\u00ed. U WEDOS pou\u017e\u00edv\u00e1me rad\u0161i 4, ka\u017ed\u00fd v jin\u00e9 lokalit\u011b a kombinujeme technologie.<\/p>\n\n\n\n
Tato kontrola testuje nejen dostupnost DNS server\u016f ale tak\u00e9 jejich odezvu. Op\u011bt se vyu\u017e\u00edv\u00e1 nejd\u0159\u00edve kontrola u n\u00e1s ve WEDOS DC1 v Hlubok\u00e9 nad Vltavou a v p\u0159\u00edpad\u011b nedostupnosti ov\u011b\u0159en\u00ed ze zahrani\u010d\u00ed.<\/p>\n\n\n
\n
\"\"<\/figure>\n<\/div>\n\n\n
Jak vid\u00edte, nav\u00edc se testuje i odezva jednotliv\u00fdch DNS. Problematika DNS je slo\u017eit\u011bj\u0161\u00ed, ale zjednodu\u0161en\u011b alespo\u0148 pro nov\u00e9 n\u00e1v\u0161t\u011bvn\u00edky (prvn\u00ed p\u0159\u00edstup) pot\u0159ebujete odezvu udr\u017eet co nejni\u017e\u0161\u00ed, proto\u017ee se p\u0159i\u010d\u00edt\u00e1 k dob\u011b pot\u0159ebn\u00e9 pro na\u010dten\u00ed str\u00e1nek, respektive \u010dehokoliv, o co prohl\u00ed\u017ee\u010d n\u00e1v\u0161t\u011bvn\u00edka po\u017e\u00e1d\u00e1.<\/p>\n\n\n\n
Na\u0161t\u011bst\u00ed si v\u0161e prohl\u00ed\u017ee\u010d, v\u00e1\u0161 opera\u010dn\u00ed syst\u00e9m, router, p\u0159\u00edpadn\u011b poskytovatel p\u0159ipojen\u00ed ukl\u00e1d\u00e1, tak\u017ee opakovan\u00e9 dotazy u\u017e jdou z cache. Nicm\u00e9n\u011b ten prvn\u00ed, kter\u00fd je hodn\u011b d\u016fle\u017eit\u00fd, m\u016f\u017ee trvat. Pr\u00e1v\u011b tohle \u0159e\u0161\u00ed AnycastDNS, kde n\u00e1v\u0161t\u011bvn\u00edkovi odpov\u00edd\u00e1 jemu  nejbli\u017e\u0161\u00ed DNS, co\u017e je jedna z funkc\u00ed na\u0161\u00ed nov\u00e9 decentralizovan\u00e9 s\u00edt\u011b WEDOS Global<\/a>.<\/p>\n\n\n\n
A jak vypadaj\u00ed varov\u00e1n\u00ed?<\/h4>\n\n\n\n
N\u00e1zev: XXXXX.cz\nC\u00edl: XXXXX.cz\nPo\u010det varov\u00e1n\u00ed: 1\n\n1. Chybn\u00e1 odpov\u011b\u010f DNS serveru\n  - ns1.XXXXX.cz\/AA.B.CCC.DDD: Response timeout\n  - ns1.XXXXX.cz\/AAAA:BBBB:CCC::DDD: Response timeout<\/code><\/pre>\n\n\n\n
Jeden z DNS server\u016f m\u00e1 v\u00fdpadek. Kontrola nahl\u00e1s\u00ed Response timeout<\/em>. Jeho roli p\u0159ebere z\u00e1lo\u017en\u00ed, tak\u017ee to v\u011bt\u0161inou nem\u00e1 dopad na slu\u017eby. Ale chce to hl\u00eddat, zvl\u00e1\u0161t\u011b pokud jich vypad\u00e1v\u00e1 v\u00edce a na del\u0161\u00ed dobu.<\/p>\n\n\n\n
N\u00e1zev: XXXXXXXXXX.cz\nC\u00edl: XXXXXXXXXX.cz\nPo\u010det varov\u00e1n\u00ed: 1\n\n1. S\u00e9riov\u00e1 \u010d\u00edsla DNS z\u00f3n se li\u0161\u00ed\n  - ns2.XXXXXXXXXX.cz\/AA.BBB.CCC.DDD: 2022112001\n  - ns2.XXXXXXXXXX.cz\/AAAA:BBBB:C:DD::EE:FFFF: 2022112001\n  - YYYYYY.XXXXXXXXXX.cz\/AAA.BBB.CCC.D: 2022112101\n  - YYYYYY.XXXXXXXXXX.cz\/AAAA:BBBB:CC::D: 2022112101\n<\/code><\/pre>\n\n\n\n
Chyba S\u00e9riov\u00e1 \u010d\u00edsla DNS z\u00f3n<\/em> se li\u0161\u00ed se m\u016f\u017ee objevit, pokud jsou aktualizov\u00e1ny z\u00e1znamy na jednom DNS serveru, ale nejsou p\u0159en\u00e1\u0161eny na ostatn\u00ed servery, kter\u00e9 obsahuj\u00ed kopii t\u00e9to z\u00f3ny. V takov\u00e9m p\u0159\u00edpad\u011b mohou n\u011bkter\u00e9 DNS servery st\u00e1le pou\u017e\u00edvat star\u00e9 verze z\u00e1znam\u016f, zat\u00edmco jin\u00e9 pou\u017e\u00edvaj\u00ed nov\u00e9 verze. To m\u016f\u017ee zp\u016fsobit probl\u00e9my s p\u0159\u00edstupem k dan\u00e9 dom\u00e9n\u011b nebo slu\u017eb\u00e1m, kter\u00e9 jsou spojen\u00e9 s touto dom\u00e9nou.<\/p>\n\n\n\n
Jak vypadaj\u00ed v\u00fdpadky?<\/h4>\n\n\n\n
V\u00fdpadky jsou u DNS pom\u011brn\u011b vz\u00e1cn\u00e9. DNS je robustn\u00ed syst\u00e9m a v\u011bt\u0161ina hosting\u016f jej m\u00e1 pom\u011brn\u011b odoln\u00fd. Pokud dojde k probl\u00e9m\u016fm, tak je to v\u011bt\u0161inou v d\u016fsledku \u00famyslu (nepoveden\u00e1 \u00fadr\u017eba, DDoS \u00fatok) anebo souhrn v\u00edce ud\u00e1losti. T\u0159eba tento probl\u00e9m m\u011bla jedna konkuren\u010dn\u00ed hostingov\u00e1 spole\u010dnost za\u010d\u00e1tkem prosince.<\/p>\n\n\n\n
N\u00e1zev: [Konkurence] XXXXX.cz\nC\u00edl: XXXXXX.cz\nStav: nedostupn\u00e9\nDetail: \n - ns1.XXXXXX.cz\/AAA.BB.CCC.DDD: Response timeout\n - ns2.XXXXXX.cz\/AAA.BB.CCC.DDD: Response timeout\n - ns3.XXXXXX.cz\/AAA.BBB.CC.DDD: Socker error 203\nPo\u010det chyb: 2\nProbl\u00e9m od: 2022-12-07 00:00:53 CET\nD\u00e9lka probl\u00e9mu: 2m 16s<\/code><\/pre>\n\n\n\n
Chyba „Socket error 203“ m\u016f\u017ee b\u00fdt zp\u016fsobena probl\u00e9my se s\u00ed\u0165ov\u00fdm p\u0159ipojen\u00edm nebo s konfigurac\u00ed DNS server\u016f.<\/p>\n\n\n\n
Z\u00e1v\u011br<\/h2>\n\n\n\n
Tohle je jen mal\u00e1 uk\u00e1zka, co v\u0161echno WEDOS OnLine um\u00ed a m\u016f\u017eete jej za\u010d\u00edt pou\u017e\u00edvat hned te\u010f a zdarma <\/a>\ud83d\ude42<\/p>\n\n\n\n
Zam\u011b\u0159ili jsme se \u010dist\u011b na kontrolu dostupnosti webu a DNS, co\u017e je pro b\u011b\u017en\u00fd web z\u00e1klad. Pokud pou\u017e\u00edv\u00e1te e-maily, tak by to cht\u011blo i kontrolu pat\u0159i\u010dn\u00fdch NS z\u00e1znam\u016f a protokol\u016f, pokud DNSSEC, tak i ten, ale to u\u017e by tento \u010dl\u00e1nek byl pomalu men\u0161\u00ed kn\u00ed\u017eka \ud83d\ude42<\/p>\n","protected":false},"excerpt":{"rendered":"
WEDOS OnLine je na\u0161e slu\u017eba pro monitorov\u00e1n\u00ed a kontrolov\u00e1n\u00ed dom\u00e9n, web\u016f, server\u016f a dal\u0161\u00edch slu\u017eeb. Sami ji vyu\u017e\u00edv\u00e1me pro hromadnou kontrolu v\u0161ech hostingov\u00fdch slu\u017eeb na\u0161ich z\u00e1kazn\u00edk\u016f a agregovan\u00e9 v\u00fdstupy m\u016f\u017eete sledovat na status.wedos.hosting. U\u0161et\u0159ila n\u00e1m spoustu probl\u00e9m\u016f a \u010dasu. V\u011b\u0159\u00edme, \u017ee se jedn\u00e1 o jednu z nejzaj\u00edmav\u011bj\u0161\u00edch slu\u017eeb v na\u0161\u00ed nab\u00eddce. a proto dostala tak\u00e9 … <\/p>\n
Pokra\u010dovat ve \u010dten\u00ed „WEDOS OnLine a monitorov\u00e1n\u00ed webu“<\/span><\/a><\/p>\n","protected":false},"author":9,"featured_media":121379,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[16],"tags":[156],"class_list":["post-123574","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-sluzby","tag-wedos-online"],"_links":{"self":[{"href":"https:\/\/blog.wedos.com\/cs\/wp-json\/wp\/v2\/posts\/123574","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.wedos.com\/cs\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.wedos.com\/cs\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.wedos.com\/cs\/wp-json\/wp\/v2\/users\/9"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.wedos.com\/cs\/wp-json\/wp\/v2\/comments?post=123574"}],"version-history":[{"count":10,"href":"https:\/\/blog.wedos.com\/cs\/wp-json\/wp\/v2\/posts\/123574\/revisions"}],"predecessor-version":[{"id":133503,"href":"https:\/\/blog.wedos.com\/cs\/wp-json\/wp\/v2\/posts\/123574\/revisions\/133503"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/blog.wedos.com\/cs\/wp-json\/wp\/v2\/media\/121379"}],"wp:attachment":[{"href":"https:\/\/blog.wedos.com\/cs\/wp-json\/wp\/v2\/media?parent=123574"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.wedos.com\/cs\/wp-json\/wp\/v2\/categories?post=123574"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.wedos.com\/cs\/wp-json\/wp\/v2\/tags?post=123574"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}