Bind needs restarting after every new account

alrock

Active Member
May 31, 2004
34
0
156
This is making me crazy.

Every time a new account is added, the domain appears like it is not resolving even though a check on DNS Stuff shows that it is configured with the correct nameservers and more than 48 hours have gone by.

The only thing that fixes it is to restart bind.

Has anyone else experienced this problem? Is there a fix for it?
 

3en

Active Member
May 21, 2004
31
0
156
Yeah, I have the same problem. Looking for a fix but can't find one.
 

haze

Well-Known Member
Dec 21, 2001
1,544
3
318
By any chance, are you guys are running RHEL3 Update4 ?
 

3en

Active Member
May 21, 2004
31
0
156
I'm running CentOS which is basicly RHEL. It's fixed now. Some one in IRC suggested to run /scripts/fixndc in ssh. Which I did and it fixed it. Very helpfull people in IRC.

Thanks for your help any way.
 

seahorse

Well-Known Member
Jul 3, 2003
49
0
156
the bind in my server also didnt restart everytime i create an account or make dns change using WMH/CPanel ?

I am using RH Enterprise 3.

WHM 9.9.9
cPanel 9.9.9-R14

do i also use /scripts/fixndc to fix?

Please advise
 
Last edited:

3en

Active Member
May 21, 2004
31
0
156
/scripts/fixndc normally does the trick. Don't know about your situation. I was running CentOS that basicly is RHEL but free becuase it's built from the rpm's.
 

seahorse

Well-Known Member
Jul 3, 2003
49
0
156
but will /scripts/fixndc permanently fix the problem.
ie, currently the bind wont restart everytime i add an account through WHM. I need to manually restart bind to make it work.

so after running /scripts/fixndc, next time when i create an account will i need to manually restart bind again?
 

alrock

Active Member
May 31, 2004
34
0
156
running fixndc did not fix it for me. Nor has anything else I have tried.
 

seahorse

Well-Known Member
Jul 3, 2003
49
0
156
what about upgrading the whm/cpanel ?

if /scripts/fixndc doesnt fix it.... i have no idea too.

anyone have any idea??
 

haze

Well-Known Member
Dec 21, 2001
1,544
3
318
alrock said:
running fixndc did not fix it for me. Nor has anything else I have tried.
What are your log files saying ?
 

philb

Well-Known Member
Jan 28, 2004
118
4
168
Problems like this are usually down to a problem with RNDC (the bind 'remote' control program) not being able to connect to bind.

/scripts/fixrndc will usually fix most of these issues.

If it still doesnt work, try running rndc reload and paste the error output into this thread into here so we can see what it's whinging about.
 

dhawton

Member
Mar 9, 2004
22
0
151
I tried /scripts/fixnamed and /scripts/fixndc

Error:
[[email protected]:/etc/namedb]# rndc reload
rndc: connect failed: connection refused

I think 2nd to last line is interesting, from /var/log/messages:
Jan 9 12:48:35 darkhelmet named[43896]: Ready to answer queries.
Jan 9 12:50:31 darkhelmet named[43975]: starting (/etc/namedb/named.conf). named 8.3.7-REL Sat Dec 25 00:55:02 CST 2004 [email protected]:/usr/obj/usr/src/usr.sbin/named
Jan 9 12:50:31 darkhelmet named[43975]: limit files set to fdlimit (1024)
Jan 9 12:50:31 darkhelmet named[43975]: /etc/namedb/named.conf:8: Ignoring BIND 9 inet control clause
Jan 9 12:50:31 darkhelmet named[43976]: Ready to answer queries.


O/S: FreeBSD
cPanel/WHM: WHM 9.9.8 cPanel 9.9.8-R118
 
Last edited:

philb

Well-Known Member
Jan 28, 2004
118
4
168
You're running Bind series 8.

You need to be running v9 for rndc to function, as version 8 of bind never had rndc.