problem with resolving SOME EXTERNAL domains

[Ronan Flood]

On Wed, 15 Jun 2005 09:05:44 -0400,
"mayer" <mayer at gis.net> wrote:

> > So dig +trace *is* querying the resolver for the addresses of the
> > intermediate nameservers on the descent from the root, rather than
> > using any associated glue.  Is there any way to override this and
> > force dig +trace to do *all* the resolution itself?  If not, perhaps
> > there should be ...
> 
> You didn't specify a nameserver to use so it goes to /etc/resolv.conf
> to get one. If you had specified one on the command line (@nameserver)
> it would not even have done that.

It would if I'd specified @ns.example.com (i.e. name rather than IP) :-/

> dig +trace is meant to use the nameserver for all lookups. It just
> does iterative queries to that nameserver. dig isn't designed to
> do resolution itself. All it can do is ask for a specific piece of
> information from a specific nameserver and get an answer back. +trace
> makes it ask for each piece one after the other. But all it's doing
> is iterating.

That's fair enough; I'm only saying that having some means of doing,
and showing, the full workings might be useful.  Perhaps a separate
utility -- there may even be something out there already, eg along
the lines of the DNS traversal http://www.squish.net/dnscheck/ 

-- 
                      Ronan Flood <R.Flood at noc.ulcc.ac.uk>
                        working for but not speaking for
             Network Services, University of London Computer Centre
     (which means: don't bother ULCC if I've said something you don't like)