debian-sf-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Debian-sf-users] Debian Testing 2.5-15: project domain question


From: Christian BAYLE
Subject: Re: [Debian-sf-users] Debian Testing 2.5-15: project domain question
Date: Wed, 12 Dec 2001 21:29:04 +0100

Jean-Francois Leveque wrote:
> 
> Christian BAYLE wrote:
> >
> > Jean-Francois Leveque wrote:
> > >
> > > Is the "DNS Update" sourceforge cron entry responsible for the
> > > projects domain name update in the main sourceforge domain?
> > >
> > yes, it is
> >
> > > If it's responsible, do you know any reason for it not to do
> > > its hourly job corectly?
> > >
> > What do you mean by not corectly?
> > The table is not filled?
> 
> The table was not filled with the new domain name,
> but it did fine on the second hourly run.
> 
I think I know why, it's because there is a in dns_conf.pl a
 gethostbyname("$unix_box".".".$sys_default_domain );
that may not give right answer the first time you setup

I should look better what happens, 
A better solution would be to ask the DNS to look in a ldap table
updated at group creation.
This is or will be possible with the new bind version.
But I only did what I found in the original SF for this.

> > I encountered some problem with bind daemon
> > I was using at the beginning rndc to make the daemon reread the table,
> > but after some time it was not responding
> > It can be problem with the hourly restart of the daemon, but there is no
> > thing I could reproduce systematicly
> > Maybe you can try a stop-pause-start procedure modifying the cron
> > command.
> > It seems to be very dependant on the daemon version
> 
> I did a kill -SIGHUP on the /var/run/named.pid and it did fine
> with bind 9. Maybe it's a little hard, but I think it will work
> with other versions. I suggest that you use it in the next release of
> 2.6,
> and maybe update it in next release of 2.5 if possible.
> 
Normaly this should be done by rndc, it works, but after an
undeterminate time
bind stops to answer, even if the process don't crash
I'm not sure that SIGHUP has not the same effect after some time.
And it's really boring to see your subdomain deseapear from the DNS

I didn't make search about the problem, and don't know if it's known,
solve, or whatever
If you have some time for this let me know what you find.

Christian


-- 
Christian Bayle 
================================================================================
E-mail: address@hidden, address@hidden
P-mail: 28, Chemin du Vieux Chene BP 98 38243 MEYLAN CEDEX
Telephone/Phone : (33) 4 76 76 41 01     Piece/Room A156



reply via email to

[Prev in Thread] Current Thread [Next in Thread]