title: Why I get a SOA dig response?
body: <p>Some time ago I setup a site with some subdomains (<code>example.com</code>, <code>test.example.com</code>...)</p>
  
  <p>Last week I added a new subdomain <code>new.example.com</code> and today I've realize that when I dig to the secondary server I get the SOA record as a response, not the answer itself:</p>
  
  <pre><code>root@Nigeria:~$ dig new.example.com @ns.kimsufi.com
  
  ; &lt;&lt;&gt;&gt; DiG 9.8.4-rpz2+rl005.12-P1 &lt;&lt;&gt;&gt; new.example.com @ns.kimsufi.com
  ;; global options: +cmd
  ;; Got answer:
  ;; -&gt;&gt;HEADER&lt;&lt;- opcode: QUERY, status: NXDOMAIN, id: 11559
  ;; flags: qr aa rd; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
  ;; WARNING: recursion requested but not available
  
  ;; QUESTION SECTION:
  ;new.example.com.       IN  A
  
  ;; AUTHORITY SECTION:
  example.com.        86400   IN  SOA ns345678.ip-93-122-113.eu. info.test.com. 2015021005 28800 7200 604800 86400
  
  ;; Query time: 36 msec
  ;; SERVER: 213.186.33.199#53(213.186.33.199)
  ;; WHEN: Mon Feb 16 11:14:35 2015
  ;; MSG SIZE  rcvd: 108
  </code></pre>
  
  <p>I'm wondering why I'm getting an authority response instead of the right response. If I dig into 'ns345678.ip-93-122-113.eu' which is the right server where my website and my DNS server is hosted, I get the expected response:</p>
  
  <pre><code>;; ANSWER SECTION:
  new.example.com.    86400   IN  A   93.122.113.255
  </code></pre>
  
  <p>Why the secondary DNS is not giving an answer to the <code>new</code> subdomain? It is giving an answer to old subdomains like 'test.example.com'. And how I must interpret the SOA response? What does it mean?</p>