BIND Non-authoritative.
Been working on BIND for some time now and finally got it to work so other servers can reach for dns lookup however.
if I do dig on Linux machine I get all my answers: Code:
[myuser@mynixserver ~]# dig @10.x.x.x cnn.com Code:
|
What windows is providing is a cached entry, not one from the server. That is why it is "non-authoritative".
This is done to minimize the impact on a name server by thousands of queries. When one tracks down your server, the host (well, name server actually) then caches the answer - so that your server doesn't have to respond any more (at least, not until the timeout interval happens). Over time, thousands of other name servers would pick up your entry - eliminating them from directly contacting your server, and in addition, spread the load out. OCCASIONALLY, (not very often) I have pre-seeded other name servers by selecting them as a name server and then looking up the designated target. Doing this between the root servers and the intermediate servers between you and the root (there usually is only two or three), greatly reduces an initial load, and can reduce the occurrence of timeouts for users. It doesn't work well when the timeout is long though - the servers will only update after their cache entry times out. |
Quote:
I thought to try some non-cached domain...on windows server by doing nslookup server 10.x.x.x >zumba.com and this is what I get back Code:
02-Sep-2013 17:34:47.008 client 10.x.x.x#22547: query: zumba.xyz.com IN A + |
All times are GMT -5. The time now is 10:51 PM. |