www.majorgeeks.com - can anybody access it?

[#1]

I have a number of PC's on my home network - none of which can access www.majorgeeks.com.
However, on one of those PC's, I can connect to my companies VPN and the VPN client tunnels ALL traffic across the VPN. The internet pop for the VPN is in San Jose. On this PC, via the VPN to San Jose, I can access majorgeeks without problem - so why can't I access it via Plusnet? It doesn't seem to be a DNS problem because both VPN and non VPN PC's resolve to the same address: 208.101.7.150.
Thanks,
Creamola.

[#2]

No problems accessing it here.
You could try rebooting your router which is the only common thing between the PCs.

[#3]

I see it OK - using PlusNet's DNS I get:-
jeremy@HECTOR:~$ nslookup -all www.majorgeeks.com
Set options:
  novc                  nodebug        nod2
  search                recurse
  timeout = 0          retry = 3      port = 53
  querytype = A        class = IN
  srchlist =
Server:        212.159.13.49
Address:        212.159.13.49#53
Non-authoritative answer:
www.majorgeeks.com ;     canonical name = majorgeeks.com.
Name:  majorgeeks.com
Address: 208.101.7.150

[#4]

weird. I get this:
Server:  ptn-cdns02.plus.net
Address:  212.159.6.10
Name:    majorgeeks.com
Address:  208.101.7.150
Aliases:  www.majorgeeks.com
I need to have a look at the router then...
Thanks,
Creamola.

[#5]

Which is the same.
Jeremy is using is a linux tool not DOS so the output content will differ.

[#6]

I know.
Sorry, I meant it was weird that we both get the same results - yet I have no access.

[#7]

internal server error here as of 3:21pm

[#8]

Yip. majorgeeks would seem to be experiencing some difficulty.
Currently returning a 500 error with the default text of

Quote

Internal Server Error The server encountered an internal error or misconfiguration and was unable to complete your request. Please contact the server administrator, webmaster@majorgeeks.com and inform them of the time the error occurred, and anything you might have done that may have caused the error. More information about this error may be available in the server error log. Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.

[#9]

Seems to be back now.