Web Hosting Talk







View Full Version : Cannot add nameservers to BIND, strange error!


LMS MIS
09-08-2002, 08:38 PM
I am trying to configure bind but it doesn't seem to allow me to add the nameservers i was using. They are registered and propagated and have been for a month. Ensim tells me there are no valid A records. I checked via SSH and it appears the nameservers and domains are all listed with (A) Records when doing a dig ns1.domain.com domain.com

I went in Ensim, added 2 (A)ddress records under the main zone but it still will not successfully add the DNS servers as the Primary or secondary. Listed in Bind is "server.domain.com" when i understand i should be able to change that to ns1.domain.com and then create a secondary one as Virtual ns2.domain.com. Any ideas where i might be going wrong? It gives me the following error both times:

(PRIMARY EDIT)

An error has occured:
Traceback (innermost last):
File /usr/lib/python2.1/site-packages/ZPublisher/Publish.py, line 171, in publish
File /usr/lib/python2.1/site-packages/ZPublisher/mapply.py, line 160, in mapply
(Object: manage_setprimaryserver)
File /usr/lib/python2.1/site-packages/ZPublisher/Publish.py, line 112, in call_object
(Object: manage_setprimaryserver)
File /home/build/fcs/serverxchange/3.1.0/25/lwp/build25/WebGui/base/services/bind/bind.py, line 541, in manage_setprimaryserver
KeyError: servername

(SECONDARY)
An error has occured:
Traceback (innermost last):
File /usr/lib/python2.1/site-packages/ZPublisher/Publish.py, line 171, in publish
File /usr/lib/python2.1/site-packages/ZPublisher/mapply.py, line 160, in mapply
(Object: manage_setsecondary)
File /usr/lib/python2.1/site-packages/ZPublisher/Publish.py, line 112, in call_object
(Object: manage_setsecondary)
File /home/build/fcs/serverxchange/3.1.0/25/lwp/build25/WebGui/base/services/bind/bind.py, line 620, in manage_setsecondary
KeyError: secondary

RH4U
09-09-2002, 07:51 AM
What did you set for the Host Name and A names??

LMS MIS
09-09-2002, 06:25 PM
the problem is fixed now

it was all due to timeouts on FDC's side
they said they were getting attacked this weekend.

everything went through fine this time around