In alt.primenet.recovery Jim Thompson said:
http://www.analog-innovations.com
and report back what error message you get.
[...]
The problem appears to be with your DNS. Whois at godaddy.com reveals
your two authoritative DNS servers are:
NS.ADTSOFT.COM
NS.BREAKINGNEWSNETWORK.COM
The first one doesn't respond to DNS queries for your domain. The second
reports no domain found. Methinks only the first DNS server ever actually
had your DNS entries (or perhaps it was the primary while the other was
secondary) and now that the first DNS server is hosed, your domain
effectively does not exist.
If you knew the IP address of your website, you could always try putting
that into your web browser to see if the hosting site is still up. Keep
in mind that shared hosting often uses the same IP address for multiple
domains and only sorts which domain to show you by the domain name in the
URL. You could get around that little problem by temporarily putting the
IP address of your hosting server into your HOSTS[1] file and then trying
to pull up your website in a browser.
[1] In Win9x, the HOSTS file is in the \WINDOWS directory, for NT/2K/XP,
it's in the \WINNT\SYSTEM32\DRIVERS\ETC folder. In any *NIX it's in /etc.
--Paul
** Note "removemunged" in email address and remove to reply. **