Aged domain setup--404 issue

6 replies
  • WEB DESIGN
  • |
Hey everyone,

I just bought my first aged domain and I'm running into a problem getting Wordpress to work on it. Here's what's happened so far:

-The owner transferred the site to my Godaddy account

-I added domain privacy, changed the nameservers to my hosting account (Bluehost) and "unlocked" the domain

-I assigned the domain to my hosting account as an "addon" domain

-I installed Wordpress and was given the message that it installed correctly.

Here's the issue: When I go to the /wp-admin page, I get an 404 error page from Hostgator, which the nameservers were pointed to before I changed them. I've already checked to make sure the nameservers are pointed to Bluehost and they are. This whole process has taken place only a few hours ago, but I've always been able to get my websites up within an hour after purchasing a new domain before.

Any ideas on what the problem could be? Thanks!
#aged #domain #issue #setup404
  • Profile picture of the author Ajay Tiwari
    Normally it takes 24-48 hours for nameserver changes to be completed and propagate through the internet. So don't worry in next few hours it will be alright..
    In your case, installation is done properly. that means nameserver changes are done properly. Sometimes due to browser cache such incidents happens, so just delete your browser cache files. Open a new window and try again to open your site. I hope that would work.
    {{ DiscussionBoard.errors[4828084].message }}
  • Profile picture of the author seasoned
    OK, you said:

    -I added domain privacy, changed the nameservers to my hosting account (Bluehost) and "unlocked" the domain

    That is exactly OPPOSITE of what should be possible! Since Icann hasn't sued verisign yet, etc... I must assume it is impossible. SO, simple question:

    Did you go into godaddy and change all the registered DNS entries to point to the DNS on your NEW site? And YEAH, it WILL take a while. Maybe a LONG while! It depends how often people on your subnet, LIKE YOU, try to go there, and the TTL settings on the domain name. The more frequently it is checked, and the larger the TTL settings, the longer it will take.

    Whether it is "aged" or not makes NO difference, outside of the fact someone can access it on your subnet and slow down the resolution.

    BTW if it fails the NEXT time, do a ping to get the IP address, and make sure it IS wrong. If it is wrong, it hasn't resolved right. If it is RIGHT, the problem is with bluehost or your settings THERE.

    BTW the domain name has pointers, set with the REGISTRAR that point to your MAIN DNS servers. THESE are supposed to resolve almost INSTANTLY!!!!!! THE MAIN DNS servers, set THERE, then point to your site. THESE are supposed to resolve almost INSTANTLY!!!!!! The PROBLEM is that when a visitor tries to look at your site, they use THEIR DNS servers. If they have been used within the TTL, they may retain the OLD address. EVENTUALLY they will expire and THEN go to the registries, use the domain name THERE to point to YOUR DNS to refresh the cache and THEN they will work.

    Steve
    {{ DiscussionBoard.errors[4828209].message }}
    • Profile picture of the author nbsteuv
      Originally Posted by seasoned View Post

      OK, you said:

      -I added domain privacy, changed the nameservers to my hosting account (Bluehost) and "unlocked" the domain

      That is exactly OPPOSITE of what should be possible! Since Icann hasn't sued verisign yet, etc... I must assume it is impossible.
      Originally Posted by seasoned View Post

      OK, you said:

      -I added domain privacy, changed the nameservers to my hosting account (Bluehost) and "unlocked" the domain

      That is exactly OPPOSITE of what should be possible! Since Icann hasn't sued verisign yet, etc... I must assume it is impossible.
      What's impossible about this? These were all just options on the Godaddy domain manager and I updated them the way I normally would.

      Can you give me more specific instructions for changing the DNS entries? The DNS manager under the Godaddy domain manager simply says "Not hosted here." I've checked on my other sites, and it says the same thing for them.

      Originally Posted by ajaykt View Post

      Normally it takes 24-48 hours for nameserver changes to be completed and propagate through the internet. So don't worry in next few hours it will be alright..
      In your case, installation is done properly. that means nameserver changes are done properly. Sometimes due to browser cache such incidents happens, so just delete your browser cache files. Open a new window and try again to open your site. I hope that would work.
      Thanks for the quick response. Deleting the cache and reopening hasn't worked yet, but I'll check it again in a few hours.
      {{ DiscussionBoard.errors[4828306].message }}
  • Profile picture of the author nbsteuv
    Just in case anybody else has the same issue and runs across this, the problem did resolve itself. A few hours later I thought to check the website with a proxy and it was up as it should have been (just not through my normal browser) and today the website appeared normal through my browser. I don't quite understand the details, but I didn't have to do anything additional.
    {{ DiscussionBoard.errors[4836071].message }}
  • Profile picture of the author Ajay Tiwari
    As i told you just wait and watch and it will be normal automatically, it happens sometimes...
    {{ DiscussionBoard.errors[4837487].message }}
  • Profile picture of the author autumnsmith
    Before pointing your domain to new hosting provider or name servers there are several things you need to check.
    You are not allowed to make changes on your domain if it is within 30 days from its expiration date.
    Ask for the nameserver of your new hosting provider and its I.P address.
    Make sure that the information is correct (spelling of nameservers) to avoid error.

    Aside from DNS name servers, there are registrars which require IP address of new name servers. The change will usually take effect within 48-72 hours for domain propagation.

    If you are getting errors, they may be caused by the following
    - domain is not yet propagated
    - you have entered wrong nameservers or I.P address
    {{ DiscussionBoard.errors[4869148].message }}

Trending Topics