Updated nameservers but redirect still present

  • Unknown's avatar
    lynlyhbgmailcom · Member ·

    Hello! I changed to custom nameservers for my domain, but the 301 redirect to the temporary wordpress.com URL is still there. How do I remove it?

    WP.com: Yes
    Jetpack: No
    Correct account: Yes

    The blog I need help with is: (visible only to logged in users)

  • supernovia · Staff ·

    Hey there, can you share what you’re hoping to do? Here’s what I see:

    • A domain
    • The free site you listed
    • No hosting plan here
    • The domain points to another host

    Currently, when I view your domain, it brings up what looks like an unstyled WordPress installation hosted with another provider. If you’re working on a new site hosted elsewhere, and you’ve just updated the domain settings, it will start working with the new host as soon as the internet catches up with those changes. That can take a few hours, and up to a few days, depending on any caching with your internet provider.

    If you want the domain to connect to the free site you have here with us, and display the custom address instead of the free WordPress address, you’ll just need a hosting plan, then you can connect the domain and point it back to our services. The Personal Plan would most likely work nicely, but if you’d like to let us know what you have in mind for the site, we can make a recommendation.

    And, if I’ve misunderstood completely and neither of these are the issue you’re having, can you share more details here? We’ll be glad to help.

  • Unknown's avatar
    lynlyhbgmailcom · Member ·

    Hi! Thank you for taking the time to look at the site.

    My plan is to keep the domain where it is but use a different host. Anyone who visited the site before the nameservers were updated will have a permanent redirect cached in their browser, so for me it is still coming up as cotedanse431981419.wordpress.com. I am not sure of a great way to get rid of this without telling people to clear their cache? It is a difficult situation…

  • Unknown's avatar
    aisajib · Member ·

    Hi there!

    When you say you want to use the domain with a different host, do you mean your WordPress.com site at https://cotedanse431981419.wordpress.com? This site still has the demo content, so I’m not sure if this is the site you want to use your domain with.

    Also, just so we are looking at the right places, can you share the domain name you’re referring to?

    Thanks!

  • Unknown's avatar
    lynlyhbgmailcom · Member ·

    The domain is cotedanse.com. I want to keep the registrar at wordpress.com. I am not going to use the demo content, I am building a new site. The problem at the moment is that wordpress.com assigns a 301 permanent redirect which is cached in the browser even after I have changed the nameservers. Visitors that have already hit this URL in the past will be redirected to the demo site instead of the new site that I have built.

  • staff-zinnia · Staff ·

    Howdy –

    It’s important to remember that DNS changes are not instantaneous and that they take up to 3 days to become fully propagated around the globe.

    When I go to https://cotedanse.com/ I see the landing page for green geeks hosted sites. It does not redirect to an old version of your WordPress.com site.

    Checking the DNS records I can see the name servers point to greengeeks.com and do not point to WordPress.com any longer.

  • Unknown's avatar
    lynlyhbgmailcom · Member ·

    @staff-zinnia The nameservers have propagated, that is not the problem. I am taking issue with how wordpress.com has applied a permanent 301 redirect on the domain, so if I do not pay to upgrade to a custom domain and instead want to move my hosting elsewhere then I am stuck with the redirect. This does not apply to you or any new visitors because you have not visited the site before, but for anyone that has visited the site previously they will be redirected back to the wordpress.com demo site.

  • supernovia · Staff ·

    Hi,

     I am taking issue with how wordpress.com has applied a permanent 301 redirect on the domain

    We can’t 301 redirect a domain that isn’t pointed to our name servers. I can see this one is pretty well propagated across the web now, so it should be working for you, too.

    If you’re still seeing a 301 redirect, some cache may be stuck somewhere. Can you try restarting your browser or computer? If you’ve got aggressive caching with your network/ISP you may look into that, too. Here’s what I’m getting:

    curl -I cotedanse.com
HTTP/1.1 200 OK

    So no 301 there. You can try curl -I cotedanse.com (that’s I as in Ichabod) at a command prompt if you want to check from your system. If it’s showing 301, try seeing what name servers show up for you there: dig ns cotedanse.com

  • The topic ‘Updated nameservers but redirect still present’ is closed to new replies.