> > On 07.07.10 20:43, Kebba Foon wrote: > > > I have been experience DNS resolutions problems these past few days, if > > > i run nslookup i get this error: > > > ;; connection timed out; no servers could be reached > > > > > > > with dig +trace i get: > > > > > > > ; <<>> DiG 9.6-ESV-R1 <<>> @<my ns server ip> espn.com +trace
> On Thu, 2010-07-08 at 10:37 +0200, Matus UHLAR - fantomas wrote: > > Combining +trace and @server is useless, either you want to trace, or you > > want to query specified server. On 08.07.10 09:00, Kebba Foon wrote: > I dont want to query a specific server, this is my cache server that i If you specify "@server" then you DO query specific server - the specified one. If you want to query your cache server, then it means you want to query the one specific server. You do that by by specifying it as "@server". The dig +trace does something very different, see dig manual page. > cant run any query from am trying to figure out why i cant query using > my server. can you log on the server, see logs, configuration, cache dump, network traffic dump and try to use dig from the server? -- Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/ Warning: I wish NOT to receive e-mail advertising to this address. Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu. Saving Private Ryan... Private Ryan exists. Overwrite? (Y/N) _______________________________________________ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
