MrGoodHost
06-28-2001, 11:28 AM
I keep getting a error : ndc: connect: connection refused
at either the first line on a bind start or on the last line when creating a new account . Anybody else get this ? What does it mean ?
BTW its a new VO server
Darkedge
06-28-2001, 05:40 PM
Hello,
I kept getting that until I ran the Initial name server setup then that went away the error seems to be generated because the scripts try to setup dns no matter what....
JonnyQuags
06-28-2001, 10:12 PM
Just means dns in not running
Hi,
I've got same problem on my new server@burst.net.
I tried to setup new nameserver. Having setting
up the "Initial NameServer Setup" on WHM, after
adding new DNS Zone for my ns1, WHM always returns
ndc: connect: connection refused.
Yesterday, I placed a support ticket to burst but
haven't got reply yet. I know it is week end,
but since I need this to be solved soon,
is there anything I can do to fix the problem?
Or, is it only burst that can fix it?
Thanks.
Anto.
PS:
I also tried to start nameserver from shell (ndc restart&)
but it gives same error message.
MrGoodHost
07-08-2001, 09:48 PM
I get it everytime I make an dns entry , ie when I create a new account or edit a dns record . According to VO it just means the dns is not accessible and not to worry . I just restart bind and everything I have put in is there and working . My DNS servers have been working for several days and everything seems fine , just a goofy little quirk ?
MrGoodHost,
Thanks for your reply. I hope it is only a little quirk.
But the problem is, after I created a new DNS zone
(i.e. clicking on "Add a DNS Zone") the IP
I chose for the Name Server is not assigned when
I click "Show IP Address Usage" on WHM.
Actually, this is the second time I create
a nameserver on WHM. The first one (on
other server provider) was a breeze.
Can anyone help me?
Anto.