Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

Everyone can access my site except my family

dns network

  • Please log in to reply

#1
Baconfan

Baconfan

    New Member

  • Member
  • Pip
  • 3 posts

I've been able to access my website fine for over a year now.

 

But I've tried to get onto it this week and it won't load. No computers using my house wifi can load it but I can load it fine using my phone's data. My friends can load it fine on their wifi.

 

I'm a total noob at this stuff but I've read it's a DNS issue. I've tried flushing it in Terminal (I'm on a Mac) and changing my DNS to the public Google one but these haven't worked. I don't know if I've done something incorrectly or what. 

 

When I try to load the site, the message says:

 

This site can’t be reached

lgibbs.net took too long to respond.

ERR_CONNECTION_TIMED_OUT

 


Edited by Baconfan, 06 August 2016 - 02:18 AM.

  • 0

Advertisements


#2
RKinner

RKinner

    Malware Expert

  • Expert
  • 17,331 posts
  • MVP

lgibbs.net works for me.  The error you see is not what I would expect from a DNS error.  

 

Run a speedtest:

 

Go to http://www.speedtest.net/and click on Begin Test
 
When the Test finishes click on Share This Result and then select Forum then Copy then move to a Reply and paste it in.  Does it look like you are getting what you pay for?  Some device on your network may be clogging the connection so shutdown or disconnect any other devices and try again.
 
I don't really speak Apple but apparently you can run a traceroute from the Terminal:
 
Type:
 
traceroute  lgibbs.net

and hit Enter.

 

This should show you what is happening.  If you can, copy and paste the result into a Reply.

 

This is what I get on a PC:

 

Tracing route to lgibbs.net [207.58.182.138]
over a maximum of 30 hops:
 
  1    <1 ms    <1 ms    <1 ms  192.168.0.1  <== This is your router.
  2     8 ms     8 ms     9 ms  96.120.12.37   <==This is the first connection to your ISP
  3     8 ms     8 ms     8 ms  xe-11-1-0-sur01.granby.co.denver.comcast.net [68
.85.221.41]
  4    10 ms    10 ms    10 ms  ae-38-ar01.denver.co.denver.comcast.net [68.86.1
03.5]
  5    11 ms    11 ms    11 ms  be-33652-cr01.1601milehigh.co.ibone.comcast.net
[68.86.92.121]
  6    12 ms    11 ms    12 ms  be-11719-cr02.denver.co.ibone.comcast.net [68.86
.86.77]
  7    11 ms    11 ms    11 ms  hu-0-10-0-6-pe02.910fifteenth.co.ibone.comcast.n
et [68.86.83.14]
  8    11 ms    11 ms    10 ms  173.167.57.142  <==This is still my ISP ( Comcast) internal routing.
  9    30 ms    32 ms    28 ms  kanc-b1-link.telia.net [62.115.120.71]  <== Here Comcast hands it off to someone else probably in Kansas City
 10    35 ms    36 ms    36 ms  chi-b21-link.telia.net [62.115.116.153] 
 11    61 ms    63 ms    61 ms  ash-bb4-link.telia.net [62.115.113.36]
 12    62 ms    62 ms    62 ms  ash-b1-link.telia.net [213.155.130.59]
 13    62 ms    62 ms    64 ms  giglinx-ic-308514-ash-b1.c.telia.net [62.115.40.218]
 14   213 ms    86 ms   298 ms  209.50.254.9.servint.net [209.50.254.9] <== This is near Alexandria VA. servint is the ISP handling your website's server Note the high ping times.  May mean congestion into the router.
 15    63 ms    63 ms    63 ms  209.50.254.6.servint.net [209.50.254.6]
 16    62 ms    62 ms    64 ms  sc-clm3872.servint.net [209.50.240.170]
 17    61 ms    61 ms    62 ms  srv.xiaoxiwan.com [207.58.182.138]  <== Made it to the server handling your website in Reston VA
 
Trace complete.

 

 

 
The first numbered steps are going to be different but some of the last steps should probably be the same.  If you get 3 *'s instead of 3 ms's then that's priobably where your problem is.
 
If the IP address it gives for your site is not:   [207.58.182.138] then yes it is a DNS problem.

 

To check your DNS from the Terminal, type;
 

nslookup  lgibbs.net

and hit Enter.

 

On a PC it looks like this:

 

Server:  cdns01.comcast.net
Address:  75.75.75.75 <==Should be 8.8.8.8 if using google's DNS
 
Non-authoritative answer:
Name:    lgibbs.net
Address:  207.58.182.138  <==Do you get this IP?

  • 0

#3
Baconfan

Baconfan

    New Member

  • Topic Starter
  • Member
  • Pip
  • 3 posts


 

lgibbs.net works for me.  The error you see is not what I would expect from a DNS error.  

 

*info*

 

Ok so I did these and here are my results:

 

SPEEDTEST:

 

(My internet has always been slow but it's never behaved like this so I suspect speed is not the issue. You know more than I, though!)

 

5533846013.png

 

TRACE:

 

Lauras-MacBook-Pro:~ lgibbs$ traceroute  lgibbs.net

traceroute to lgibbs.net (207.58.182.138), 64 hops max, 52 byte packets

 1  10.1.1.1 (10.1.1.1)  2.052 ms  1.200 ms  1.597 ms

 2  rdl804.ba.optusnet.com.au (198.142.130.30)  373.753 ms  277.216 ms  291.425 ms

 3  * * *

 4  * * *

 5  * * *

 6  * * *

 7  211.29.125.205 (211.29.125.205)  69.180 ms

    198.142.250.245 (198.142.250.245)  91.909 ms

    198.142.250.253 (198.142.250.253)  47.607 ms

 8  198.142.139.116 (198.142.139.116)  46.276 ms  46.468 ms  46.663 ms

 9  198.142.139.132 (198.142.139.132)  44.774 ms  46.424 ms  47.300 ms

10  tg0-1-0-3.ig11.optus.net.au (202.139.19.33)  46.396 ms  46.554 ms  46.302 ms

11  203.208.131.225 (203.208.131.225)  155.887 ms  154.540 ms  156.452 ms

12  63-218-211-253.static.pccwglobal.net (63.218.211.253)  343.220 ms  253.585 ms  254.964 ms

13  tenge12-4.br01.rst01.pccwbtn.net (63.223.45.14)  414.595 ms  335.029 ms  381.014 ms

14  tenge12-4.br01.rst01.pccwbtn.net (63.223.45.14)  352.780 ms  411.660 ms  309.869 ms

15  servint.tenge10-3.br01.rst01.pccwbtn.net (63.218.125.22)  461.260 ms  338.787 ms  377.737 ms

16  209.50.254.9.servint.net (209.50.254.9)  411.596 ms  562.783 ms  506.649 ms

17  209.50.254.6.servint.net (209.50.254.6)  411.245 ms  318.558 ms  350.471 ms

18  sc-clm3872.servint.net (209.50.240.170)  320.948 ms  362.402 ms  440.248 ms

19  * * *

20  * * *

21  * * *

22  * * *

23  * * *

24  * * *

25  * * *

26  * * *

27  * * *

28  * * *

29  * * *

30  * * *

31  * * *

32  * * *

33  * * *

34  * * *

35  * * *

36  * * *

37  * * *

38  * * *

39  * * *

40  * * *

41  * * *

42  * * *

43  * * *

44  * * *

45  * * *

46  * * *

47  * * *

48  * * *

49  * * *

50  * * *

51  * * *

52  * * *

53  * * *

54  * * *

55  * * *

56  * * *

57  * * *

58  * * *

59  * * *

60  * * *

61  * * *

62  * * *

63  * * *

64  * * *

Lauras-MacBook-Pro:~ lgibbs$ 

 

DNS LOOKUP:

 

lgibbs$ nslookup  lgibbs.net

Server: 8.8.8.8

Address: 8.8.8.8#53

 

Non-authoritative answer:

Name: lgibbs.net

Address: 207.58.182.138

 

Lauras-MacBook-Pro:~ lgibbs$ 


Edited by Baconfan, 06 August 2016 - 04:11 PM.

  • 0

#4
RKinner

RKinner

    Malware Expert

  • Expert
  • 17,331 posts
  • MVP

As i thought it's not a DNS issue.  If you look at my traceroute the last three steps are the same as yours:

 

16  209.50.254.9.servint.net (209.50.254.9)  411.596 ms  562.783 ms  506.649 ms

17  209.50.254.6.servint.net (209.50.254.6)  411.245 ms  318.558 ms  350.471 ms

18  sc-clm3872.servint.net (209.50.240.170)  320.948 ms  362.402 ms  440.248 ms

 

 

 

 

So the packet made it from Australia to Alexandria VA without a problem.  The next reply would have been from the server where your webpage lives but there is no reply.  We know that the Alexandria servers know how to get to your host server so for some reason the host server doesn't want or doesn't know how to reply to you.  I'm afraid there is something wrong at that end.  Can you contact the admin for the host server and ask for help?  Could be your originating IP address has gotten added to a blacklist by mistake.


  • 0

#5
Baconfan

Baconfan

    New Member

  • Topic Starter
  • Member
  • Pip
  • 3 posts

As i thought it's not a DNS issue.  If you look at my traceroute the last three steps are the same as yours:

 

16  209.50.254.9.servint.net (209.50.254.9)  411.596 ms  562.783 ms  506.649 ms

17  209.50.254.6.servint.net (209.50.254.6)  411.245 ms  318.558 ms  350.471 ms

18  sc-clm3872.servint.net (209.50.240.170)  320.948 ms  362.402 ms  440.248 ms

 

 

 

 

So the packet made it from Australia to Alexandria VA without a problem.  The next reply would have been from the server where your webpage lives but there is no reply.  We know that the Alexandria servers know how to get to your host server so for some reason the host server doesn't want or doesn't know how to reply to you.  I'm afraid there is something wrong at that end.  Can you contact the admin for the host server and ask for help?  Could be your originating IP address has gotten added to a blacklist by mistake.

 

Hm, weird. Thank you so much for your time and help with this! I'll have a chat with them. 


  • 0






Similar Topics


Also tagged with one or more of these keywords: dns, network

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP