Follow Slashdot blog updates by subscribing to our blog RSS feed

 



Forgot your password?
typodupeerror
×
The Internet Communications IT

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

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.
This discussion has been archived. No new comments can be posted.

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

Comments Filter:
  • Keep the domain IMO (Score:5, Informative)

    by mewsenews ( 251487 ) on Tuesday February 14, 2012 @02:02PM (#39035029) Homepage

    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.

  • by Anonymous Coward on Tuesday February 14, 2012 @02:03PM (#39035045)

    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.

  • by Fastolfe ( 1470 ) on Tuesday February 14, 2012 @02:04PM (#39035069)

    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.

  • by Anonymous Coward on Tuesday February 14, 2012 @02:05PM (#39035083)

    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.

  • HTTP 301 (Score:5, Informative)

    by chenjeru ( 916013 ) on Tuesday February 14, 2012 @02:09PM (#39035141)

    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.

  • Re:Step 2 (Score:5, Informative)

    by Joce640k ( 829181 ) on Tuesday February 14, 2012 @02:43PM (#39035567) Homepage

    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.

  • by JWSmythe ( 446288 ) <jwsmythe@nospam.jwsmythe.com> on Tuesday February 14, 2012 @03:02PM (#39035893) Homepage Journal

    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.

  • Re:Step 1, reversed (Score:5, Informative)

    by rduke15 ( 721841 ) <rduke15@gm[ ].com ['ail' in gap]> on Tuesday February 14, 2012 @05:37PM (#39037873)

    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.

Suggest you just sit there and wait till life gets easier.

Working...