title: Dig answer status: REFUSED from secondary server, primary is fine
body: <p>I have 2 debian 7 VPS both running a few services, with ISPConfig running on one of them to manage both.</p>
  
  <p>If I log into my primary server (ns1.example.com) and I do:</p>
  
  <pre><code>DiG @ns1.example.com any example.com
  DiG @ns2.example.com any example.com
  </code></pre>
  
  <p>ns1 responds fine with all of my records, but NS2 does not:</p>
  
  <pre><code>; &lt;&lt;&gt;&gt; DiG 9.8.4-rpz2+rl005.12-P1 &lt;&lt;&gt;&gt; @ns2.example.com any example.com
  ; (1 server found)
  ;; global options: +cmd
  ;; Got answer:
  ;; -&gt;&gt;HEADER&lt;&lt;- opcode: QUERY, status: REFUSED, id: 45647
  ;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
  ;; WARNING: recursion requested but not available
  </code></pre>
  
  <p>However, if I log into my secondary server (ns2), and run the same 2 commands, both return the correct DNS records</p>
  
  <p>I am extremely new to BIND, so I'm struggling a bit with this, but I'm guessing it's just something to do with the network/bind config, as both servers look like they have all the records, ns2 just isn't passing them to other servers?</p>
  
  <p>edit: not sure if this would be better on serverfault now that i've posted it..</p>