Created a WebSite I Can't Access

by JoshN
10 replies
So Registered a Domain name with Go Daddy 3 days ago,
changed the name servers to point over to ixwebhosting where I have it hosted and every time I go to the site its still going to godaddy.

I cleared my cookies browing history cache, ect and even tried another browser that I dont use.


I then bought another domain on godaddy the next day and also pointed it to my hosting company, within 5 minutes the correct site showed up.

The one from 3 days ago still doesnt show up for me, but it seems like anyone outside my isp can access it just fine.

Whats goin on??

Any thoughts
#access #created #website
  • Profile picture of the author jamesrich1
    Go to your C-panel and then add the domain name. It should show up on your hosting side shortly after you do this. Go install a wordpress so you can access it after you do that.
    {{ DiscussionBoard.errors[5932320].message }}
    • Profile picture of the author JoshN
      Originally Posted by jamesrich1 View Post

      Go to your C-panel and then add the domain name. It should show up on your hosting side shortly after you do this. Go install a wordpress so you can access it after you do that.
      I didn't have anything built for the site yet so I just deleted it from my list of domains and then re-created it.

      I had wordpress installed but I couldn't access it by going to xxxxxxxxx.com/wordpress and because its on a shared IP I couldn't just type in the IP either at least not to my knowledge.
      {{ DiscussionBoard.errors[5932390].message }}
  • Profile picture of the author Cataclysm1987
    DNS errors. They happen all the time.

    Reset your cache again, load a private browsing window, use a proxy, whatever.

    Or just wait a while longer and it will probably show up just fine.
    Signature

    No signature here today!

    {{ DiscussionBoard.errors[5932321].message }}
  • Profile picture of the author Sillysoft
    Well first verify the domain that isnt working is pointed to the dns server you are pointing it to. The easiest thing is ping your domain that isnt working, jot down the ip. Now ping the domain that is working and compare ip's. If the ip's do not match then you know something is up. If they are the same then maybe you didnt create the records on your hosting side to resolve the domain to your hosting account. Or maybe your isp is still caching the dns records. In which in cmd like you can do the following to clear your dns cache:

    ipconfig/flushdns

    Then:

    nbtstat -R
    {{ DiscussionBoard.errors[5932347].message }}
    • Profile picture of the author JoshN
      Originally Posted by Sillysoft View Post

      Well first verify the domain that isnt working is pointed to the dns server you are pointing it to. The easiest thing is ping your domain that isnt working, jot down the ip. Now ping the domain that is working and compare ip's. If the ip's do not match then you know something is up. If they are the same then maybe you didnt create the records on your hosting side to resolve the domain to your hosting account. Or maybe your isp is still caching the dns records. In which in cmd like you can do the following to clear your dns cache:

      ipconfig/flushdns

      Then:

      nbtstat -R
      When I was on tech support, they tried pinging my site (from a computer outside of my isp) and it came up with an Ixwebhosting ip and they were able to access the site. When I try to ping my site it comes up with a completely different ip. I am guessing the IP for the godaddy parking page which is what my browser pulls up.
      {{ DiscussionBoard.errors[5932411].message }}
      • Profile picture of the author Sillysoft
        Originally Posted by JoshN View Post

        When I was on tech support, they tried pinging my site (from a computer outside of my isp) and it came up with an Ixwebhosting ip and they were able to access the site. When I try to ping my site it comes up with a completely different ip. I am guessing the IP for the godaddy parking page which is what my browser pulls up.
        Then I suggest clearing your cache. The commands I gave you are to run in cmd. However if your in Windows 7 you have to run cmd.exe as an administrator. If Windows 7 you go to your start button, then search for cmd. It should then show you cmd.exe, simply right click it then click on run as administrator. It will ask you to verify this, click ok or yes. Then the command line window will pop up, black screen.

        There type

        ipconfig/flushdns

        Then hit enter

        Then type

        nbtstat -R

        The hit enter

        Next ping your site that isnt working again and see if the ip changed.
        {{ DiscussionBoard.errors[5932442].message }}
        • Profile picture of the author JoshN
          Originally Posted by Sillysoft View Post

          Then I suggest clearing your cache. The commands I gave you are to run in cmd. However if your in Windows 7 you have to run cmd.exe as an administrator. If Windows 7 you go to your start button, then search for cmd. It should then show you cmd.exe, simply right click it then click on run as administrator. It will ask you to verify this, click ok or yes. Then the command line window will pop up, black screen.

          There type

          ipconfig/flushdns

          Then hit enter

          Then type

          nbtstat -R

          The hit enter

          Next ping your site that isnt working again and see if the ip changed.
          Gotcha. I just did it and the first command worked and the second failed. Regardless I pinged the web address and the ip changed. I tried it in my browser and it worked.

          So awesome, that worked great but just curious what did I just do? How did that work?


          Thanks guys
          {{ DiscussionBoard.errors[5932495].message }}
          • Profile picture of the author Sillysoft
            Originally Posted by JoshN View Post

            Gotcha. I just did it and the first command worked and the second failed. Regardless I pinged the web address and the ip changed. I tried it in my browser and it worked.

            So awesome, that worked great but just curious what did I just do? How did that work?


            Thanks guys
            Hmm wonder why the second one didnt work. Anyway your computer caches dns locally so that things would come up quicker without having to go out to the dns server to get the info. So this command basically removes anything in the local cache. So it appears your computer cached your new site that wasnt working to the old godaddy dns, by clearing it you forced it to find the updated info.
            {{ DiscussionBoard.errors[5932537].message }}
        • Profile picture of the author Lilypuff
          I had this same issue as well. We could not acess our site on our main computer but we could access it just fine on our iPad and iPhones. We also tried a different browser and clearing the cache. It just ended up taking some extra time. As long as other people can access your site, you know that it is running fine. Let the 72 hours run out and if it still isn't working you can try contacting the help desk again. Good luck, I know it's frustrating.
          {{ DiscussionBoard.errors[5932516].message }}
  • Profile picture of the author Sillysoft
    You can go even further and force your computer to resolve to an ip without changing the dns. I created a video on this:

    {{ DiscussionBoard.errors[5932554].message }}

Trending Topics