Words by Michael Montero [Tue, Jun 04, 2002 at 04:02:25PM -0400]: > However, I'm not sure why digging domains would work consistently all the > time then suddenly trigger nslookup to work. To prove it's not some type > of caching I'll nslookup a domain and get temporary failure in name > resolution. Then I'll dig a completely different domain and get results > successfully. Then I will return to nslookup the first domain....which I > did not lookup using dig. And it resolves. Everything thereafter > resolves fine. > > If however, I then do: > > nslookup > > server [any name server] > some.domain.com > > It fails....times out. All the time. I'm assuming my rules are blocking > this. I'm just not sure how.....how the dig utility differs from > nslookup. >
Dig doesn't try to resolve the reverse for the dns server and fail if it can't. Check it out. -- Jose Celestino <[EMAIL PROTECTED]> SAPO.pt::Systems http://www.sapo.pt --------------------------------------------------------------------- Quod licet Iovi non licet bovi. (What Jove may do, is not permitted to a cow.)
