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. ----- Your Message May Appear Below This Line On Tue, 4 Jun 2002, Michael Montero wrote: > No, most certainly not. That's been covered already. I used to run > ipchains.....problem didn't exist with my simplistic rules. When I got a > little more serious and installed ip_tables the problem began. > > > >
