Topic: Can ping IP not www

[steve288]

I use the SME in servergateway mode.

I came back from lunch and now I cannot browse the net on my windows machines.

If I log on the terminal I cannot ping www.yahoo.com

But if I ping the IP eg.
M:\>ping www.yahoo.com

Pinging any-fp.wa1.b.yahoo.com [67.195.160.76] with 32 bytes of d

Reply from 67.195.160.76: bytes=32 time=33ms TTL=50
Reply from 67.195.160.76: bytes=32 time=32ms TTL=50
Reply from 67.195.160.76: bytes=32 time=31ms TTL=50
Reply from 67.195.160.76: bytes=32 time=32ms TTL=50

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

The dns server in the configuration is the machine its self. eg 10.1.0.17.

I asume this is a dns issue but Im not sure where to look to find an answer.
Does anyone have any ideas?
Thanks.

[cactus]

Did you already try running the connection test when logged in as admin on your server from the menu?

The dns server in the configuration is the machine its self. eg 10.1.0.17.

Do you mean that you configured SME Server to use a DNS Server and that you pointed that to the servers IP address? If so, that is not needed, SME Server does not need a DNS server to resolve names, there is certainly no need to configure SME Server's DNS to point to it self.

[steve288]

Hello,

Yes I tried that. Admin / Test your internet connection / failed.

I set this thing up sometime ago its hard to remember, but When I look in the Server-manager and then look at the Review configuration/Server Names/DNS server/ it says 10.1.0.17
However in the terminal window when you login as / Admin  and get the Configure gui. The "Corporate DNS Server address" screen is indeed blank. As I believe they recomend.

I have run these tests, not sure what the right response?

/root/bin#/etc/init.d/tinydns status
run: /service/tinydns: (pid 4208) 5997s, normally down; run: log: (pid 3034) 6013s

/root/bin#/etc/init.d/dnscache status
run: /service/dnscache: (pid 4107) 6021s, normally down; run: log: (pid 3015) 6037s

When I run this it runs fine. I get a web site.
#lynx 69.147.125.65

But when I run #lynx www.yahoo.com

Looking up www.yahoo.com first
Looking up www.yahoo.com.com, guessing...
Looking up www.yahoo.com.edu, guessing...
Looking up www.yahoo.com.net, guessing...
Looking up www.yahoo.com.org, guessing...
Can't Access `file://localhost/root/bin/www.yahoo.com'
Alert!: Unable to access document.

lynx: Can't access startfile

Anythoughts

[cactus]

You have a issue here:

Yes I tried that. Admin / Test your internet connection / failed.

This seems to indicate that there is something wrong with the configuration of your server. You should investigate and find out.

I set this thing up sometime ago its hard to remember, but When I look in the Server-manager and then look at the Review configuration/Server Names/DNS server/ it says 10.1.0.17
However in the terminal window when you login as / Admin  and get the Configure gui. The "Corporate DNS Server address" screen is indeed blank. As I believe they recomend.

My guess is that you have unsaved changes waiting to be applied in that case. Did you finish the wizard to the end and apply the changes?

I have run these tests, not sure what the right response?

/root/bin#/etc/init.d/tinydns status
run: /service/tinydns: (pid 4208) 5997s, normally down; run: log: (pid 3034) 6013s

/root/bin#/etc/init.d/dnscache status
run: /service/dnscache: (pid 4107) 6021s, normally down; run: log: (pid 3015) 6037s

This is fine, services are up and running for some time (100h+)

When I run this it runs fine. I get a web site.
#lynx 69.147.125.65

But when I run #lynx www.yahoo.com

Looking up www.yahoo.com first
Looking up www.yahoo.com.com, guessing...
Looking up www.yahoo.com.edu, guessing...
Looking up www.yahoo.com.net, guessing...
Looking up www.yahoo.com.org, guessing...
Can't Access `file://localhost/root/bin/www.yahoo.com'
Alert!: Unable to access document.

lynx: Can't access startfile

That points to a DNS issue since hostname based things do not seem to work, but by IP they do.

What is the output of the following command:

Code: [Select]

db configuration show dnscache
db configuration show dnscache.forwarder
Is there anything you might have modified on the system recently before this behavior started occuring?

[steve288]

From the web gui I did a reconfigure / reboot.
Still no ping www.yahoo.com

/root#db configuration show dnscache
dnscache=service
    TCPPort=53
    UDPPort=53
    access=private
    status=enabled

/root#db configuration show dnscache.forwarder
dnscache.forwarder=service
    status=enabled

Yes I installed SARG, which worked well listing web sites visited. I have now uninstalled it to see if it makes a change. But it did NOT.

Ps I should say I installed it yesterday and it worked w/out any problems. It seems odd that it worked well yesterday and today then suddely started blocking addresses ?? (if its the culpret).

[cactus]

From the web gui I did a reconfigure / reboot.

That is not what I was referring to. I meant the reconfigure option in the admin console. Is there a message there are unsaved changes? Did you complete the menu sequence to the end?

[CharlieBrady]

Check whether your disk is full. A full disk will stop dnscache from resolving (because it blocks when trying to log).

[steve288]

Charlie ... I think you have hit on something !!
I did a
/tmp#df -h -T
Filesystem    Type    Size  Used Avail Use% Mounted on
/dev/mapper/main-root
              ext3     72G   72G     0 100% /
/dev/md1      ext3     99M   45M   49M  48% /boot
none         tmpfs    760M     0  760M   0% /dev/shm

I think this means the disk is full, IM not sure now how to diagnose this ?? now ?

[steve288]

Problem solved !!!!

I had created find that sent the output to a file. Im not sure why it grew so big. It should not have since it was looking for an obscure string. I have to look at the find command I used but basically it filled the disk in one file. Once I deleted the file. And presto I can now ping www.google.com or what ever.

Thanks a bunch both of you for helping me out. Lesson learned, if everything works and then it stops pinging web addresses first check disk.
Thanks.

[CharlieBrady]

Lesson learned, if everything works and then it stops pinging web addresses first check disk.

I think this is an indication of just how reliable dnscache is.

[steve288]

Indeed the whole system.
Thanks