We have a master DNS server that is running on windoze and it shuts down at least once a day. We want to make one of our SLES10 SP1 servers a backup/slave DNS so when the crappy primary DNS goes down, name resolution still works using the SLES10 SP1 DNS. So, i go into yast->DNS server and at the first screen i am asked about forwarders. I don't believe we are using forwarders on the primary so i did not enter any here. At the 2nd screen, add new zone, i enter in the same zone name as is in the primary DNS server (right?) and under type, make it "slave". Click add. Then i click next, firewall is disabled and start-up behaviour is on: start now and when booting. The box under that says forwarders: <blank> and domains:,localhost,0.0.127.in-addr.arpa, <domain name from primary DNS>. I click finish and encounter this error: error occurred when srating service named error: shutting down name server BIND- Warning named not running!. Done Starting name server BIND And the only clickable option is OK. I click OK and encounter another dialog box saying "saving the configuration failed. Change the settings? with "yes" and "no" as clickable options. I click yes and it takes me back to the initial setup of the DNS server. I click no and the config goes away. I start it back up (dns server in yast) and see that the dns server is not running. click on start dns server now and nothing happens. Named is running according to runlevel: Services. I don't see bind in that list. A rpm -qa bind says bind-9.3.4-1.16. All i want to do is configure a back-up or slave DNS. How do you do this? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Chris Arnold wrote:
We have a master DNS server that is running on windoze and it shuts down at least once a day. We want to make one of our SLES10 SP1 servers a backup/slave DNS so when the crappy primary DNS goes down, name resolution still works using the SLES10 SP1 DNS. So, i go into yast->DNS server and at the first screen i am asked about forwarders. I don't believe we are using forwarders on the primary so i did not enter any here. At the 2nd screen, add new zone, i enter in the same zone name as is in the primary DNS server (right?) and under type, make it "slave". Click add. Then i click next, firewall is disabled and start-up behaviour is on: start now and when booting. The box under that says forwarders: <blank> and domains:,localhost,0.0.127.in-addr.arpa, <domain name from primary DNS>. I click finish and encounter this error: error occurred when srating service named error: shutting down name server BIND- Warning named not running!. Done Starting name server BIND And the only clickable option is OK. I click OK and encounter another dialog box saying "saving the configuration failed. Change the settings? with "yes" and "no" as clickable options. I click yes and it takes me back to the initial setup of the DNS server. I click no and the config goes away. I start it back up (dns server in yast) and see that the dns server is not running. click on start dns server now and nothing happens. Named is running according to runlevel: Services. I don't see bind in that list. A rpm -qa bind says bind-9.3.4-1.16. All i want to do is configure a back-up or slave DNS. How do you do this?
We have a couple of internet facing sles boxes serving around 800 dns domains, so it's doable. The microsoft dns has gone down at random times, while the sles servers have never so much as hiccuped, and this has led management to point mission critical servers to sles dns rather than windows. Due to a legacy situation we have windows boxes as masters for simple domains, and a sles server as the master for complex domains (e.g. having different views), so we have a good combination of cases - forward, slave, and master. But we've never used yast to set it up, we've always edited the zone files and config files with vi, or managed it with webmin, so I can't say what the problem might be with yast. My suggestion is to get a copy of the O'Reilly book on bind and dns, and just set it up by hand, and also file a bug report with Novell on the yast dns setup tool. Joe -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Sloan wrote:
Due to a legacy situation we have windows boxes as masters for simple domains, and a sles server as the master for complex domains (e.g. having different views), so we have a good combination of cases - forward, slave, and master. But we've never used yast to set it up, we've always edited the zone files and config files with vi, or managed it with webmin, Hey Joe (as JMH would say) Care to share how you configured the slave DNS using the files? This should be really simply as the setup is simple in this environment. What files did you manage and what did you do to the files to configure them by hand? Thanks for any info -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Chris Arnold wrote:
Sloan wrote:
Due to a legacy situation we have windows boxes as masters for simple domains, and a sles server as the master for complex domains (e.g. having different views), so we have a good combination of cases - forward, slave, and master. But we've never used yast to set it up, we've always edited the zone files and config files with vi, or managed it with webmin,
Hey Joe (as JMH would say) Care to share how you configured the slave DNS using the files? This should be really simply as the setup is simple in this environment. What files did you manage and what did you do to the files to configure them by hand? Thanks for any info
OK a quick example, with an imaginary domain called "lexusespanol.com" - In named.conf add a stanza like this: zone "lexusespanol.com" { type slave; file "lexusespanol.com.db"; masters { 172.16.121.119; }; }; So we've specified the zone name (lexusespanol.com), the type (slave), the name of the file containing the dns data (lexusespanol.com.db) and the IP address of the master server from which we get the zone data (172.16.121.119). The server (172.16.121.119) must be configured to allow zone transfers with our dns slave server. Once these files are in place, and /var/lib/named is writeable by the user "named", restart named and the magic should happen. Look for the file to appear in /var/lib/named, and test the dns server to make sure it can answer requests for that domain. Joe -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Sloan wrote:
OK a quick example, with an imaginary domain called "lexusespanol.com" -
In named.conf add a stanza like this:
zone "lexusespanol.com" { type slave; file "lexusespanol.com.db"; masters { 172.16.121.119; }; };
So we've specified the zone name (lexusespanol.com), the type (slave), the name of the file containing the dns data (lexusespanol.com.db) and the IP address of the master server from which we get the zone data (172.16.121.119).
The server (172.16.121.119) must be configured to allow zone transfers with our dns slave server.
Once these files are in place, and /var/lib/named is writeable by the user "named", restart named and the magic should happen. Look for the file to appear in /var/lib/named, and test the dns server to make sure it can answer requests for that domain. Yea, thats the way i have it configured and it seems that named will not start. I get an error about ldap.xx.so shared libs. We have zimbra mail server installed on this same system and it appears, after a search through the zimbra forums, that it has something to do with zimbra. Zimbra appears to be a hog and not able to install anything after zimbra is installed....
Chris -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Chris Arnold wrote:
Sloan wrote:
OK a quick example, with an imaginary domain called "lexusespanol.com" -
In named.conf add a stanza like this:
zone "lexusespanol.com" { type slave; file "lexusespanol.com.db"; masters { 172.16.121.119; }; };
So we've specified the zone name (lexusespanol.com), the type (slave), the name of the file containing the dns data (lexusespanol.com.db) and the IP address of the master server from which we get the zone data (172.16.121.119).
The server (172.16.121.119) must be configured to allow zone transfers with our dns slave server.
Once these files are in place, and /var/lib/named is writeable by the user "named", restart named and the magic should happen. Look for the file to appear in /var/lib/named, and test the dns server to make sure it can answer requests for that domain.
Yea, thats the way i have it configured and it seems that named will not start. I get an error about ldap.xx.so shared libs. We have zimbra mail server installed on this same system and it appears, after a search through the zimbra forums, that it has something to do with zimbra. Zimbra appears to be a hog and not able to install anything after zimbra is installed....
Ah yes, we looked at zimbra too, and found that after installing it, ldap would not start, due to zimbra modifying the system-wide ld.so config to load the zimbra libs, which are apparently missing some symbols. Joe -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (2)
-
Chris Arnold -
Sloan