forked from coolaj86/digd.js
		
	clarify (kinda) vanity nameserver comment
This commit is contained in:
		
							parent
							
								
									148bda8afc
								
							
						
					
					
						commit
						a1eca4f1a5
					
				| @ -407,6 +407,9 @@ module.exports.query = function (input, query, cb) { | |||||||
|       console.log("It's NS"); |       console.log("It's NS"); | ||||||
| 
 | 
 | ||||||
|       // If it's a vanity NS, it's not a valid NS for lookup
 |       // 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())) { |       if (-1 === db.primaryNameservers.indexOf(r.data.toLowerCase())) { | ||||||
|         console.log("It's a vanity NS"); |         console.log("It's a vanity NS"); | ||||||
|         return false; |         return false; | ||||||
|  | |||||||
		Loading…
	
	
			
			x
			
			
		
	
		Reference in New Issue
	
	Block a user