Slashdot Mirror


Ask Slashdot: Smartest Way To Transfer an Old Domain/Site?

An anonymous reader writes "Back in early 95 I registered a domain name and built a website for a hobby of mine. Over time the website (and domain) name have built a small but steady stream of traffic but my interest in the hobby is essentially gone and I've not been a visitor to my own site in well over two years. I'd like to sell the site/domain to a long time member who has expressed interest in taking over and trying to grow the site, however I use the domain for my own personal email including banking, health insurance, etc. How have fellow readers gone about parting ways from a domain that they've used for an email address?" More generally, what terms would you like to include (or have you included) in a domain transfer? Old horror stories could help prevent new horror stories.

36 of 113 comments (clear)

  1. Step 1 by leighklotz · · Score: 3, Insightful

    I'd create a new domain for yourself first...you need to get off the old one.

    1. Re:Step 1 by HappyDrgn · · Score: 2

      I would take the added step of putting an auto reply / vacation message on the old mailbox, so that anyone emailing you gets a reply telling them your email address has changed, but still forwarding the message so you still get it.

    2. Re:Step 1 by fafaforza · · Score: 2

      Potentially creating backscatter spam. I would respond personally/manually. Set up a separate folder or mark any mail being sent to the old domain so that it's easier to spot anything still going to that domain.

      And I think I'd wait about a year after moving to a new domain for email before handing over the hobby domain. And even then, I'd require to run the email server for at least a few months after that so that no forwards can be changed and mail can't be seen.

    3. Re:Step 1 by edb · · Score: 2

      Please don't generate a new email message, that's a potential source of new spam.

      Much better to configure your SMTP server to reject the email at SMTP connect time, with the error message containing the new address to use. The error message usually ends up visible to the human sender, and spam 'bots will ignore it.

      --
      In theory, practice and theory are the same. In practice, they rarely are.
  2. Maybe by Anrego · · Score: 5, Insightful

    Disclaimer: I have no experience in this situation this is just my take on this so take with lots of salt (well.. try and keep it under 1500ml if you are watching your sodium.. )

    I’d move the site to a new domain name owned by the new guy, keep the current domain name, and just set up a friendly redirect page (with an appropriate explanation to users).

    Eventually people/search engines will learn the new domain name (and even if they don’t.. keeping the redirect up forever is probably nothing) and you can start migrating to a new email address while keeping the old domain name “just in case”.

    If other people have email accounts or rely on other services on the current domain... then it gets more complicated.

    Also I’d personally like to thank you for asking a question that is:

    - non-trivial
    - can benefit from the vast amount of diversity and experience within the slashdot crowd
    - will probably generate interesting stories
    - and most importantly, isn’t depressing as hell nor a reminder that everything is falling apart in our industry

    This is what "ask slashdot" could be! We really need more of this!

    1. Re:Maybe by ganjadude · · Score: 5, Insightful

      I agree with this as well. sometime around 2001 I was working with a fairly big niche website, maybe around 25000 users 2500 regular users. and they not only transfered ownership of the site but they changed the name of the site as well. What we ended up doing was buying the new domain and setting up the new site with new logos etc than we simply put a redirect up on the old domain, left it for about 6 months before the traffic to the old domain was pretty much zero and the new domain was flourishing.

      Fast forward to around 2008, A turn based web game community I was an administrator for sold out a portion of the community to zynga, thescum of the gaming world. He decided that with a portion of the community gone that it would be good to change the name of the rest of the portion he maintained. He proceeded to change the forum,the 4 different domains and put them all on one domain where before it was a little cluster. Overnight he did this, he killed the original links to everything but the forum. Traffic declined 65% in that first week and it never recovered.

      --
      have you seen my sig? there are many others like it but none that are the same
    2. Re:Maybe by Qzukk · · Score: 4, Interesting

      If you absolutely want to give them the domain, then tell whoever to set up their own hosting and change the A records for the website to the new host while keeping the MX records and adding an old.example.com A record for people to access the old site while you transfer data between hosting companies. In the meantime, get a new domain and start updating everyone who emails you with your new address. After a suitable time (you no longer receive email at the old address), transfer the domain to this person.

      As a bonus, it means that whoever is wanting to take over the domain is going to have to prove they're going to run it for several months. If they decide that it costs too much to run, flake out, or just turn it into a porn site, you can point the A record back and find someone else.

      --
      If I have been able to see further than others, it is because I bought a pair of binoculars.
    3. Re:Maybe by uncledrax · · Score: 2

      So you're arguing that the parent is correct, and users should DEFINITELY keep under 1500ml of sodium?

      --
      ----- The internet has given everyone the ability to have their voice heard equally as loud.. even if they shouldn't be
  3. Don't trust the buyer by Anonymous Coward · · Score: 3, Insightful

    I'm sure he's a nice guy, but migrate everything away from that domain before selling. This means adjusting every account you've signed up for using that email address/etc. Then wait six months and see if anything new comes in. Under no circumstances should you expect to receive any forwarded mail without someone having read it.

    1. Re:Don't trust the buyer by characterZer0 · · Score: 2

      Under no circumstances should you expect to receive any forwarded mail without someone having read it.

      This holds for any email on any system. Use PGP.

      --
      Go green: turn off your refrigerator.
    2. Re:Don't trust the buyer by Anrego · · Score: 5, Insightful

      Sounds reasonable.

      Once he's convinced his bank, health care provider, and generally everyone outside an extremely small group of people of this.. he'll be all set! (well, except that this doesn't really protect against the new owner killing his email service outright either).

      (All kidding aside, it's a lost cause. PGP isn't simple enough for the masses, doesn't work well with the whole webmail thing (aka how just about everyone access their email these days), and in the few cases where it works, ironically makes non-geeks more nervous (why does this email say something about security, am I being hacked!!!).

    3. Re:Don't trust the buyer by Anrego · · Score: 3, Insightful

      Actually it's the opposite!

      My experience is non-technically inclined people tend to associate different with bad. When an email shows up and has a different colored title, or a weird symbol, or a dialog pops up asking them something about keyrings ... they freak out and get nervous (especially if they see words like "security").

      More importantly, most users don't care about this stuff. It's not intuitive for them to think "oh, this means I can be reasonable sure thsi email hasn't been tampered with and was actually sent by this person (or someone with access to their PC)".

      The problem is to be successful for the masses, PGP would have to have immediate widespread adoption in email clients, which isn't going to happen.

    4. Re:Don't trust the buyer by darkpixel2k · · Score: 2

      Under no circumstances should you expect to receive any forwarded mail without someone having read it.

      This holds for any email on any system. Use PGP.

      The number of companies out there that have a 'preferences' page with a space for my public key is astounding. Every single e-mail I get from them is encrypted...er...wait. Welcome back to the real world. Unless it's something that happens automatically (so your mother and grandmother don't have to figure it out) it won't happen.

      --
      There's no place like ::1 (I've completed my transition to IPv6)
  4. Keep the domain IMO by mewsenews · · Score: 5, Informative

    There's no clean way to ensure a new owner will provide service for your old email address to your satisfaction.

    However, it is ridiculously easy for you to set up a permanent redirect from the front page of the website to a new location managed by this guy who is interested in being the new maintainer.

    You could even set him up with a subdomain of the current domain name so that folks feel comfortable that it's the same old site they've been visiting for years. This requires very little effort on your part and you maintain control over your email address.

    1. Re:Keep the domain IMO by trnk · · Score: 5, Insightful

      Next week on ask slashdot: 'I'm a long-term user of a forum on a domain that the owner is no longer interested in, I've offered to buy from him but instead he's told me he wants to keep it and offered to let me purchase a redirect to my servers instead. I was planning on investing quite a bit of time and money to build up the site and it's brand but I'm worried about him retaining control. Is this a good idea?'

      ...Well, there's no clean way to ensure the old owner will provide service for your forward to your satisfaction...etc.

      Come on, everyone saying 'just keep the old domain' really isn't considering the implications of that for the interested buyer.

  5. Do you want to get rid of the entire domain? by Anonymous Coward · · Score: 4, Informative

    Might it simply be sufficient to transfer your site hosting to the other party and point the DNS records for the site itself to whenever they want? You can then have your mail hanging off the original domain and retain control of it.

  6. Keep the domain, transfer the web site? by Fastolfe · · Score: 5, Informative

    Why do you want to transfer the domain when you can just give him/her control of the web site? You can continue to own the services on the domain that matter to you (mail) and they'd own the HTTP service on the IP address you point the domain to. This could even be an intermediate step to full ownership transfer once you've moved your identity someplace else and are comfortable with the new owner of the domain taking more ownership over it.

  7. Not even that complicated by Anonymous Coward · · Score: 5, Informative

    Keep the domain, yes, but "lease" the rights to the www version of the site. Your DNS record can point the MX record to your mail sever (or Gmail, or whatever), while the A records for the domain and www host to wherever he wants to host it. You may wish to setup forwarding on certain addresses for him, like webmaster@, but make sure the domain is locked and secured to you first.

    1. Re:Not even that complicated by JWSmythe · · Score: 3, Informative

      You shouldn't have posted as AC. Some people won't see this, and you have the right answer.

          Set the A records to wherever the new web hosting provider will be. Set the MX record to where the mail is to be delivered. It will then be up to him (the submitter) to forward mail for anything specific at the domain, such as webmaster@ to the real webmaster.

          Or in bind...

      ;
      ; domain: example.com
      ;
      $TTL 3600
      @ IN SOA ns.example.com. webmaster.example.com. (
                      2012021401 ; Serial (soa version)
                      14400 ; Refresh after three hours
                      3600 ; Retry after one hour
                      86400 ; Expire after one day
                      3600 ) ; Mininum TTL of one hour
      ;
      ; name servers for this domain
      ;
                              IN NS ns1.example.com.
                              IN NS ns2.example.com.
                              IN NS ns3.example.com.
      ;
      ; A and MX records
      ;
       
      example.com. IN A 1.2.3.4
      www.example.com. IN A 1.2.3.4
      mail.example.com. IN A 5.6.7.8
      example.com. IN MX mail.example.com.
       
      example.com. IN TXT "v=spf1 ip4:5.6.7.0/25 a mx include:example.com include:example.com ~all"
      *.example.com. IN TXT "v=spf1 ip4:5.6.7.0/25 a mx include:example.com include:example.com ~all"

      And most importantly, the submitter shouldn't have needed to even ask this. Dearest submitter, please turn in your geek card on your way out.

      --
      Serious? Seriousness is well above my pay grade.
    2. Re:Not even that complicated by Atzanteol · · Score: 4, Insightful

      And most importantly, the submitter shouldn't have needed to even ask this. Dearest submitter, please turn in your geek card on your way out.

      Perhaps he does, or maybe simply hadn't thought of it. Either way he's looking for options and advice based on personal experience. What's wrong with that?

      --
      "Ignorance more frequently begets confidence than does knowledge"

      - Charles Darwin
    3. Re:Not even that complicated by icebraining · · Score: 2

      You can even set up an NS record just for the subdomain and let them manage their own A records without having to waste time in case they change hosts or something.

    4. Re:Not even that complicated by Anonymous Coward · · Score: 2

      Upvote for informative. Downvote for being an asshole.

  8. Dear Jerry... by srussia · · Score: 5, Funny

    Over time the website (and domain) name have built a small but steady stream of traffic but my interest in the hobby is essentially gone and I've not been a visitor to my own site in well over two years. I'd like to sell the site/domain to a long time member who has expressed interest in taking over and trying to grow the site, however I use the domain for my own personal email including banking, health insurance, etc.

    There's nothing for it but to just suck it up and keep your yahoo.com e-mail.

    --
    Set your phasers on "funky"!
  9. CmdrTaco, is that you? by utahjazz · · Score: 5, Funny

    my interest in the hobby is essentially gone and I've not been a visitor to my own site in well over two years.

    CmdrTaco, is that you?

  10. HTTP 301 by chenjeru · · Score: 5, Informative

    As Anrego says, I'd suggest not actually handing over the domain. Instead, rebuild the site under a new domain while updating key content such as contact links, and then set up an "HTTP 301: permanently moved" redirect to the new site on the new domain. This will transfer your pagerank to the new domain and makes search engines happy. Then, you can keep your email and other domain services under your own control.

    --
    Even if you're on the right track, you'll get run over if you just sit there. - Will Rogers
  11. MX records are your friend... by klubar · · Score: 2

    If there is a little bit of trust between you and the buyer the following will work.

    Change the MX record on the domain to point to your own mail server. You'll continue to get the mail and can forward all of the site mail to the new owner (using some other domain).

    Get a new email address and update all your accounts to point to the new address. After 6 months or so, just hand over the DNS control to the new owner.

    If there is no trust between you and the buyer it's going to be complex, involve lawyers and probably an escrow agent. I'm guessing the site doesn't generate enough revenue to be worth the compexity. If there isn't trust, unless the site is worth more than $20K (or so) it probably will cost more in legal and escrow fees than you'll get for the domain.

  12. loose coupling by s1d3track3D · · Score: 2

    thanks for reminding me to not couple my personal duties with my interestes/domains/sites.

    interestes and hobbies come and go, seems the easiest way to handle this is to never have to.

  13. Sell the site, not the domain by Sloppy · · Score: 2

    Moving your email address is a hassle. Let's just assume you don't want any hassle at all, at the cost of the new guy not quite getting everything he wants (yet still be dealt with very reasonably).

    Sell the site, not the domain. Keep the domain either for the rest of your life, or until you're so bored out of your mind that you have the time to deal with moving your email (i.e. hopefully the rest of your life).

    On the still-yours domain, have a web server reply with 301 redirects to the equivalent page at the new domain. Then after a while (a year?), have it reply with 410. Then after a while, uninstall the web server. There may always be some stale links, but there's nothin' to do about that.

    --
    As copyright owner of this comment, I authorize everyone to defeat any technological measure which limits access to it.
  14. Transition period by MetalliQaZ · · Score: 2

    Move all of your accounts to a new email address ASAP. Then, over the course of a few months, watch the old email address closely. Watch for any straggling emails going to the old email. Fix any stragglers. When you are comfortable that the only thing showing up is SPAM, then transfer the domain.

    Look, there's no way you can be 100% sure. The best thing would be to trust the new guy.

    Speaking of stragglers... Just today I noticed that two large companies (one named after a large South American river, the other is a giant Bank in America) that were still sending stuff to an old email address after I had changed my account preferences. Obviously my old address lingers in their databases without any user interface to clean it.

    --
    "Here Lies Philip J. Fry, named for his uncle, to carry on his spirit"
  15. Re:Step 2 by Joce640k · · Score: 5, Informative

    Step 2: Run *both* domains for at least six months.

    Change all mail that's in databases (bank, etc), tell as many friends as possible to use the new address.

    Set up mail forwarding to the new domain so you always hit 'reply' from there. Never reply on the old domain.

    Meanwhile, give your friend access to as much of the site as possible while still keeping the admin password to yourself. Most servers allow separate FTP accounts, etc., he should be able to change files without admin access.

    --
    No sig today...
  16. DNS does that for you... by xded · · Score: 2

    DNS A records (i.e., the ones that provide IP addresses to web browsers) are different from MX records (i.e., the ones that provide IP addresses to MTAs), and in your domain you already have both.

    Just keep the ownership of your domain, point the A record to the new guy's server and keep the MX record as it is (or point it to Gmail, to finally move all the email addresses off your SquirrelMail thing...)

  17. Nice try... by rampant+mac · · Score: 4, Funny

    "Back in early 95 I registered a domain name and built a website for a hobby of mine"

    Nice try Mr. Goatse. We're not falling for this one again.

    --
    I like big butts and I cannot lie.
    1. Re:Nice try... by Chrisq · · Score: 4, Funny

      "Back in early 95 I registered a domain name and built a website for a hobby of mine"

      Nice try Mr. Goatse. We're not falling for this one again.

      anal stretching was his hobby, you insensitive clod.

  18. Comment removed by account_deleted · · Score: 2

    Comment removed based on user account deletion

  19. Re:Step 1, reversed by rduke15 · · Score: 5, Informative

    I'd create a new domain for yourself first

    No. Do it the other way around. I would create a new domain for the new guy taking over your site, or let him do it. Then transfer the web content to the new site, and set up a redirect on your site to the new one.

    That way, people going to the old web site end up on the correct new site, but you don't have to change or worry about anything related to your personal email addresses.

    If your web site also used email @yoursite, then YOU take care of setting up a redirect or whatever solution seems best.

    You don't want to have your personal stuff at the mercy of someone else, or to have to call him to find out what the problem is if he made some configuration mistake or whatever.

  20. Re:Step 2 by Dan541 · · Score: 2

    Set up mail forwarding to the new domain so you always hit 'reply' from there. Never reply on the old domain.

    Also if you filter the mail into a separate folder it helps you to find contacts and services still using the old address.

    --
    An SQL query goes to a bar, walks up to a table and asks, "Mind if I join you?"