Need help? Check out our Support site, then


how to remove redirect to wordpress domain

  1. I purchased domain mapping a few days ago and redirected a previously purchased domain to the wordpress site. This has caused huge problems since. I have since deleted the domain mapped with worrdpress. However, althought, I changed the DNS settings for the domain (where it is registered), I still have not been able to remove the redirect to wordpress. Can support or anyone on the forum advise how this can be fixed so the domain no longer points to wordpress?

    With thanks.

    The blog I need help with is talentmanagementinteams.wordpress.com.

  2. However, althought, I changed the DNS settings for the domain (where it is registered),

    I believe you will need to contact Staff directly in order to sort this.
    http://en.support.wordpress.com/contact/
    Reference link > Site Redirect > http://en.support.wordpress.com/site-redirect/

  3. ~~timethief
    Contact form's closed until Monday. I already modlooked this thread.

  4. Hi managingteams,

    Was the domain mapping for talentmanagementinteams.co.uk?

    I show the following for the name servers:
    ns1060.websitewelcome.com.
    talentmanagementinteams.co.uk.
    ns1059.websitewelcome.com.

    I'm also able to visit that site without being redirecting to WordPress.com, so it's likely just a cache issue.

    Can you please try clearing out your cache and cookies?
    http://en.support.wordpress.com/browser-issues/#clear-your-cache-and-cookies

    To flush your dns cache:

    On a PC:
    - Go to Control Panel > Network Connections
    - Right click your connection and choose "Repair"
    There is an alternative way to do this detailed at:
    http://sunnyoasis.com/services/DNS-cache-flush.php .

    On a Mac:
    - Close all browsers.
    - Go to Application > Utilities > Terminal
    - type:
    dscacheutil -flushcache

  5. ~~ airodyssey
    OOPS! I didn't notice that. :(

  6. Hi Everyone,

    Thanks for responding to my post. Fortunately, it has been sorted.

    Timethief and Airodessy -yes, support was closed for the weekend, so I was hoping that someone on the forum could have helped.

    Coffeemanmatt -thank you for you specific guidance on what could have been done. This will be helpful if I do have a cache problem, although this specific situation was not a cache issue.

    Fixing it involved further editing of DNS information, as the MX information was wrong. Also the domain had been left unlocked, so it had to be locked to prevent authorised changes.

    Yes, thankfully the problem has been fixed.

    Regards.

  7. Thanks for letting us know your issue has been resolved.

Topic Closed

This topic has been closed to new replies.

About this Topic