1 Nov 2008 at 14:52 #1 Pilky01 Pilky01 Soldato Joined 3 Jun 2008 Posts 5,060 I am trying to set up a forum for a friend. Got it all sorted out and everything but I cant view them. I just get a blank screen It works for other people and works if I view it through a proxy. Clicky
I am trying to set up a forum for a friend. Got it all sorted out and everything but I cant view them. I just get a blank screen It works for other people and works if I view it through a proxy. Clicky
1 Nov 2008 at 15:11 #2 unknowndomain unknowndomain Soldato Joined 18 Apr 2004 Posts 2,613 Location London Perhaps your isp has cached a blank page, or your isp has not yet recived the new DNS infos for your new domain name/hosting setup? Type 'ping core2.org.uk' into terminal or command line (Windows + C) See where its going, then for me who it works for its going to ... 66.197.177.69, where is it pointing for you? Last edited: 1 Nov 2008
Perhaps your isp has cached a blank page, or your isp has not yet recived the new DNS infos for your new domain name/hosting setup? Type 'ping core2.org.uk' into terminal or command line (Windows + C) See where its going, then for me who it works for its going to ... 66.197.177.69, where is it pointing for you?
1 Nov 2008 at 15:14 #3 Pilky01 Pilky01 Soldato OP Joined 3 Jun 2008 Posts 5,060 unknowndomain said: Perhaps your isp has cached a blank page, or your isp has not yet recived the new DNS infos for your new domain name/hosting setup? Click to expand... I have cleared my cache, and I don't understand the second thing (new at this) Cheers.
unknowndomain said: Perhaps your isp has cached a blank page, or your isp has not yet recived the new DNS infos for your new domain name/hosting setup? Click to expand... I have cleared my cache, and I don't understand the second thing (new at this) Cheers.
1 Nov 2008 at 15:16 #4 Pilky01 Pilky01 Soldato OP Joined 3 Jun 2008 Posts 5,060 unknowndomain said: See where its going, then for me who it works for its going to ... 66.197.177.69, where is it pointing for you? Click to expand... 194.154.164.82 Which seems to belong to these guys http://www.ripe.net/ So the problem is that its sending me to the wrong ip? Last edited: 1 Nov 2008
unknowndomain said: See where its going, then for me who it works for its going to ... 66.197.177.69, where is it pointing for you? Click to expand... 194.154.164.82 Which seems to belong to these guys http://www.ripe.net/ So the problem is that its sending me to the wrong ip?
1 Nov 2008 at 15:34 #5 unknowndomain unknowndomain Soldato Joined 18 Apr 2004 Posts 2,613 Location London Its not your temporary files cache, but some ISPs cache files to save bandwidth and provide a faster service, namely AOL. if its pointing at 194.154.164.82 it means the DNS (wikipedia it) has not had time to update, when did you register this domain name/hosting?
Its not your temporary files cache, but some ISPs cache files to save bandwidth and provide a faster service, namely AOL. if its pointing at 194.154.164.82 it means the DNS (wikipedia it) has not had time to update, when did you register this domain name/hosting?
1 Nov 2008 at 15:38 #6 Pilky01 Pilky01 Soldato OP Joined 3 Jun 2008 Posts 5,060 unknowndomain said: Its not your temporary files cache, but some ISPs cache files to save bandwidth and provide a faster service, namely AOL. if its pointing at 194.154.164.82 it means the DNS (wikipedia it) has not had time to update, when did you register this domain name/hosting? Click to expand... Yesterday, just got to wait a bit then Thanks.
unknowndomain said: Its not your temporary files cache, but some ISPs cache files to save bandwidth and provide a faster service, namely AOL. if its pointing at 194.154.164.82 it means the DNS (wikipedia it) has not had time to update, when did you register this domain name/hosting? Click to expand... Yesterday, just got to wait a bit then Thanks.
1 Nov 2008 at 15:40 #7 unknowndomain unknowndomain Soldato Joined 18 Apr 2004 Posts 2,613 Location London Yup, it can take up to 72 hours, normally only about 24 for it to propagate across all the internets.
Yup, it can take up to 72 hours, normally only about 24 for it to propagate across all the internets.
1 Nov 2008 at 16:06 #9 JIM_BOB7813 JIM_BOB7813 Soldato Joined 4 May 2004 Posts 3,270 You can edit your hosts file manually, then right click/"repair" your windows network interface, then it should work immediately.
You can edit your hosts file manually, then right click/"repair" your windows network interface, then it should work immediately.
1 Nov 2008 at 16:08 #10 Pilky01 Pilky01 Soldato OP Joined 3 Jun 2008 Posts 5,060 JIM_BOB7813 said: You can edit your hosts file manually, then right click/"repair" your windows network interface, then it should work immediately. Click to expand... Thanks, but could you explain in to me a little simpler please I have no idea about this sort of stuff
JIM_BOB7813 said: You can edit your hosts file manually, then right click/"repair" your windows network interface, then it should work immediately. Click to expand... Thanks, but could you explain in to me a little simpler please I have no idea about this sort of stuff
1 Nov 2008 at 16:35 #11 EYEREX EYEREX Soldato Joined 19 Oct 2002 Posts 2,520 Location South London Works ok for me using google chrome
1 Nov 2008 at 18:01 #12 suarve suarve Soldato Joined 8 Oct 2005 Posts 4,184 Location Midlands, UK Pilky01 said: Thanks, but could you explain in to me a little simpler please I have no idea about this sort of stuff Click to expand... open the windows/system32/drivers/etc. double click on the file called 'hosts'. Below the line - 127.0.0.1 localhost - add the ip and domain in the same format as the above line.
Pilky01 said: Thanks, but could you explain in to me a little simpler please I have no idea about this sort of stuff Click to expand... open the windows/system32/drivers/etc. double click on the file called 'hosts'. Below the line - 127.0.0.1 localhost - add the ip and domain in the same format as the above line.
1 Nov 2008 at 18:03 #13 Pilky01 Pilky01 Soldato OP Joined 3 Jun 2008 Posts 5,060 suarve said: open the windows/system32/drivers/etc. double click on the file called 'hosts'. Below the line - 127.0.0.1 localhost - add the ip and domain in the same format as the above line. Click to expand... Done that and i am still getting the same. I put 66.197.177.69 core2.org.uk Is that right? Last edited: 1 Nov 2008
suarve said: open the windows/system32/drivers/etc. double click on the file called 'hosts'. Below the line - 127.0.0.1 localhost - add the ip and domain in the same format as the above line. Click to expand... Done that and i am still getting the same. I put 66.197.177.69 core2.org.uk Is that right?
1 Nov 2008 at 22:02 #14 Pilky01 Pilky01 Soldato OP Joined 3 Jun 2008 Posts 5,060 Update: I have registered another domain and used the same host and it does the same thing. Pings the same IP and everything.
Update: I have registered another domain and used the same host and it does the same thing. Pings the same IP and everything.
1 Nov 2008 at 22:04 #15 unknowndomain unknowndomain Soldato Joined 18 Apr 2004 Posts 2,613 Location London what browser are you using?
1 Nov 2008 at 22:05 #16 Pilky01 Pilky01 Soldato OP Joined 3 Jun 2008 Posts 5,060 Google Chrome but i have tried with FF2 an and IE
2 Nov 2008 at 10:58 #17 Pilky01 Pilky01 Soldato OP Joined 3 Jun 2008 Posts 5,060 All sorted now thanks guys.
2 Nov 2008 at 13:04 #18 suarve suarve Soldato Joined 8 Oct 2005 Posts 4,184 Location Midlands, UK Pilky01 said: All sorted now thanks guys. Click to expand... what was it in the end?