Skip to main content

Wordpress to Blogger migration; Publish to personal domain name 1and1

By
How to migrate from Wordpress to Blogger and to publish your blogspot.com address to your personal domain name - e.g. publishing www.syswow64.blogspot.com at www.syswow64.co.uk

NOTE: Work in progress
  1. Log in to blogger, select your Blog
  2. Select Settings > Basic > Publishing
  3. Click Advanced settings and enter your personal domain name and hit save.

    4.  
    • You will receive an error message since you do not have proven ownership of the domain
  4. If you have your domain name registered with 1and1.co.uk (basic account) you will not be able to follow the instructions as the CNAME is too long (more than 32 characters).
  5. I suggest you change your NameServer to point at byethost.com. You will not only be able to take full control of long CNAMES but you will be able to add 5 domains and share 1000MB for free.
1and1 nameserver instructions:

  1. Login to 1and1 and go to the "Domain Overview"
  2. Select the domain name and edit the DNS settings to point to byethost.com.





















Byethost Setup instructions:
  1. Register a free account with Byethost.com
(More to follow)
    Labels:

    Comments

    1. Chris DaishJanuary 10, 2013 at 1:02 AM

      I see you have joined the dark side!

      ReplyDelete
    2. DESIGNNovember 17, 2014 at 11:08 PM

      This comment has been removed by a blog administrator.

      ReplyDelete
    3. DESIGNNovember 17, 2014 at 11:08 PM

      This comment has been removed by a blog administrator.

      ReplyDelete

    Post a Comment

    Popular posts from this blog

    SCCM Unknown computer not able to see Task Sequences after installing Current Branch 1702

    By
    Soon after installing SCCM CB 1702 we were unable to see Task Sequences deployed to the unknown collection. This issue was identified as a random system taking the GUID of the 'x64 Unknown Computer (x64 Unknown Computer)' record. As a result it was now a known GUID; as we were only deploying Task Sequences to the Unknown collection none were made available. 'x64 Unknown Computer (x64 Unknown Computer)' record 'x86 Unknown Computer (x86 Unknown Computer)' record To get the GUID of your unknown systems open SQL management studio and run the following command: --Sql Command to list the name and GUID for UnknownSystems record data select ItemKey, Name0,SMS_Unique_Identifier0 from UnknownSystem_DISC Using the returned GUID (SMS_Unique_Identifier0) we can find the hostname that has been assigned the 'x64 Unknown Computer (x64 Unknown Computer)' GUID by running the query below. --x64 Unknown Computers select Name0,SMS_Unique_Identifier0,Decommissioned0 from Sys...
    161 comments
    Read more

    Windows 7 Offline files will not go Online when connected to network

    By
    Issue Several laptop users move between networks, domain, home, etc and when they attempt to access DFS shares explorer status is working offline.  The issue only resolves it self after a reboot. Connecting directly to the share works and i am able to ping network resources.  This behavior occurs for VPN users as well. Possible Causes "slow-link mode". In win7 (with default settings) a client will enter slow-link mode if the latency to the server is above 80ms. In slow-link mode all writes are made to the local cache and a background sync only happens every 6 hours.  Depending on your connection the default slow link detection speed is 64,000 bps On client computers running Windows 7 or Windows Server 2008 R2, a shared folder automatically transitions to the slow-link mode if the round-trip latency of the network is greater than 80 milliseconds, or as configured by the "Configure slow-link mode" policy. After transitioning a folder to the slow-link mode, Offline Fil...
    151 comments
    Read more

    SCCM Software Update - Job error 0x80004005 Failed to Add Update Source for WUAgent

    By
    SCCM Software Updates - Failed to Add Update Source for WUAgent  Today I have been looking at a range of servers (Server 2008 /R2 2012 /R2) that were failing to communicate with the Software Update Point (SUP) in SCCM and retrieve deployment policy. The UpdateDeployment.log was reporting the Job error 0x80004005 Job error (0x80004005) received for assignment ({af7a48e6-d550-4070-dd9b-ecc234567584}) action UpdatesDeploymentAgent 12/6/2017 10:32:27 AM 2096 (0x0830) The WUAHandler.log  was reporting "Unable to read existing WUA Group Policy object" and "Failed to Add Update Source for WUAgent " Unable to read existing WUA Group Policy object. Error = 0x80004005. WUAHandler 12/6/2017 3:41:00 AM 2828 (0x0B0C) Failed to Add Update Source for WUAgent of type (2) and id ({3AAB6A76-CE2D-4E8A-9F11-123AE69612A1}). Error = 0x80004005. WUAHandler 12/6/2017 11:03:31 AM 2276 (0x08E4) Until the agent can report back to the SUP, SCCM will not be able to summarize Software Update sta...
    4 comments
    Read more