+- ispCP - Board - Support (http://www.isp-control.net/forum)
+-- Forum: ispCP Omega Support Area (/forum-30.html)
+--- Forum: System Setup & Installation (/forum-32.html)
+--- Thread: Secondary DNS (/thread-4257.html)
Secondary DNS - NiCiuS - 09-13-2008 05:54 AM
Hi,
I want to use secondary DNS im another server which doesn´t have ispcp. Im following this howto http://www.isp-control.net/documentation/frequently_asked_questions/how_do_i_configure_my_other_nameserver?s=secondary%20dns but i dont know where it says:
ispCP server
Edit your site config file and add this:
Alias /named /etc/bind
<directory /etc/bind>
Order Deny,Allow
Deny from all
Allow from [YOUR.NS2.IP]
</directory>
Which site config file it refers?
thanX!
NcS
RE: Secondary DNS - joximu - 09-13-2008 06:01 AM
The apache config for the site where the named.conf (from ns1) is being downloaded by ns2 (so - the vhost part on the ispcp-server)
/J
RE: Secondary DNS - NiCiuS - 09-16-2008 04:33 AM
Sorry, but I still don´t know which file I have to edit. It´s the vhost of the main domain?
ThanX again!
NcS
RE: Secondary DNS - joximu - 09-16-2008 08:26 PM
you can add it to the main domain but you also can add it to a vhost part...
The idea is that ns2 can download a file from ns1 (ispsp) and the part above is the security setting for this.
If you want to use a virtual domain for this transaction (ns1->ns2) you put it in a vhost part otherwise in the main server part...
Hope you see the point - it's up to you :-)
/J
RE: Secondary DNS - NiCiuS - 09-18-2008 12:33 PM
Well, the script works fine!
But bind9 doesn´t start after the sincro
When I exec the script:
gs1:~# sh dnsupdate.sh
Checking for new named.conf... done.
Generating zone names... done. (/tmp/zones.txt) Generating zone info...
New zone available (127.in-addr.arpa)... added.
Restarting Bind
Stopping domain name service...: bindrndc: connect failed:
127.0.0.1#953: connection refused
failed!
Starting domain name service...: bind failed!
New zone available (0.in-addr.arpa)... added.
Restarting Bind
Stopping domain name service...: bindrndc: connect failed:
127.0.0.1#953: connection refused
failed!
Starting domain name service...: bind failed!
New zone available (255.in-addr.arpa)... added.
Restarting Bind
Stopping domain name service...: bindrndc: connect failed:
127.0.0.1#953: connection refused
failed!
Starting domain name service...: bind failed!
New zone available (zone)... added.
Restarting Bind
Stopping domain name service...: bindrndc: connect failed:
127.0.0.1#953: connection refused
failed!
Starting domain name service...: bind failed!
New zone available (zone)... added.
Restarting Bind
Stopping domain name service...: bindrndc: connect failed:
127.0.0.1#953: connection refused
failed!
Starting domain name service...: bind failed!
New zone available (MYFIRSTDOMAIN.TLD)... added.
Restarting Bind
Stopping domain name service...: bindrndc: connect failed:
127.0.0.1#953: connection refused
failed!
Starting domain name service...: bind failed!
New zone available (MYOTHERDOMAIN.TLD)... added.
Restarting Bind
Stopping domain name service...: bindrndc: connect failed:
127.0.0.1#953: connection refused
failed!
Starting domain name service...: bind failed!
and in logs I have this:
Sep 17 22:36:19 gs1 named[10810]: starting BIND 9.3.4-P1.1 -u bind Sep 17 22:36:19 gs1 named[10810]: found 4 CPUs, using 4 worker threads Sep 17 22:36:19 gs1 named[10810]: loading configuration from '/etc/bind/named.conf'
Sep 17 22:36:19 gs1 named[10810]: /etc/bind/named.conf.local:9: zone
'127.in-addr.arpa': already exists previous definition:
/etc/bind/named.conf:25
Sep 17 22:36:19 gs1 named[10810]: /etc/bind/named.conf.local:15: zone
'0.in-addr.arpa': already exists previous definition:
/etc/bind/named.conf:30
Sep 17 22:36:19 gs1 named[10810]: /etc/bind/named.conf.local:21: zone
'255.in-addr.arpa': already exists previous definition:
/etc/bind/named.conf:35
Sep 17 22:36:19 gs1 named[10810]: /etc/bind/named.conf.local:33: zone
'zone': already exists previous definition: /etc/bind/named.conf.local:27 Sep 17 22:36:19 gs1 named[10810]: loading configuration: failure Sep 17 22:36:19 gs1 named[10810]: exiting (due to fatal error)
So, bind 9 doesn´t start. Do you know which could be the problem?
(i saw something like that in the forum but is in german
)ThanX a lot aGain!
NCS.
RE: Secondary DNS - momo - 09-19-2008 07:05 AM
Hi NCS,
I had an issue with bind9 once, but can't remember what it was
Only thing is that I couldn't reload it.
My notes says to do this...maybe you can try...
comment this line in /etc/bind/named.conf
Code:
#include "/etc/bind/vhcs.conf";RE: Secondary DNS - bpratt - 11-16-2008 02:05 PM
I'm having some issues setting this up on my Debian Etch system
When I add in the key and server lines in to my named.conf file, bind9 won't restart and complains about both 'key' and 'server' being unknown options.
I've done a apt-get update followed by a apt-get install bind9, and it says I have the up to date version of bind9
I updated to the most current RC6 of ISPCP about 3 weeks or so after RC6 was released.
Where have I gone wrong ??
