{"id":367,"date":"2026-08-29T16:06:07","date_gmt":"2026-08-29T16:06:07","guid":{"rendered":"https:\/\/www.vps.tc\/blog\/?p=367"},"modified":"2026-08-29T13:17:55","modified_gmt":"2026-08-29T13:17:55","slug":"alan-adi-transferi-nasil-yapilir","status":"publish","type":"post","link":"https:\/\/www.vps.tc\/blog\/tr\/alan-adi-transferi-nasil-yapilir\/","title":{"rendered":"Alan Ad\u0131 Transferi Nas\u0131l Yap\u0131l\u0131r? Ad\u0131m Ad\u0131m Rehber"},"content":{"rendered":"
\u0130\u00e7indekiler<\/strong><\/p>\n
    \n
  1. Alan ad\u0131 transferinden \u00f6nce DNS haritas\u0131n\u0131 \u00e7\u0131kar\u0131n<\/a><\/li>\n
  2. Transfer ile DNS de\u011fi\u015fikli\u011fi ayn\u0131 \u015fey de\u011fil<\/a><\/li>\n
  3. Alan ad\u0131 transferi i\u00e7in \u00f6n ko\u015fullar<\/a><\/li>\n
  4. Ta\u015f\u0131madan \u00f6nce kulland\u0131\u011f\u0131m kontrol listesi<\/a><\/li>\n
  5. Ad\u0131m ad\u0131m alan ad\u0131 transferi<\/a><\/li>\n
  6. E-posta ve DNS taraf\u0131nda dikkat edilecek noktalar<\/a><\/li>\n
  7. Transfer neden reddedilir veya bekler?<\/a><\/li>\n
  8. Alan ad\u0131 transferi s\u0131ras\u0131nda g\u00fcvenlik<\/a><\/li>\n
  9. \u00dclke uzant\u0131lar\u0131nda prosed\u00fcr de\u011fi\u015febilir<\/a><\/li>\n
  10. Ta\u015f\u0131ma plan\u0131n\u0131 ne zaman iptal etmek gerekir?<\/a><\/li>\n
  11. S\u0131k Sorulan Sorular<\/a><\/li>\n<\/ol>\n<\/div>\n

    Alan ad\u0131 transferinden \u00f6nce DNS haritas\u0131n\u0131 \u00e7\u0131kar\u0131n<\/h2>\n

    Bir alan ad\u0131 transferinde ilk bakt\u0131\u011f\u0131m yer kay\u0131t kurulu\u015funun transfer ekran\u0131 de\u011fil, terminaldir. Ge\u00e7en y\u0131l bir m\u00fc\u015fterinin alan ad\u0131n\u0131 ta\u015f\u0131ma haz\u0131rl\u0131\u011f\u0131nda NS<\/code> ve A<\/code> kay\u0131tlar\u0131n\u0131 kontrol ettim; site do\u011fru VPS’e gidiyordu. Sonra AAAA<\/code> kayd\u0131n\u0131 sorgulad\u0131\u011f\u0131mda, y\u0131llar \u00f6nce emekli edilmi\u015f bir sunucunun IPv6 adresini g\u00f6rd\u00fcm. IPv6 kullanan baz\u0131 istemciler siteye ula\u015famayacakt\u0131. Transfer ba\u015flamadan \u00f6nce kayd\u0131 temizledik.<\/p>\n

    Alan ad\u0131 transferi, alan ad\u0131n\u0131n mevcut kay\u0131t kurulu\u015fundan ba\u015fka bir kay\u0131t kurulu\u015funa ta\u015f\u0131nmas\u0131d\u0131r. Web sitenizin dosyalar\u0131, veritaban\u0131 veya sunucusu bu i\u015flemle otomatik olarak ta\u015f\u0131nmaz. De\u011fi\u015fen \u015fey, alan ad\u0131n\u0131n y\u00f6netildi\u011fi kay\u0131t kurulu\u015fudur.<\/p>\n

    Bu ayr\u0131m k\u00fc\u00e7\u00fck g\u00f6r\u00fcn\u00fcr, fakat ta\u015f\u0131ma s\u0131ras\u0131nda en \u00e7ok kar\u0131\u015f\u0131kl\u0131k burada \u00e7\u0131kar. Alan ad\u0131n\u0131 ba\u015fka firmaya ge\u00e7irirken DNS kay\u0131tlar\u0131n\u0131z, e-posta servisiniz ve sitenizin \u00e7al\u0131\u015ft\u0131\u011f\u0131 VPS ayn\u0131 kalabilir. Transferi DNS ta\u015f\u0131mas\u0131yla ayn\u0131 g\u00fcne denk getirirseniz, sorun \u00e7\u0131kt\u0131\u011f\u0131nda hangi de\u011fi\u015fikli\u011fin etkili oldu\u011funu ay\u0131rmak zorla\u015f\u0131r.<\/p>\n

    Ben alan ad\u0131 transferlerini iki ayr\u0131 i\u015f gibi planl\u0131yorum: \u00f6nce kay\u0131t kurulu\u015funu de\u011fi\u015ftiriyor, DNS’i ayn\u0131 yerde ve ayn\u0131 kay\u0131tlarla \u00e7al\u0131\u015f\u0131r halde b\u0131rak\u0131yorum. Daha sonra gerekiyorsa DNS sa\u011flay\u0131c\u0131s\u0131n\u0131 de\u011fi\u015ftiriyorum. Biraz daha yava\u015f ilerliyor; gece yar\u0131s\u0131 kaybolan e-posta kutular\u0131n\u0131 aramaktan yine de h\u0131zl\u0131.<\/p>\n

    Transfer ile DNS de\u011fi\u015fikli\u011fi ayn\u0131 \u015fey de\u011fil<\/h2>\n

    Alan ad\u0131 transferi tamamland\u0131\u011f\u0131nda nameserver kay\u0131tlar\u0131 \u00e7o\u011fu uzant\u0131da oldu\u011fu gibi kal\u0131r. Alan ad\u0131n\u0131z ns1.ornekdns.com<\/code> ve ns2.ornekdns.com<\/code> adreslerini kullan\u0131yorsa, yeni kay\u0131t kurulu\u015fu bu nameserver bilgisini devral\u0131r. Siteniz de ayn\u0131 sunucuya \u00e7\u00f6z\u00fclmeye devam eder.<\/p>\n

    Bunu varsaymak yerine transferden \u00f6nce kontrol edin. Terminalde \u015fu sorgularla mevcut durumu g\u00f6rebilirsiniz:<\/p>\n

    dig +short NS example.com\ndig +short A example.com\ndig +short AAAA example.com\ndig +short MX example.com<\/code><\/pre>\n
    dig +short<\/code> \u00e7\u0131kt\u0131s\u0131 k\u0131sa ve do\u011frudan bilgi verir. NS<\/code> kayd\u0131 DNS sunucular\u0131n\u0131, A<\/code> kayd\u0131 web sunucusunun IPv4 adresini, AAAA<\/code> kayd\u0131 IPv6 adresini, MX<\/code> kayd\u0131 ise e-postay\u0131 kabul eden sunucuyu g\u00f6sterir.<\/p>\n
    Transfer sonras\u0131nda bu sorgular\u0131 yeniden \u00e7al\u0131\u015ft\u0131r\u0131p de\u011ferleri kar\u015f\u0131la\u015ft\u0131r\u0131r\u0131m. Kay\u0131tlar de\u011fi\u015ftiyse \u00f6nce yeni kay\u0131t kurulu\u015funun DNS ekran\u0131na bakar\u0131m; hemen sunucuyu yeniden ba\u015flatmak burada hi\u00e7bir \u015feyi d\u00fczeltmez. DNS problemi log okuyarak de\u011fil, do\u011fru DNS sorgusuyla ba\u015flar.<\/p>\n
    Alan ad\u0131 transferi i\u00e7in \u00f6n ko\u015fullar<\/h2>\n
    Her alan ad\u0131 her zaman transfer edilemez. Ba\u015flamadan \u00f6nce a\u015fa\u011f\u0131daki kontrolleri tamamlay\u0131n.<\/p>\n
    Alan ad\u0131 kilidi a\u00e7\u0131k m\u0131?<\/h3>\n
    \u00c7o\u011fu alan ad\u0131, izinsiz ta\u015f\u0131may\u0131 \u00f6nlemek i\u00e7in transfer kilidiyle korunur. Kay\u0131t kurulu\u015funuzun panelinde bu se\u00e7enek Registrar Lock<\/code>, Transfer Lock<\/code> veya ClientTransferProhibited<\/code> ad\u0131yla g\u00f6r\u00fcnebilir.<\/p>\n
    Transfer ba\u015flatmadan \u00f6nce kilidi kald\u0131rman\u0131z gerekir. Baz\u0131 panellerde de\u011fi\u015fiklik birka\u00e7 dakika i\u00e7inde g\u00f6r\u00fcn\u00fcr, baz\u0131 durumlarda kay\u0131t kurulu\u015funun sistemine yans\u0131mas\u0131 daha uzun s\u00fcrebilir. Kilidi kald\u0131rd\u0131\u011f\u0131n\u0131z halde transfer ba\u015flat\u0131lam\u0131yorsa whois<\/code> veya RDAP \u00e7\u0131kt\u0131s\u0131n\u0131 kontrol edin.<\/p>\n
    Yetkilendirme kodu: EPP veya Auth Code<\/h3>\n
    EPP kodu, alan ad\u0131n\u0131n transfer yetkilendirme kodudur. Baz\u0131 firmalar bunu AuthInfo Code<\/code> veya yaln\u0131zca Transfer Code<\/code> olarak adland\u0131r\u0131r. Yeni kay\u0131t kurulu\u015fu bu kodu transfer sipari\u015fi s\u0131ras\u0131nda ister.<\/p>\n
    Kodu e-posta ile almak yerine m\u00fcmk\u00fcnse panelden kendiniz g\u00f6r\u00fcnt\u00fcleyin. Kopyalarken ba\u015f\u0131nda ya da sonunda bo\u015fluk kalmad\u0131\u011f\u0131ndan emin olun. Metin d\u00fczenleyicisinde kodu \u00f6nce d\u00fcz metin olarak kontrol etmek, g\u00f6r\u00fcnmeyen karakterleri yakalaman\u0131za yard\u0131mc\u0131 olabilir.<\/p>\n
    Alan ad\u0131 sahibinin e-posta adresi<\/h3>\n
    Transfer onaylar\u0131, kay\u0131t bilgilerindeki y\u00f6netici veya alan ad\u0131 sahibi e-posta adresine g\u00f6nderilebilir. Bu adres art\u0131k kullan\u0131lm\u0131yorsa i\u015flem beklemede kal\u0131r. Whois gizlili\u011fi kullan\u0131l\u0131yorsa adresin ger\u00e7ek posta kutusu yerine maskeli bir adres olabilece\u011fini de hesaba kat\u0131n.<\/p>\n
    Gizlilik hizmetini transferden \u00f6nce kapatman\u0131z her zaman zorunlu de\u011fildir; bu, kay\u0131t kurulu\u015funa ve uzant\u0131ya g\u00f6re de\u011fi\u015fir. Fakat onay mesaj\u0131n\u0131n hangi adrese gidece\u011fini a\u00e7\u0131k\u00e7a bilmeniz gerekir. Eski bir ajans \u00e7al\u0131\u015fan\u0131n\u0131n adresiyle kay\u0131tl\u0131 alan adlar\u0131nda en \u00e7ok zaman burada kaybediliyor.<\/p>\n
    60 g\u00fcnl\u00fck transfer k\u0131s\u0131tlamas\u0131<\/h3>\n
    Yeni kaydedilmi\u015f bir alan ad\u0131 \u00e7o\u011fu genel uzant\u0131da ilk 60 g\u00fcn i\u00e7inde transfer edilemez. Kay\u0131t sahibi veya ileti\u015fim bilgilerindeki baz\u0131 de\u011fi\u015fikliklerden sonra da 60 g\u00fcnl\u00fck transfer kilidi uygulanabilir. Bu kural \u00f6zellikle ICANN kapsam\u0131ndaki uzant\u0131larda g\u00f6r\u00fcl\u00fcr; her \u00fclke kodlu uzant\u0131da ayn\u0131 \u015fekilde uygulanmaz.<\/p>\n
    Alan ad\u0131n\u0131 yeni ald\u0131ysan\u0131z veya sahibi bilgisini az \u00f6nce de\u011fi\u015ftirdiyseniz, transfer ekran\u0131nda hata alman\u0131z normal olabilir. Kay\u0131t kurulu\u015funun destek ekibinden kilidin nedenini ve biti\u015f tarihini yaz\u0131l\u0131 olarak isteyin.<\/p>\n
    Ta\u015f\u0131madan \u00f6nce kulland\u0131\u011f\u0131m kontrol listesi<\/h2>\n
    Transfer ekran\u0131na ge\u00e7meden \u00f6nce k\u0131sa bir kontrol listesi kullan\u0131yorum. Bu liste i\u015flemi teknik olarak h\u0131zland\u0131rm\u0131yor, kritik bir \u015feyi unutma ihtimalini azalt\u0131yor.<\/p>\n