{"id":2836,"date":"2026-10-10T10:00:00","date_gmt":"2026-10-10T07:00:00","guid":{"rendered":"https:\/\/narhost.com\/blog\/?p=2836"},"modified":"2026-09-26T23:22:20","modified_gmt":"2026-09-26T20:22:20","slug":"hosting-firmasi-kapanirsa","status":"publish","type":"post","link":"https:\/\/narhost.com\/blog\/hosting-firmasi-kapanirsa\/","title":{"rendered":"Hosting Firmas\u0131 Kapan\u0131rsa Sitenize ve Alan Ad\u0131n\u0131za Ne Olur"},"content":{"rendered":"<div id=\"ai-ozet\" class=\"ai-box\">\n<p class=\"ai-box-title\">K\u0131saca \u00f6zet<\/p>\n<ul>\n<li>Hosting firmas\u0131 kapan\u0131rsa siteniz, veritaban\u0131n\u0131z ve e-postalar\u0131n\u0131z eri\u015filemez h\u00e2le gelir; elinizde g\u00fcncel bir tam yedek ve alan ad\u0131n\u0131z\u0131n y\u00f6netimi varsa site ba\u015fka bir sunucuda ayn\u0131 g\u00fcn yeniden a\u00e7\u0131labilir.<\/li>\n<li>As\u0131l kay\u0131p riski sunucuda de\u011fil alan ad\u0131ndad\u0131r: alan ad\u0131 sizin ad\u0131n\u0131za kay\u0131tl\u0131 de\u011filse ve y\u00f6netim paneline eri\u015fiminiz yoksa DNS kay\u0131tlar\u0131n\u0131 yeni sunucuya \u00e7eviremezsiniz.<\/li>\n<li>.com, .net gibi genel uzant\u0131larda ICANN akrediteli kay\u0131t firmalar\u0131 kay\u0131t verisini ba\u011f\u0131ms\u0131z bir emanet kurulu\u015funa yat\u0131rmak zorundad\u0131r; kay\u0131t firmas\u0131 kapan\u0131rsa alan ad\u0131 kaybolmaz, ba\u015fka bir firmaya aktar\u0131l\u0131r.<\/li>\n<li>Firma kapanmas\u0131 tek senaryo de\u011fildir; hesab\u0131n ask\u0131ya al\u0131nmas\u0131, ka\u00e7\u0131r\u0131lan \u00f6deme ya da k\u00f6t\u00fcye kullan\u0131m \u015fik\u00e2yeti de siteyi ayn\u0131 \u015fekilde kapat\u0131r.<\/li>\n<li>\u00d6nlem d\u00f6rt par\u00e7al\u0131d\u0131r: sizin ad\u0131n\u0131za kay\u0131tl\u0131 alan ad\u0131, sa\u011flay\u0131c\u0131 d\u0131\u015f\u0131nda saklanan tam yedek, DNS&#8217;e ba\u011f\u0131ms\u0131z eri\u015fim ve ba\u015fka sunucuya ta\u015f\u0131nabilen standart teknoloji.<\/li>\n<li>Yede\u011fi yaln\u0131z sa\u011flay\u0131c\u0131n\u0131n sunucusunda duran bir site, sa\u011flay\u0131c\u0131yla birlikte kaybolur; yede\u011fin bir kopyas\u0131 sizin bilgisayar\u0131n\u0131zda ya da ayr\u0131 bir depolamada durmal\u0131d\u0131r.<\/li>\n<\/ul>\n<\/div>\n<p>Bir sabah siteniz a\u00e7\u0131lm\u0131yor, destek hatt\u0131 cevap vermiyor ve sa\u011flay\u0131c\u0131n\u0131n kendi sitesi de kapal\u0131. Hosting firmas\u0131 kapan\u0131rsa ne olaca\u011f\u0131n\u0131 \u00e7o\u011fu i\u015fletme bu anda d\u00fc\u015f\u00fcnmeye ba\u015flar; oysa sorunun cevab\u0131 aylar \u00f6nce verilmi\u015f kararlarda sakl\u0131d\u0131r. Alan ad\u0131 kimin ad\u0131na kay\u0131tl\u0131, son yedek nerede, DNS paneline kim girebiliyor. Bu \u00fc\u00e7 sorunun cevab\u0131 haz\u0131rsa kesinti birka\u00e7 saatlik bir ta\u015f\u0131ma i\u015fidir. Haz\u0131r de\u011filse site, e-posta ar\u015fivi ve bazen alan ad\u0131n\u0131n kendisi uzun s\u00fcre geri al\u0131namayabilir.<\/p>\n<h2>Hosting Firmas\u0131 Kapan\u0131rsa \u0130lk G\u00fcn Ne Olur<\/h2>\n<p>Bar\u0131nd\u0131rma hizmeti durdu\u011funda ilk etkilenen \u015fey sunucudaki her \u015feydir. Web sitesinin dosyalar\u0131, veritaban\u0131, e-posta kutular\u0131 ve sunucuda duran yedekler ayn\u0131 donan\u0131mdad\u0131r. Sunucu kapand\u0131\u011f\u0131nda ziyaret\u00e7i ba\u011flant\u0131 hatas\u0131 g\u00f6r\u00fcr, gelen e-postalar bir s\u00fcre kuyrukta bekleyip g\u00f6ndericiye geri d\u00f6ner, form ve sipari\u015f kay\u0131tlar\u0131 durur.<\/p>\n<p>Alan ad\u0131 ise ayr\u0131 bir hizmettir. Hosting firmas\u0131 kapan\u0131rsa alan ad\u0131n\u0131z kendili\u011finden silinmez; yaln\u0131z h\u00e2l\u00e2 kapanan sunucunun IP adresini g\u00f6sterir. Yeni bir sunucu a\u00e7\u0131p DNS kay\u0131tlar\u0131n\u0131 oraya \u00e7evirdi\u011finiz anda site yeniden yay\u0131na girer. Bunun \u015fart\u0131 iki \u015feydir: alan ad\u0131n\u0131n y\u00f6netimine eri\u015febilmek ve yeni sunucuya y\u00fckleyecek g\u00fcncel bir yede\u011fe sahip olmak.<\/p>\n<div class=\"highlight-box\">\n<p class=\"label\">Bilgi<\/p>\n<p>Hosting ve alan ad\u0131 ayn\u0131 firmadan al\u0131nm\u0131\u015f olabilir, ama teknik olarak iki ayr\u0131 kay\u0131tt\u0131r. Alan ad\u0131 bir kay\u0131t firmas\u0131 \u00fczerinden kay\u0131t otoritesinde durur; hosting ise bir sunucudaki alan ve kaynakt\u0131r. Kapanma riskini tartarken bu ikisini ayr\u0131 ayr\u0131 d\u00fc\u015f\u00fcnmek gerekir.<\/p>\n<\/div>\n<h2>Tek Risk Firma Kapanmas\u0131 De\u011fil<\/h2>\n<p>Pratikte siteyi bir gecede kapatan olaylar\u0131n \u00e7o\u011fu firma iflas\u0131 de\u011fildir. Kredi kart\u0131n\u0131n s\u00fcresi dolar ve yenileme \u00f6demesi ge\u00e7mez, hesap ask\u0131ya al\u0131n\u0131r. Sitedeki eski bir eklentiden s\u0131zan zararl\u0131 kod toplu e-posta g\u00f6nderir, hesap k\u00f6t\u00fcye kullan\u0131m \u015fik\u00e2yetiyle durdurulur. Tek ki\u015finin bildi\u011fi panel \u015fifresi o ki\u015fiyle birlikte gider. A\u015fa\u011f\u0131daki tablo bu senaryolar\u0131 ve her birinin kar\u015f\u0131l\u0131\u011f\u0131n\u0131 yan yana koyuyor.<\/p>\n<table>\n<thead>\n<tr>\n<th>Senaryo<\/th>\n<th>Siteye etkisi<\/th>\n<th>Kurtaran haz\u0131rl\u0131k<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Hosting firmas\u0131 kapan\u0131rsa<\/td>\n<td>Sunucudaki dosya, veritaban\u0131 ve e-posta eri\u015filemez<\/td>\n<td>D\u0131\u015far\u0131da saklanan tam yedek ve alan ad\u0131 y\u00f6netimi<\/td>\n<\/tr>\n<tr>\n<td>Hesap \u00f6deme nedeniyle ask\u0131ya al\u0131n\u0131rsa<\/td>\n<td>Site ve e-posta durur, veri genelde bir s\u00fcre korunur<\/td>\n<td>Yenileme tarihlerini takip etmek, g\u00fcncel \u00f6deme bilgisi<\/td>\n<\/tr>\n<tr>\n<td>K\u00f6t\u00fcye kullan\u0131m \u015fik\u00e2yetiyle durdurulursa<\/td>\n<td>Temizlik yap\u0131lana kadar hesap kapal\u0131 kal\u0131r<\/td>\n<td>G\u00fcncel yaz\u0131l\u0131m, temiz yedekten geri d\u00f6n\u00fc\u015f imk\u00e2n\u0131<\/td>\n<\/tr>\n<tr>\n<td>Panel \u015fifresini bilen ki\u015fi ayr\u0131l\u0131rsa<\/td>\n<td>Alan ad\u0131 ve hosting y\u00f6netilemez h\u00e2le gelir<\/td>\n<td>Hesaplar\u0131n \u015firket ad\u0131na a\u00e7\u0131lmas\u0131, yetkili ki\u015fi tan\u0131m\u0131<\/td>\n<\/tr>\n<tr>\n<td>Kay\u0131t firmas\u0131 kapan\u0131rsa<\/td>\n<td>Alan ad\u0131 ba\u015fka bir akrediteli firmaya aktar\u0131l\u0131r<\/td>\n<td>WHOIS bilgilerinin do\u011fru ve size ait olmas\u0131<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h2>Alan Ad\u0131 Neden Hosting&#8217;den Ba\u011f\u0131ms\u0131z D\u00fc\u015f\u00fcn\u00fclmeli<\/h2>\n<p>Siteyi yeniden a\u00e7man\u0131n anahtar\u0131 alan ad\u0131d\u0131r. Ziyaret\u00e7iler, arama motorlar\u0131 ve e-posta g\u00f6nderenler sizi alan ad\u0131n\u0131zla bulur; sunucu de\u011fi\u015febilir, alan ad\u0131 de\u011fi\u015fmemelidir. Genel uzant\u0131larda (.com, .net, .org) ICANN akrediteli kay\u0131t firmalar\u0131, 2013 tarihli kay\u0131t firmas\u0131 akreditasyon s\u00f6zle\u015fmesinin 3.6 maddesi gere\u011fi kay\u0131t verilerini ba\u011f\u0131ms\u0131z bir emanet kurulu\u015funa d\u00fczenli olarak yat\u0131r\u0131r. <a href=\"https:\/\/www.icann.org\/en\/contracted-parties\/accredited-registrars\/services\/registrar-data-escrow-program\" title=\"ICANN Registrar Data Escrow program\u0131 \u2014 resm\u00ee sayfa\" target=\"_blank\" rel=\"noopener\">ICANN&#8217;in kay\u0131t verisi emanet program\u0131<\/a> bu y\u00fczden vard\u0131r: kay\u0131t firmas\u0131 kapan\u0131rsa alan adlar\u0131 kay\u0131t sahiplerinin bilgileriyle ba\u015fka bir firmaya aktar\u0131labilir.<\/p>\n<p>Bu koruman\u0131n i\u015fe yaramas\u0131 i\u00e7in kay\u0131ttaki sahip bilgisinin size ait olmas\u0131 gerekir. Alan ad\u0131 ajans\u0131n, eski bir \u00e7al\u0131\u015fan\u0131n ya da sa\u011flay\u0131c\u0131n\u0131n ad\u0131na g\u00f6r\u00fcn\u00fcyorsa aktar\u0131m sonras\u0131nda hak sahibi oldu\u011funuzu kan\u0131tlamak zorla\u015f\u0131r. Yenileme uyar\u0131lar\u0131n\u0131n geldi\u011fi e-posta adresinin de aktif ve \u015firkete ait olmas\u0131 \u015fartt\u0131r.<\/p>\n<div class=\"warn-box\">\n<p class=\"label\">Dikkat<\/p>\n<p>Alan ad\u0131n\u0131n e-postalar\u0131 da ayn\u0131 alan ad\u0131 \u00fczerinde \u00e7al\u0131\u015f\u0131yorsa (info@firmaniz.com gibi) ve hosting kapand\u0131ysa, kay\u0131t firmas\u0131n\u0131n g\u00f6nderdi\u011fi do\u011frulama ve yenileme e-postalar\u0131 size ula\u015fmaz. Alan ad\u0131 hesab\u0131nda ileti\u015fim adresi olarak ba\u015fka bir alan ad\u0131na ba\u011fl\u0131 ikinci bir adres tan\u0131mlay\u0131n.<\/p>\n<\/div>\n<h2>Yedek Sa\u011flay\u0131c\u0131n\u0131n Sunucusunda Durursa Yedek Say\u0131lmaz<\/h2>\n<p>\u00c7o\u011fu hosting paketinde otomatik yedek al\u0131n\u0131r ve bu yedekler sa\u011flay\u0131c\u0131n\u0131n altyap\u0131s\u0131nda tutulur. G\u00fcnl\u00fck ar\u0131zalar i\u00e7in bu yeterlidir: silinen bir dosya, bozulan bir g\u00fcncelleme ya da hacklenen bir sitede geri d\u00f6n\u00fc\u015f sa\u011flar. Hosting firmas\u0131 kapan\u0131rsa ise bu yedekler de eri\u015filemez olur. Kapanma senaryosunda i\u015fe yarayan tek yedek, sizin elinizde duran kopyad\u0131r.<\/p>\n<p>Tam hesap yede\u011fi dosyalar\u0131, veritabanlar\u0131n\u0131, e-posta kutular\u0131n\u0131 ve DNS b\u00f6lgesini tek ar\u015fivde toplar. Bu ar\u015fivi paneli \u00fczerinden indirmenin yolu <a href=\"https:\/\/narhost.com\/destek\/yedek-dosyasi-nasil-indirilir\/\" title=\"Yedek Dosyas\u0131 Nas\u0131l \u0130ndirilir \u2014 Narhost Destek Merkezi\">yedek dosyas\u0131 nas\u0131l indirilir<\/a> kart\u0131nda ad\u0131m ad\u0131m anlat\u0131l\u0131yor. Ne s\u0131kl\u0131kla indirilece\u011fi ise sitenizin ne kadar s\u0131k de\u011fi\u015fti\u011fine ba\u011fl\u0131d\u0131r; bu karar\u0131 veren \u00f6l\u00e7\u00fctler <a href=\"https:\/\/narhost.com\/blog\/ne-siklikla-yedek-almali\/\" title=\"Ne S\u0131kl\u0131kla Yedek Almal\u0131 \u2014 Narhost Blog\">ne s\u0131kl\u0131kla yedek almal\u0131<\/a> yaz\u0131s\u0131nda tabloyla duruyor. Kurumsal bir tan\u0131t\u0131m sitesi i\u00e7in ayda bir, sipari\u015f alan bir ma\u011faza i\u00e7in her hafta indirilen kopya makul bir ba\u015flang\u0131\u00e7t\u0131r.<\/p>\n<div class=\"senaryo-block\">\n<p class=\"label\">\u00d6rnek senaryo<\/p>\n<p>Yedek par\u00e7a satan k\u00fc\u00e7\u00fck bir i\u015fletmenin sitesi, \u00f6demesi ka\u00e7\u0131r\u0131lan hosting hesab\u0131 ask\u0131ya al\u0131n\u0131nca \u00fc\u00e7 g\u00fcn kapal\u0131 kald\u0131. Hesab\u0131 a\u00e7t\u0131rmak i\u00e7in eski sa\u011flay\u0131c\u0131ya ula\u015f\u0131lamad\u0131. \u0130\u015fletmenin muhasebecisi, her ay\u0131n ilk i\u015f g\u00fcn\u00fc indirdi\u011fi tam yede\u011fi harici diskte tutuyordu. Alan ad\u0131 \u015firket ad\u0131na kay\u0131tl\u0131yd\u0131 ve panel \u015fifresi iki ki\u015fide vard\u0131. Yeni bir hosting hesab\u0131 a\u00e7\u0131ld\u0131, yedek geri y\u00fcklendi, DNS kay\u0131tlar\u0131 \u00e7evrildi ve site ayn\u0131 ak\u015fam yay\u0131ndayd\u0131. Kaybedilen veri, son yedekten sonra gelen d\u00f6rt sipari\u015fti; bunlar da e-posta bildirimlerinden elle girildi.<\/p>\n<\/div>\n<h2>DNS Eri\u015fimi ve Ad Sunucular\u0131 Kimin Elinde<\/h2>\n<p>Alan ad\u0131n\u0131z hangi ad sunucular\u0131n\u0131 g\u00f6steriyorsa DNS kay\u0131tlar\u0131n\u0131z oradad\u0131r. Bir\u00e7ok i\u015fletmede ad sunucusu hosting firmas\u0131n\u0131n sunucular\u0131d\u0131r; bu en pratik kurgu olsa da hosting kapand\u0131\u011f\u0131nda DNS b\u00f6lgesi de kapan\u0131r. O durumda ad sunucusunu yeni sa\u011flay\u0131c\u0131ya \u00e7evirmeniz gerekir ve bunu yaln\u0131z alan ad\u0131n\u0131n y\u00f6netim paneline girebilen ki\u015fi yapabilir.<\/p>\n<p>Haz\u0131rl\u0131k basittir: alan ad\u0131 panelinin kullan\u0131c\u0131 ad\u0131 ve \u015fifresi \u015firketin \u015fifre y\u00f6neticisinde durmal\u0131, iki ad\u0131ml\u0131 do\u011frulama kodu tek bir ki\u015finin telefonuna ba\u011fl\u0131 kalmamal\u0131d\u0131r. DNS b\u00f6lgenizin g\u00fcncel bir kopyas\u0131n\u0131 (A, MX, TXT kay\u0131tlar\u0131) bir belgede tutmak, yeni sunucuda e-postay\u0131 kurarken SPF ve DKIM kay\u0131tlar\u0131n\u0131 yeniden yazmay\u0131 h\u0131zland\u0131r\u0131r.<\/p>\n<h2>Ta\u015f\u0131nabilir Teknoloji Se\u00e7mek Neden \u00d6nemli<\/h2>\n<p>Bir sitenin ba\u015fka bir sa\u011flay\u0131c\u0131ya ta\u015f\u0131nabilmesi, \u00fczerine kuruldu\u011fu teknolojinin standart olmas\u0131na ba\u011fl\u0131d\u0131r. PHP ve MySQL ile \u00e7al\u0131\u015fan bir WordPress sitesi, cPanel yede\u011fiyle birlikte hemen her Linux hosting hesab\u0131na geri y\u00fcklenebilir. Kapal\u0131 bir site olu\u015fturucuda haz\u0131rlanm\u0131\u015f sayfalar ise \u00e7o\u011fu zaman d\u0131\u015fa aktar\u0131lamaz; hizmet kapand\u0131\u011f\u0131nda i\u00e7erik s\u0131f\u0131rdan kurulur.<\/p>\n<p>Se\u00e7im yaparken sorulacak soru \u015fudur: bu site ba\u015fka bir firmaya ta\u015f\u0131nmak istense hangi dosyalarla, ka\u00e7 ad\u0131mda ta\u015f\u0131n\u0131r. Ta\u015f\u0131man\u0131n ad\u0131mlar\u0131, TTL ayar\u0131 ve e-postan\u0131n kesintisiz aktar\u0131lmas\u0131 <a href=\"https:\/\/narhost.com\/blog\/hosting-nasil-tasinir\/\" title=\"Hosting Nas\u0131l Ta\u015f\u0131n\u0131r \u2014 Narhost Blog\">hosting nas\u0131l ta\u015f\u0131n\u0131r<\/a> yaz\u0131s\u0131nda ayr\u0131nt\u0131l\u0131 anlat\u0131l\u0131yor. Sa\u011flay\u0131c\u0131 se\u00e7erken bak\u0131lacak di\u011fer \u00f6l\u00e7\u00fctleri ise <a href=\"https:\/\/narhost.com\/blog\/hosting-nasil-secilir\/\" title=\"Hosting Nas\u0131l Se\u00e7ilir \u2014 Narhost Blog\">hosting nas\u0131l se\u00e7ilir<\/a> rehberi bir arada topluyor.<\/p>\n<figure class=\"nh-sema\"><img loading=\"lazy\" src=\"https:\/\/narhost.com\/blog\/wp-content\/uploads\/2026\/09\/hosting-firmasi-kapanirsa-sema-narhost.webp\" alt=\"hosting firmas\u0131 kapan\u0131rsa siteyi yeniden a\u00e7mak i\u00e7in alan ad\u0131, d\u0131\u015f yedek, DNS eri\u015fimi ve geri y\u00fckleme ad\u0131mlar\u0131n\u0131 g\u00f6steren \u015fema\" width=\"1200\" height=\"500\" loading=\"lazy\" decoding=\"async\"><figcaption>Alan ad\u0131 sizde, yedek sa\u011flay\u0131c\u0131 d\u0131\u015f\u0131nda, DNS eri\u015fimi belgeli ve geri y\u00fckleme denenmi\u015fse kapanma birka\u00e7 saatlik bir ta\u015f\u0131maya d\u00f6n\u00fc\u015f\u00fcr.<\/figcaption><\/figure>\n<h2>Hosting Firmas\u0131 Kapan\u0131rsa Haz\u0131r Olmak \u0130\u00e7in S\u0131ra<\/h2>\n<p>Haz\u0131rl\u0131\u011f\u0131n do\u011fru s\u0131ras\u0131 alan ad\u0131yla ba\u015flar, yedekle devam eder ve yeni sunucuda denenmi\u015f bir geri y\u00fcklemeyle biter. Geri y\u00fcklemesi hi\u00e7 denenmemi\u015f bir yedek, bozuk \u00e7\u0131kt\u0131\u011f\u0131 g\u00fcn fark edilir. Y\u0131lda bir kez yede\u011fi test ama\u00e7l\u0131 bir hesaba a\u00e7\u0131p sitenin \u00e7al\u0131\u015ft\u0131\u011f\u0131n\u0131 g\u00f6rmek, hosting firmas\u0131 kapan\u0131rsa ya\u015fanacak pani\u011fi birka\u00e7 saatlik rutin bir i\u015fe \u00e7evirir.<\/p>\n<div class=\"success-box\">\n<p class=\"label\">Sonu\u00e7<\/p>\n<p>Sa\u011flay\u0131c\u0131n\u0131n gelece\u011fini kontrol edemezsiniz, ama elinizdekini kontrol edebilirsiniz. Alan ad\u0131 sizin ad\u0131n\u0131za ve sizin eri\u015fiminizde, tam yede\u011fin bir kopyas\u0131 sa\u011flay\u0131c\u0131n\u0131n d\u0131\u015f\u0131nda, DNS bilgileri belgelenmi\u015f ve site standart bir teknolojide ise hangi firman\u0131n kapand\u0131\u011f\u0131n\u0131n \u00f6nemi azal\u0131r.<\/p>\n<\/div>\n<h2>Kontrol Listesi<\/h2>\n<ul class=\"kontrol-listesi\">\n<li>WHOIS kayd\u0131nda alan ad\u0131 sahibi olarak \u015firketinizin g\u00f6r\u00fcnd\u00fc\u011f\u00fcn\u00fc do\u011frulay\u0131n.<\/li>\n<li>Alan ad\u0131 ve hosting panelinin \u015fifrelerini \u015firketin \u015fifre y\u00f6neticisine kaydedin.<\/li>\n<li>Kay\u0131t firmas\u0131n\u0131n ileti\u015fim adresini ba\u015fka bir alan ad\u0131na ba\u011fl\u0131 bir e-posta yap\u0131n.<\/li>\n<li>Tam hesap yede\u011fini d\u00fczenli aral\u0131kla indirip sa\u011flay\u0131c\u0131 d\u0131\u015f\u0131nda saklay\u0131n.<\/li>\n<li>DNS kay\u0131tlar\u0131n\u0131z\u0131n g\u00fcncel listesini bir belgede tutun.<\/li>\n<li>Alan ad\u0131 ve hosting yenileme tarihlerini takvime ekleyin, otomatik yenilemeyi a\u00e7\u0131n.<\/li>\n<li>Yede\u011fi y\u0131lda bir kez ba\u015fka bir hesapta geri y\u00fckleyerek deneyin.<\/li>\n<\/ul>\n<div class=\"kb-faq\">\n<h2>S\u0131k\u00e7a sorulan sorular<\/h2>\n<h3>Hosting firmas\u0131 kapan\u0131rsa alan ad\u0131m da gider mi?<\/h3>\n<p>Kendili\u011finden gitmez. Alan ad\u0131 hosting&#8217;den ayr\u0131 bir kay\u0131tt\u0131r ve s\u00fcresi dolana kadar sizin ad\u0131n\u0131za kay\u0131tl\u0131 kal\u0131r. Genel uzant\u0131larda kay\u0131t firmas\u0131 kapan\u0131rsa ICANN alan adlar\u0131n\u0131 ba\u015fka bir akrediteli firmaya aktar\u0131r. \u00d6nemli olan WHOIS&#8217;te sahip olarak sizin g\u00f6r\u00fcnmeniz ve ileti\u015fim e-postan\u0131z\u0131n \u00e7al\u0131\u015fmas\u0131d\u0131r.<\/p>\n<h3>Sa\u011flay\u0131c\u0131n\u0131n ald\u0131\u011f\u0131 otomatik yedek yetmez mi?<\/h3>\n<p>G\u00fcnl\u00fck ar\u0131zalar i\u00e7in yeter, kapanma senaryosu i\u00e7in yetmez. Otomatik yedekler sa\u011flay\u0131c\u0131n\u0131n altyap\u0131s\u0131nda durur; firma ya da hesab\u0131n\u0131z eri\u015filemez oldu\u011funda bu yedeklere de ula\u015famazs\u0131n\u0131z. Tam hesap yede\u011finin bir kopyas\u0131n\u0131 d\u00fczenli olarak indirip kendi bilgisayar\u0131n\u0131zda ya da ayr\u0131 bir depolamada saklaman\u0131z gerekir.<\/p>\n<h3>E-postalar\u0131m da kaybolur mu?<\/h3>\n<p>Sunucudaki posta kutular\u0131 sunucuyla birlikte eri\u015filemez olur. Tam hesap yede\u011fi e-posta kutular\u0131n\u0131 da i\u00e7erir, bu y\u00fczden yede\u011finiz g\u00fcncelse e-postalar\u0131 yeni sunucuya geri y\u00fckleyebilirsiniz. Bilgisayar\u0131n\u0131zdaki e-posta istemcisi IMAP yerine yerel kopya tutuyorsa o ar\u015fiv de ikinci bir g\u00fcvence olur.<\/p>\n<h3>Ajans\u0131m alan ad\u0131n\u0131 kendi ad\u0131na kaydetti, ne yapmal\u0131y\u0131m?<\/h3>\n<p>Ajansla konu\u015fup sahip bilgisini \u015firketinize \u00e7evirmesini isteyin; ajans teknik i\u015fler i\u00e7in yetkili ki\u015fi olarak kalabilir. Bu de\u011fi\u015fiklik iyi ili\u015fki varken kolayd\u0131r, anla\u015fmazl\u0131k \u00e7\u0131kt\u0131ktan sonra aylar s\u00fcrebilir. De\u011fi\u015fiklikten sonra WHOIS kayd\u0131nda \u015firket ad\u0131n\u0131z\u0131n g\u00f6r\u00fcnd\u00fc\u011f\u00fcn\u00fc kontrol edin.<\/p>\n<h3>Yeni sunucuda site ne kadar s\u00fcrede a\u00e7\u0131l\u0131r?<\/h3>\n<p>Elinizde tam yedek ve alan ad\u0131 eri\u015fimi varsa geri y\u00fckleme ve DNS de\u011fi\u015fikli\u011fi birka\u00e7 saatlik i\u015ftir. DNS de\u011fi\u015fikli\u011finin t\u00fcm d\u00fcnyaya yay\u0131lmas\u0131 TTL de\u011ferine ba\u011fl\u0131 olarak birka\u00e7 saati bulabilir. Yedek yoksa s\u00fcre, sitenin ne kadar\u0131n\u0131n yeniden olu\u015fturulmas\u0131 gerekti\u011fine g\u00f6re g\u00fcnlerle \u00f6l\u00e7\u00fcl\u00fcr.<\/p>\n<\/div>\n<div class=\"cta-box\">\n<p class=\"label\">Narhost&#8217;ta<\/p>\n<p>Web hosting paketlerimizde cPanel \u00fczerinden tam hesap yede\u011finizi istedi\u011finiz zaman indirebilir, haftal\u0131k al\u0131nan yedeklere ek olarak kendi kopyan\u0131z\u0131 kendiniz saklayabilirsiniz.<\/p>\n<p><a class=\"cta-btn\" href=\"https:\/\/narhost.com\/web-hosting\" title=\"Narhost Web Hosting paketleri\">Web hosting paketlerini incele<\/a><\/div>\n","protected":false},"excerpt":{"rendered":"<p>Hosting firmas\u0131 kapan\u0131rsa siteniz, veritaban\u0131n\u0131z ve e-postalar\u0131n\u0131z eri\u015filemez olur; elinizde g\u00fcncel bir tam yedek ve alan ad\u0131n\u0131z\u0131n y\u00f6netimi varsa site ba\u015fka bir sunucuda ayn\u0131 g\u00fcn yeniden a\u00e7\u0131labilir. Riskler, alan ad\u0131 g\u00fcvencesi ve haz\u0131rl\u0131k listesi bu yaz\u0131da.<\/p>\n","protected":false},"author":1,"featured_media":2837,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[8],"tags":[],"class_list":["post-2836","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-hosting"],"_links":{"self":[{"href":"https:\/\/narhost.com\/blog\/wp-json\/wp\/v2\/posts\/2836","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/narhost.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/narhost.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/narhost.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/narhost.com\/blog\/wp-json\/wp\/v2\/comments?post=2836"}],"version-history":[{"count":1,"href":"https:\/\/narhost.com\/blog\/wp-json\/wp\/v2\/posts\/2836\/revisions"}],"predecessor-version":[{"id":2838,"href":"https:\/\/narhost.com\/blog\/wp-json\/wp\/v2\/posts\/2836\/revisions\/2838"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/narhost.com\/blog\/wp-json\/wp\/v2\/media\/2837"}],"wp:attachment":[{"href":"https:\/\/narhost.com\/blog\/wp-json\/wp\/v2\/media?parent=2836"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/narhost.com\/blog\/wp-json\/wp\/v2\/categories?post=2836"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/narhost.com\/blog\/wp-json\/wp\/v2\/tags?post=2836"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}