Re: dig +trace to find all the forwarders?

In message , Jo sh Kuo writes: > > You need administrative access to see the overides to the normal resolution > > process. > > > > > Just so I understand this completely, by administrative access you mean I > need to be able to log in to each of the resolvers (not administrative > access on my lo

Re: dig +trace to find all the forwarders?

> > You need administrative access to see the overides to the normal resolution > process. > > Just so I understand this completely, by administrative access you mean I need to be able to log in to each of the resolvers (not administrative access on my local workstation to do a 'sudo dig example.ne

Re: dig +trace to find all the forwarders?

In message , Jo sh Kuo writes: > Hi all, > > I am trying to trace a recursive outbound query. My workstation is > configured to point to the forwarder/resolver 192.168.0.2, which is a > dedicated forwarder that is configured to forward all DNS queries to the > ISP's DNS resolver. Sometimes I get

dig +trace to find all the forwarders?

Hi all, I am trying to trace a recursive outbound query. My workstation is configured to point to the forwarder/resolver 192.168.0.2, which is a dedicated forwarder that is configured to forward all DNS queries to the ISP's DNS resolver. Sometimes I get name resolution failures, and I want to know

Re: error (network unreachable)

In message , "ic.nssip" writ es: > > I just enabled querylog (using rndc querylog command) and each first = > query logged it's coming with errors (network unreachable) when trying = > to resolve dns servers names. > > Has anyone any idea where from this sort of message is coming from and = > wh