Koozali.org: home of the SME Server

Obsolete Releases => SME Server 7.x => Topic started by: pabbec on July 13, 2007, 01:21:26 AM

Title: DNS problem
Post by: pabbec on July 13, 2007, 01:21:26 AM
Hi.

I have some problems with some web sites that are loading very slowly.    I thinking that my ISP was filtering content. But I make a traceroute and have this results:

Code: [Select]

[root@server ~]# traceroute -n divx.com
traceroute to divx.com (8.4.80.20), 30 hops max, 38 byte packets
 1  * * *
 2  * * *
 3  * * *
 4  * * *
 5  200.51.217.249  46.623 ms  79.825 ms  88.293 ms
 6  213.140.43.69  208.522 ms  96.704 ms  159.802 ms
 7  213.140.43.158  172.669 ms 213.140.38.70  189.460 ms 84.16.12.193  175.813 m
s
 8  213.140.36.89  178.110 ms 213.140.43.198  195.417 ms 213.140.36.89  189.166
ms
 9  213.140.36.37  280.944 ms  248.415 ms  187.250 ms
10  4.71.122.5  233.769 ms  189.391 ms *
11  4.68.122.1  259.793 ms 4.68.122.65  220.857 ms 4.68.122.129  190.644 ms
12  64.159.1.137  298.445 ms * 4.68.128.149  287.253 ms
13  4.68.113.38  271.331 ms  235.565 ms  234.990 ms
14  209.245.56.22  247.016 ms !X *  275.112 ms !X
[/code]

This means that my server has problems?

Best Regards,

Pablo
[/code]
Title: Re: DNS problem
Post by: raem on July 13, 2007, 04:10:01 AM
pabbec

Just guessing, did you set an external DNS server ?
In most cases it's better to set the sme server as DNS server (faster).
Title: Hi Ray
Post by: pabbec on July 13, 2007, 04:18:24 AM
How I can know this? My SME is working with the default configuration.

I must to clarify that I when execute traceroute, the "* * * *" in the first steps of trace, delay some 30 seconds aprox. Is too much.
Title: Re: Hi Ray
Post by: raem on July 13, 2007, 04:31:33 AM
pabbec

>How I can know this?

Server manager Review configuration Server names DNS = local IP ??
It should.
Title: Re: Hi Ray
Post by: pabbec on July 13, 2007, 04:54:38 AM
Quote from: "RayMitchell"
pabbec

>How I can know this?

Server manager Review configuration Server names DNS = local IP ??
It should.


Yes. DNS server   = 192.168.1.1
Title: DNS problem
Post by: mmccarn on July 14, 2007, 02:18:34 PM
Quote from: "pabbec"
traceroute -n divx.com

The "-n" option for traceroute instructs traceroute to print only the IP address of each node on the route, and specifically not to do any DNS lookups, so your issue is clearly unrelated to DNS.

Do you have any sort of redundancy or load balancing on your internet connection?  I was told years ago by someone who knows way more than me about networking that a redundant or load-balanced internet connection will always return '* * *' in traceroute if the returning packets are using a different route than the outgoing packets.