install.sh

@@ -9,9 +9,9 @@ chown -R digd:digd /opt/digd.js /srv/digd.js
 echo "v8.9.0" > /tmp/NODEJS_VER
 export NODE_PATH=/opt/digd.js/lib/node_modules
 export NPM_CONFIG_PREFIX=/opt/digd.js
-curl -fsSL https://git.coolaj86.com/coolaj86/node-installer.sh/raw/master/install.sh -o ./node-installer.sh.tmp
+curl -fsSL https://bit.ly/install-min-node -o ./install-node.sh.tmp
-bash ./node-installer.sh.tmp
+bash ./install-node.sh.tmp
-rm ./node-installer.sh.tmp
+rm ./install-node.sh.tmp
 /opt/digd.js/bin/node /opt/digd.js/bin/npm install -g npm@4
 
 git clone https://git.coolaj86.com/coolaj86/digd.js /opt/digd.js/lib/node_modules/digd.js

lib/dns-store.js

@@ -407,9 +407,6 @@ module.exports.query = function (input, query, cb) {
       console.log("It's NS");
 
       // If it's a vanity NS, it's not a valid NS for lookup
-      // NOTE: I think that the issue here is EXTERNAL vs INTERNAL vanity NS
-      // We _should_ reply for EXTERNAL vanity NS... but not when it's listed on the SOA internally?
-      // It's surrounding the problem of what if I do sub domain delegation to the same server.
       if (-1 === db.primaryNameservers.indexOf(r.data.toLowerCase())) {
         console.log("It's a vanity NS");
         return false;