How to transfer a domain name

/ shuibaco | 水八口记

Original link: https://blog.shuiba.co/failed-to-transfer-domain

Brother Dou took his baby to the water park today, I am so happy, the me-time came unexpectedly! It just so happens that I have done a lot of things recently, and my desire to record is particularly strong. I can get a whole day of blogging time, and my heart is full of joy. So let us quickly get to the point!

Speaking of which, when I was researching image anti-leeching before, I accidentally learned that Cloudflare is good, so after AWS WAF deducted 1,000 yen from me every month, I became dissatisfied. WAF seems to be a bit of an overkill for my little blog, and the cost is not low, so there is really no need to continue. I stopped using it for a month and stopped the loss in time. Just two days ago, Name.com sent me an email that the domain name was about to expire. I thought it was time to transfer the domain name, so I jumped up from a light sleep one night and started to study how to transfer the domain name to Cloudflare.

● If WAF fits my needs

1. Transfer the domain name to Route 53

2. Continue to use S3 and WAF



● If WAF does not fit my needs ←现在是这种情况

1. Shut down WAF

2. Transfer the domain name to Cloudflare and use its anti-leech settings

3. Consider transferring to R2

After reading relevant information, inquiring about the price 1 , and knowing that it comes with WHOIS privacy 2 and SSL certificate 3 , I rolled up my sleeves and started working without hesitation. Adding a domain name, modifying the DNS to Cloudflare, and entering the transfer code, the whole process was done in one go, but it failed in the end. Take a closer look, I don’t know when shuiba.co turned into a premium domain! I went crazy, googled, and even consulted Name.com’s live support4 , and was told it was “a decision from above”, and there was nothing they could do but suggest that I switch to a registrar that supports premium domain. Cloudflare does not support it, because it focuses on high cost performance, and the premium domain seems to be a bit special, so it is difficult to handle. Similarly, Route 53 does not support it. Of course, being cautious, I checked the information of Route 53 to verify the correctness of this idea. That’s okay, I stopped thinking about switching to Route 53.

As for the “top”, it refers to the registry, and the place where we usually buy domain names is called a registrar, and there is a concept of a registrant, which refers to you and me Those who buy domain names5 . Therefore, when a domain name is judged as premium, registrars such as Name.com cannot return it to normal status. Ah, a typical case of being tricked.

Although the domain name transfer failed and my plan to delete another account failed, I found that DNS can still enjoy its anti-leech service in Cloudflare7. So I reset all the records according to the gourd painting, and also deleted the expired records by the way. Also set SSL/TLS to Full , and turn on Hotlink Protection in Scrape Shield . So far, except for the cheap domain name fee, the free SSL and image anti-leeching have been successfully set up.

Some people say that Cloudflare only protects pictures but not other multimedia files such as videos. I have no conditions to test Cloudflare, but I have tested that WAF can protect videos. ——Excerpt from “AWS Picture Bed Anti-leech Link”

Still using Blogger to test, the picture is blank, and the video can be watched. Direct access to pictures or video links can also be displayed or downloaded. I think it’s enough for the free service to achieve this level. No matter how bad it is, there are still 3 WAFs that can be set up. I feel full of security. What’s more, there is CloudFront blocking it, so it can be said that there are many barriers.

I originally planned to try R2 after transferring the domain name to Cloudflare. If it is similar to S3, it would be better to move the image bed to 8 , so that I can reduce another account! When I am old, I love to do subtraction very much, I am addicted to breaking away, and I started minimalism. Maybe it was because of the failure to delete the account one after another, I remembered the decision I made a long time ago, turned my head and closed Paypal, ah, so refreshing!

  1. Cloudflare’s .co domain is $22 a year, and Name.com is $31 a year.
    ↩
  2. Name.com can be exempted by entering the discount code PRIVACYPLEASE when purchasing, which is equivalent to free.
    ↩
  3. You no longer need to pluck Tencent Cloud’s wool , and you don’t have to update it every year.
    ↩
  4. The benefits of tossing late at night, crooked nuts are all online! It’s still a human service.
    ↩
  5. “What is the difference between a registry, registrar and registrant?”
    ↩
  6. Name.com was retained and renewed.
    ↩
  7. This time I reviewed it and found out that @wellsleep mentioned Cloudflare’s CDN’s own certificate in the comment of “Tencent Cloud Free SSL Certificate” .
    ↩
  8. The UI difference between Cloudflare and AWS is like the difference between a cool girl and a straight boy.
    ↩

This article is transferred from: https://blog.shuiba.co/failed-to-transfer-domain
This site is only for collection, and the copyright belongs to the original author.