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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
