Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Now my delegation issues look resolved, but I am still having trouble with the root lookup (which I thought would be soooo easy.)</p> <p>I think the problem stems from the fact that when I <code>dig</code> from the itchy machine I get an authority record instead of an answer record. I'm just not sure what I did (or didn't) to cause that.</p> <p>If you "dig [no args]" from a machine using the typical hint file for the internet you get a block of answers for the root nameservers and the translation in the additional section.</p> <p>if I do that from the bogus machine (root and TLD nameserver) I get</p> <pre><code>;; QUESTION SECTION: ;. IN NS ;; ANSWER SECTION: . 3600 IN NS ns.bogustld. ;; ADDITIONAL SECTION: ns.bogustld. 3600 IN A 10.0.0.1 </code></pre> <p>If I do that from the itchy machine I get</p> <pre><code>;; QUESTION SECTION: ;. IN NS ;; AUTHORITY SECTION: . 3600000 IN NS ns.bogustld. ;; Query time: 0 msec </code></pre> <p>It get's more interesting if you try <code>dig +trace .</code></p> <h3>Internet box</h3> <pre><code>; &lt;&lt;&gt;&gt; DiG 9.5.0a6 &lt;&lt;&gt;&gt; +trace . ;; global options: printcmd . 3005 IN NS C.ROOT-SERVERS.NET. . 3005 IN NS D.ROOT-SERVERS.NET. . 3005 IN NS E.ROOT-SERVERS.NET. . 3005 IN NS F.ROOT-SERVERS.NET. . 3005 IN NS G.ROOT-SERVERS.NET. . 3005 IN NS H.ROOT-SERVERS.NET. . 3005 IN NS I.ROOT-SERVERS.NET. . 3005 IN NS J.ROOT-SERVERS.NET. . 3005 IN NS K.ROOT-SERVERS.NET. . 3005 IN NS L.ROOT-SERVERS.NET. . 3005 IN NS M.ROOT-SERVERS.NET. . 3005 IN NS A.ROOT-SERVERS.NET. . 3005 IN NS B.ROOT-SERVERS.NET. ;; Received 500 bytes from 64.105.172.26#53(64.105.172.26) in 19 ms . 86400 IN SOA a.root-servers.net. nstld.verisi gn-grs.com. 2008102201 1800 900 604800 86400 ;; Received 92 bytes from 128.63.2.53#53(H.ROOT-SERVERS.NET) in 84 ms </code></pre> <h3>My internal root box (Bogus)</h3> <pre><code>; &lt;&lt;&gt;&gt; DiG 9.5.0-P2 &lt;&lt;&gt;&gt; +trace . ;; global options: printcmd . 3600 IN NS ns.bogustld. ;; Received 57 bytes from 10.0.0.1#53(10.0.0.1) in 1 ms . 3600 IN NS ns.bogustld. ;; Received 72 bytes from 10.0.0.1#53(ns.bogustld) in 0 ms </code></pre> <h3>Itchy</h3> <pre><code>; &lt;&lt;&gt;&gt; DiG 9.5.0-P2 &lt;&lt;&gt;&gt; +trace . ;; global options: printcmd . 3600000 IN NS ns.bogustld. ;; Received 41 bytes from 10.0.0.2#53(10.0.0.2) in 0 ms dig: couldn't get address for 'ns.bogustld': failure </code></pre> <p>Why does my internet facing machine find a SOA, but none of my internal machines?</p>
    singulars
    1. This table or related slice is empty.
    1. POInternal DNS configuration woes
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USJT.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload