Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

DNS server Problem

Status
Not open for further replies.

cts123

Technical User
Feb 28, 2007
108
IN
Hi,

We have a DNS server which is running on Fedora Linux. Now a days we are facing a problem. We have a job which does namelookup of a server ftp.domain.com and does ftp. That job is critical job.

like it does, ftp ftp.domain.com and does mput of few set of files in a location.this job is now a days failing, because while doing ftp to ftp.domain.com, the ftp is not happening. We thought there is some issue with the FTP server, but found problem is somewhere else.

If I bounce "named" in the DNS server and run the job it runs successfully. Now a days this job failing twice a week. And I had to bounce the "named" process of that server.

I also got some reference on this topic before, by setting the recursive-clients value in named.conf file. I am not sure this didn't solve the purpose.

=====================================================
// generated by named-bootconf.pl

options {
directory "/var/named";
tcp-clients 3500;
recursive-clients 3500;

/*
/* If there is a firewall between you and nameservers you want
* to talk to, you might need to uncomment the query-source
* directive below. Previous versions of BIND always asked
* questions using port 53, but BIND 8.1 uses an unprivileged
* port by default.
*/
// query-source address * port 53;
};

=========================================================

Now a days I am manually bouncing the named service and have a plan to put in crontab to bounce the named twice or thrice a week. But this is not the solution and I want to know whats wrong and where.

TIA ..







 
Is there more than one ftp.domain.com??? You could simply define the target by IP address rather than by name, thus eliminating the need for DNS for this task.

You could also add a line in your crontab to bounce the named service nightly at a non-impact time for your key process:

05 01 * * * root service named restart

OR, if ftp.domain.com is publicly declared in a zone that can be read by other resolvers, then you could change your resolv.con to utilize another DNS resolver to find ftp.domain.com



D.E.R. Management - IT Project Management Consulting
 
Hi thedaver,

Thanks for your suggestion ..
At this time I believe I have to go for crontab entry...
I will let you know with this exercise.

-Tua
 
Hi,

I tried that option by setting the crontab today (13th),
but I can see the porcess is still holding the old PID .

[root@DNS001 log]# ps -ef | grep -i name
named 24259 1 0 Mar12 ? 00:03:41 /usr/sbin/named -u named -t /var/named/chroot
root 24989 24813 0 10:40 pts/1 00:00:00 grep -i name

Do I need to put the command in the crontab like ?

05 01 * * * /etc/rc.d/init.d/named restart


 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top