Why can I use sql_bind as a secondary nameserver?
You can, but it will not write changed entries to the database. There were too many issues dealing with security and validity of the SQL database to make writing to the database practical. • When I start the modified named daemon, it complains about “no SOA RRs found”. What’s wrong? As sql_bind uses the same mechanism to validate a domain as stock BIND does, you will need to have a SOA record per zone. • When I start the modified named daemon, it complains about “multiple SOA RRs found”. What’s wrong? You can only have on SOA record per zone. Did you run read_dnswalk twice? If so, then you have duplicates of every entry in your zone not just the SOA records. You need to clean out your database tables and rerun read_dnswalk. If you are porting sql_bind to a new database, make sure that your “select” statment in sql_load() is correct. If your database supports the use of parentheses in a where clause, please use them. • Do I still need both host and arpa entries? Yes. Sql_bind only chang
