Weird dig behavior when querying ANY

Adamiec, Lawrence ladamiec at kentlaw.iit.edu
Tue Sep 10 15:49:14 UTC 2013


I don't get 5 seconds for a reply.


;; ANSWER SECTION:
google.com.             219     IN      AAAA    2607:f8b0:4009:805::1006
google.com.             29      IN      A       173.194.46.34
google.com.             29      IN      A       173.194.46.35
google.com.             29      IN      A       173.194.46.36
google.com.             29      IN      A       173.194.46.37
google.com.             29      IN      A       173.194.46.38
google.com.             29      IN      A       173.194.46.39
google.com.             29      IN      A       173.194.46.40
google.com.             29      IN      A       173.194.46.41
google.com.             29      IN      A       173.194.46.46
google.com.             29      IN      A       173.194.46.32
google.com.             29      IN      A       173.194.46.33
google.com.             33272   IN      NS      ns4.google.com.
google.com.             33272   IN      NS      ns2.google.com.
google.com.             33272   IN      NS      ns1.google.com.
google.com.             33272   IN      NS      ns3.google.com.



Larry




On Tue, Sep 10, 2013 at 10:40 AM, Nicholas F Miller <
nicholas.miller at colorado.edu> wrote:

> The problem is the reply will ALWAYS be five seconds when doing an 'ANY'
> query. It is not a matter of the TTL counting down.
> _________________________________________________________
> Nicholas Miller, OIT, University of Colorado at Boulder
>
>
>
>
> On Sep 10, 2013, at 9:24 AM, Matus UHLAR - fantomas <uhlar at fantomas.sk>
> wrote:
>
> > On 10.09.13 08:15, Nicholas F Miller wrote:
> >> I am at a loss. When doing digs using our name servers for 'ANY'
> records of
> >> a domain we are getting TTLs of five seconds.  The TTLs will be correct
> if
> >> we query for the records individually just not when using 'ANY'.  Ideas?
> >
> > BIND simply provides you the remaining TTL. If you do it again, you will
> see
> > TTL has either decreased in the time difference, or the records were
> fetched
> > again.
> >
> > the discussion a few days ago has revealed that BIND does not recursively
> > fetch records when you send ANY query.
> > --
> > Matus UHLAR - fantomas, uhlar at 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.
> > "They say when you play that M$ CD backward you can hear satanic
> messages."
> > "That's nothing. If you play it forward it will install Windows."
> > _______________________________________________
> > Please visit https://lists.isc.org/mailman/listinfo/bind-users to
> unsubscribe from this list
> >
> > bind-users mailing list
> > bind-users at lists.isc.org
> > https://lists.isc.org/mailman/listinfo/bind-users
>
> _______________________________________________
> Please visit https://lists.isc.org/mailman/listinfo/bind-users to
> unsubscribe from this list
>
> bind-users mailing list
> bind-users at lists.isc.org
> https://lists.isc.org/mailman/listinfo/bind-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/bind-users/attachments/20130910/7d857993/attachment.html>


More information about the bind-users mailing list