Koozali.org: home of the SME Server

Contribs.org Forums => General Discussion => Topic started by: hairytea on August 16, 2006, 05:17:43 PM

Title: SME Server 6 pointing to incorrect DNS server
Post by: hairytea on August 16, 2006, 05:17:43 PM
Hi all,

FYI.
I am logging into my server via a web browser using the servers local address (192.168.1.1/server-manager etc.)!

My problem is we are being blocked from several websites or should i say cannot access them.

After discussions with my ISP and several ipconfig a/ll and ping tests to certain addresses, it appears that our server is pointing us to our ISP's OLD DNS addresses.

I can't for the life of me find any settings anywhere in the server to update this or manually configure the DNS address that the server is pointing to.

I also have putty and can log in as root so if anyone knows a way to accomplish this using this method them please please let me know.

Many thanks in advance
Title: SME Server 6 pointing to incorrect DNS server
Post by: hairytea on August 16, 2006, 05:23:23 PM
Forgot to mention.....

In the SME Servers (Review Configuration) page i see that the DNS server address is that of the server itself (192.168.1.1)!???!????

If i manually enter my ISP's DNS addresses into my local machines on the network (manually configured IP addresses (within range) and DNS servers), then i get very strange results......

IE6 wont connect to any sites whatsoever but other applications connect ok i.e. skype internet phone, msn messenger and many other applications connect and work as normal?

i am very very confused now!
Title: SME Server 6 pointing to incorrect DNS server
Post by: raem on August 17, 2006, 01:11:23 PM
hairytea

> In the SME Servers (Review Configuration) page i see that the DNS
> server address is that of the server itself (192.168.1.1)!???!????

That is usually correct for most people.


> If i manually enter my ISP's DNS addresses into my local machines...

You should configure them for auto detect or manually use the same IP as above ie your server.


There was a problem with DNS resolution that was fixed long ago, have you applied all updates for sme6.x eg
e-smith-dnscache-0.3.0-04.noarch.rpm
which has also since been updated to
e-smith-dnscache-0.3.0-04sme02

see
http://forums.contribs.org/index.php?topic=27117.msg119493#msg119493

do
yum update
/sbin/e-smith/signal-event post-upgrade
/sbin/e-smith/signal-event reboot