bind9 slave server.

[SamTzu]

I'm testing a secondary dns built with this howto slave server setup but I ran in to interesting problem.

I can lookup all the domains when I'm on ns2 using this command

dig @ns2 example.com.

That works fine. How ever I cant lookup anything from any other host.

Why would bind9 only answer from localhost?

[SamTzu]

Let me rephrase that.
How can I change "named" to listen on 0.0.0.0?

Now it's only listening on these ports...

tcp 0 0 10.10.103.126:53 0.0.0.0:* LISTEN 16905/named
tcp 0 0 127.0.0.2:53 0.0.0.0:* LISTEN 16905/named
tcp 0 0 127.0.0.1:53 0.0.0.0:* LISTEN 16905/named
tcp 0 0 127.0.0.1:953 0.0.0.0:* LISTEN 16905/named
tcp6 0 0 :::53 :::* LISTEN 16905/named
tcp6 0 0 ::1:953 :::* LISTEN 16905/named

[SamTzu]

The how to link was wrong.
It's this...
http://www.howtoforge.com/installing...th-ispconfig-3

[SamTzu]

I figured it out.
It was OpenVZ virtualization that was the problem.
I had to create a veth network device interface before I could get Bind to listen properly.

[SamTzu]

I have a question.
If I were to implement this on a new DNS slave server, should I manually copy the dns_* related database tables first?
So that all the records on the dns_ tables are identical on all the DNS servers?