On Wed, 7 Jan 2004, Kwan Lowe wrote:
> All the externals I've tried so far are not resolving my domain
> properly.
Around 3pm this afternoon I did a few more queries against
digitalhermit.com from a site downstream from Cogent, manually tracing
down from the GTLD servers to your nameserver, and ns1.digitalhermit.com
seemed to be responding perfectly. Well, aside from the fact that the
zone file is slightly in error -- it's missing an NS record that is being
listed by the registry as an additional authoritative server. And I think
there were two identical MX records with different priorities ("if this
one doesn't work, try speaking more slowly!").
I didn't try the other nameserver though... but it appears that your
nameserver is basically okay from my part of the net.
> Is there are way to query the TTL or expire values from dig if the
> domain isn't resolving. I.e., determine how long until a nameserver's
> cache expires?
If you're asking whether there's a way to tell remotely when a particular
nameserver will expire a given record in its cache: I believe the answer
is no, such information isn't provided in the DNS protocol.
I dunno, it sounds like you may be experiencing connectivity rather than
DNS problems. Perhaps some packet tracing is in order.
-----------------------------------------------------------------------
This list is provided as an unmoderated internet service by Networked
Knowledge Systems (NKS). Views and opinions expressed in messages
posted are those of the author and do not necessarily reflect the
official policy or position of NKS or any of its employees.
This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 20:14:32 EDT