[KateLR]

Hi

 

I wasn't sure what area to put this in so please move if I am totally off the mark...

 

I have two issues that I have been trying to sort out for few days, I only found one issue due to investigating the other...one is a hosting issue the other is to do with running a tracert on my PC

 

The first /original issue is - I have a blog -  domain sunshineandpaintpots.com through blogger but with our domain hosted through GoDaddy.  Up until 6 days ago all was well and we had no issues.  Now we (and other readers) are experiencing intermittent outages with the blog.  It always comes back up, but not for a while sometimes down for ages/others for minutes.  When it is not working for me here in Australia it will work fine simultaneously in the USA or Canada for example.  We have had known issues from the Uk and Aus so far. 

 

Godaddy say it has to be Blogger, Blogger says it has to be Godaddy...?!  I would really like to work out why there are so many outages so that my readers and I can stop being so frustrated with having to keep coming back to try again.

 

The screen you get when it down is (i.e)

this page cant be displayed 

(chrome)

this page is not available

 

The second issue which may or may not be connected is that today I ran a tracert on my domain and it just comes back with - unable to resolve target system name.  If I do a random tracert for another domain it works fine.  Likewise if I get on another PC here in my home and run the tracert the sunshine domain doesn't work but others do.  Again if I get someone else (outside of this house ) to run the tracert for me for sunshine it works fine for them albeit a bit slow. 

 

Why would that be and who would be able to tell me why this would be happening/how to fix it.  I can use another web based system to run the pings etc and they are all fine, so it's more of a baffling 'I want to solve it' type query rather than I need it to be fixed.

 

I am not techie at all, so not sure where to start other than all I have done already...deleted cache, dns flush>?!, tried other browsers, called all three providers, blogger, ISP, godaddy etc

 

Any ideas?

Many thanks in advance, and sorry for my ignorance on where to put this/and title...

Kate

 

 

 

 

[Advertisements]

I don't think you can do anything about this since it is not your computer that is the cause of the problem (others experience it as well).
 
This has to be hashed out by GoDaddy and Blogger.
 
I just did a tracert and it was slow but completed:
 
>tracert sunshineandpaintpots.com

Tracing route to sunshineandpaintpots.com [216.239.38.21]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2    23 ms     8 ms    12 ms  10.52.32.1
  3    10 ms     7 ms     8 ms  ten0-0-0-7.orld03-ser1.bhn.net [72.31.195.32]
  4    18 ms    13 ms    10 ms  ten0-0-0-3.orld31-car2.bhn.net [72.31.188.150]
  5    16 ms    15 ms    15 ms  ten0-6-0-1.orld71-car2.bhn.net [97.69.194.146]
  6    16 ms    14 ms    23 ms  72-31-188-176.net.bhntampa.com [72.31.188.176]
  7    17 ms    14 ms    15 ms  10.bu-ether15.orldfljo00w-bcr00.tbone.rr.com [66.109.6.98]
  8    25 ms    33 ms    27 ms  bu-ether18.atlngamq47w-bcr01.tbone.rr.com [66.109.1.72]
  9    28 ms    22 ms    22 ms  bu-ether21.atlngamq46w-bcr00.tbone.rr.com [107.14.19.8]
 10    23 ms    23 ms    22 ms  ae-0-0.pr0.atl20.tbone.rr.com [66.109.6.171]
 11    23 ms    34 ms    29 ms  66.109.9.90
 12    24 ms    23 ms    31 ms  72.14.239.100
 13    23 ms    24 ms    24 ms  66.249.94.20
 14    24 ms    24 ms    24 ms  209.85.253.90
 15     *        *        *     Request timed out.
 16    25 ms    24 ms    24 ms  any-in-2615.1e100.net [216.239.38.21]

Trace complete.

 

nslookup and ping worked to the IP address too.

 

>nslookup 216.239.38.21
Server:  UnKnown
Address:  192.168.1.1

Name:    any-in-2615.1e100.net
Address:  216.239.38.21


>ping 216.239.38.21

Pinging 216.239.38.21 with 32 bytes of data:
Reply from 216.239.38.21: bytes=32 time=23ms TTL=39
Reply from 216.239.38.21: bytes=32 time=22ms TTL=39
Reply from 216.239.38.21: bytes=32 time=24ms TTL=39
Reply from 216.239.38.21: bytes=32 time=22ms TTL=39

Ping statistics for 216.239.38.21:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 22ms, Maximum = 24ms, Average = 22ms

[Ztruker]

I don't think you can do anything about this since it is not your computer that is the cause of the problem (others experience it as well).
 
This has to be hashed out by GoDaddy and Blogger.
 
I just did a tracert and it was slow but completed:
 
>tracert sunshineandpaintpots.com

Tracing route to sunshineandpaintpots.com [216.239.38.21]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2    23 ms     8 ms    12 ms  10.52.32.1
  3    10 ms     7 ms     8 ms  ten0-0-0-7.orld03-ser1.bhn.net [72.31.195.32]
  4    18 ms    13 ms    10 ms  ten0-0-0-3.orld31-car2.bhn.net [72.31.188.150]
  5    16 ms    15 ms    15 ms  ten0-6-0-1.orld71-car2.bhn.net [97.69.194.146]
  6    16 ms    14 ms    23 ms  72-31-188-176.net.bhntampa.com [72.31.188.176]
  7    17 ms    14 ms    15 ms  10.bu-ether15.orldfljo00w-bcr00.tbone.rr.com [66.109.6.98]
  8    25 ms    33 ms    27 ms  bu-ether18.atlngamq47w-bcr01.tbone.rr.com [66.109.1.72]
  9    28 ms    22 ms    22 ms  bu-ether21.atlngamq46w-bcr00.tbone.rr.com [107.14.19.8]
 10    23 ms    23 ms    22 ms  ae-0-0.pr0.atl20.tbone.rr.com [66.109.6.171]
 11    23 ms    34 ms    29 ms  66.109.9.90
 12    24 ms    23 ms    31 ms  72.14.239.100
 13    23 ms    24 ms    24 ms  66.249.94.20
 14    24 ms    24 ms    24 ms  209.85.253.90
 15     *        *        *     Request timed out.
 16    25 ms    24 ms    24 ms  any-in-2615.1e100.net [216.239.38.21]

Trace complete.

 

nslookup and ping worked to the IP address too.

 

>nslookup 216.239.38.21
Server:  UnKnown
Address:  192.168.1.1

Name:    any-in-2615.1e100.net
Address:  216.239.38.21


>ping 216.239.38.21

Pinging 216.239.38.21 with 32 bytes of data:
Reply from 216.239.38.21: bytes=32 time=23ms TTL=39
Reply from 216.239.38.21: bytes=32 time=22ms TTL=39
Reply from 216.239.38.21: bytes=32 time=24ms TTL=39
Reply from 216.239.38.21: bytes=32 time=22ms TTL=39

Ping statistics for 216.239.38.21:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 22ms, Maximum = 24ms, Average = 22ms

[donetao]

Hey Ztrucker!

WOT doesn't like your ping. It gave them a red life saver!!

Attached Thumbnails

• 
• 

Edited by donetao, 15 August 2014 - 09:46 PM.

[dsenette]

is anyone outside of your location having the problems or is it just you on your network connection that has the connectivity issues?

 

if it's just at your location (i.e. your house or office) can you tell us your DNS information? either open a command prompt (start, run, cmd) and type "ipconfig /all" and paste the results, or log in to your router's configuration page and look for a status page or something similar that lists the DNS servers the connection is using.

 

Ztrucker's NSLOOKUP (DNS check) only shows one address...if you check with google DNS there are 4