Hi,

I am facing a very irritating problem. I am running a pair of DNS on my Red Hat 6.2 box which i have hired at Catalog. Italso runs Plesk.

The problem i face is quite irritating.

Sometime my DNS server will just shutdown for no reason and thus all the sites on my server are down :(

This happens quite often. Sometime when i reach my office, I have a couple of calls waiting for me telling me this !

When i contacted the support team, they told me that it might be possible since at that time I was running two set of DNS servers on the same server. ns & ns2.webhostindia.com and also ns & ns2.talash.net

However on their advise i removed one pair of DNS servers.

But I still think that the problem exists. My IP is 209.217.52.194

Can anybody help me and let me know what could be the problem and what can be the solution.

Regards
Abhishek Rungta

First of all your primary and secondary dns should be on seperate boxes. You can host muliple Hostnames on the same box but primary and secondary servers should be on seperate boxes. Doesnt catalog.com provide free dns service??? IF all else fails, theres a couple of free dns services on the net you might look into.

Hi,

Lets say i have ns.webhostindia.com running on my box and now want the secondary nameserver hosted on catalog as ns2.webhostindia.com.

What shall i do. How do i replicate entries of my DNS ?

Can you suggest me some resources and some companies who can provide me secondary DNS ?

Regards
Abhishek Rungta

Even if this is done, why is it that the Dns server should shut down

We have a server @ rackspace where there are 3 pairs of dns running, and the dns server has never gone down till now over. The server is more than year old now.

But it does not have plesk. only webmin ,

By itself running many dns servers on the machine should not have shut it down, I also know a couple of other people who r doing the same.

You should be having primary and secondary on different servers is a different issue altogether.

Regards
Manish Kapadia

A small script to monitor the nameserver may do the trick:

Save the following as monitor_named.pl

#!/usr/bin/perl
unless(-e "/var/run/named.pid")
{ `/etc/rc.d/init.d/named start`; }
exit;

then just drop this file in:
/etc/cron-monitor Make the directory if needed.

Now add this line to /etc/crontab:

0,5,10,15,20,25,30,35,40,45,50,55 * * * * root run-parts /etc/cron-monitor

That should do it :D

BTW,

The following script will monitor the web server as well:

#!/usr/bin/perl


$IsRun = `/etc/rc.d/init.d/httpd status`;


unless ($IsRun =~ /is running/)

{
`/etc/rc.d/init.d/httpd start`;
}

exit;

Just save it and drop it in /etc/cron-monitor.

You can follow this example to monitor most services on your server.

Ooops, forgot - chmod the scripts 755 so they can execute.

Did you upgrade your name server? There was a big security problem a few month ago. At this time my server had the same problem as yours, I'm sure somebody had a script crashing my named all the time.

- domi

Hi mlovic,

Thanx a lot for your valuable suggestion. I will definitely put this script to work on my server.

Voodoo, the problem with the BIND upgrade is that my server runs Plesk, which installs bind itself and we have to depend upon Plesk.com to give us an upgrade. Otherwise it might just mess up the system :(

I am learning the flexibility and problems of a control panel. Nice experience though :) Learnt a lot after joining this forum.

Thanx everybody again !
Abhishek

Abhishek,

May 30, 2001. Plesk, Inc. has released a NEW PATCH for PSA version 1.3.1.

Did you update yours, It was quite recent so you may have missed out, just try and update yours if you havent and keep us posted if your problem gets solved.

Running that cron job is also a real good solution to the problem atleast for the time being till the updates fix up the dns.

Regards
Manish Kapadia