Hey there - same thing has happened to me this week too!
That could be a symptom of DNS problem along with a good-intentioned
but non-standard service from your ISP when such a problem occurs.
E.g. check with nslookup if your DNS has a lookup for that sitename.
Note also that it may be an alias of its domain name which you would
also have to have a lookup for:
<nslookup>
Non-authoritative answer:
Name: digiscrapdesigner.com
Address: 70.86.28.230
Aliases:
www.digiscrapdesigner.com
</nslookup>
In addition you could use nslookup in its interactive mode with debug set
to see how this lookup is actually done by your DNS.
I am going crazy
trying to figure it out - I just need my fix of digiscrapdesigner forums and
tutorials! Please, please, if you managed to sort anything out - can you
help me?
Can you ping -n 1 both the sitename and its domain name?
It's just the lookups that you are interested in. Though, as it happens
both names do respond to the pings:
<cmd_output>
F:\>ping -n 1
www.digiscrapdesigner.com
Pinging digiscrapdesigner.com [70.86.28.230] with 32 bytes of data:
F:\>ping -n 1 digiscrapdesigner.com
Pinging digiscrapdesigner.com [70.86.28.230] with 32 bytes of data:
</cmd_output>
Then check with ipconfig /displaydns that you have an A (Host) record
cached for the domain name for its IP address:
<displaydns>
digiscrapdesigner.com
----------------------------------------
Record Name . . . . . : digiscrapdesigner.com
Record Type . . . . . : 1
Time To Live . . . . : 14016
Data Length . . . . . : 4
Section . . . . . . . : Answer
A (Host) Record . . . : 70.86.28.230
</displaydns>
If none of these lookups are working for you, you should notify your ISP
about the problem with their DNS and add a record to your HOSTS file
as a temporary workaround:
<HOSTS>
70.86.28.230
www.digiscrapdesigner.com
</HOSTS>
Good luck
Robert Aldwinckle
---
[quoted text clipped - 10 lines]