Back to index

tor  0.2.3.18-rc
Public Member Functions | Public Attributes
cached_resolve_t Struct Reference

A DNS request: possibly completed, possibly pending; cached_resolve structs are stored at the OR side in a hash table, and as a linked list from oldest to newest. More...

Collaboration diagram for cached_resolve_t:
Collaboration graph
[legend]

List of all members.

Public Member Functions

 HT_ENTRY (cached_resolve_t)

Public Attributes

 result
uint8_t state
 Is this cached entry pending/done/valid/failed?
uint8_t is_reverse
 Is this a reverse (addr-to-hostname) lookup?
time_t expire
 Remove items from cache after this time.
uint32_t ttl
 What TTL did the nameserver tell us?
pending_connection_tpending_connections
 Connections that want to know when we get an answer for this resolve.
int minheap_idx
 Position of this element in the heap.

Detailed Description

A DNS request: possibly completed, possibly pending; cached_resolve structs are stored at the OR side in a hash table, and as a linked list from oldest to newest.

Definition at line 140 of file dns.c.


Member Function Documentation

< IPv6 addr for address.

< IPv4 addr for address.

< Hostname for address (if a reverse lookup)

Definition at line 141 of file dns.c.

        {
    struct {
      struct in6_addr addr6; 
      uint32_t addr;  
    } a;
    char *hostname; 
  } result;

Member Data Documentation

Remove items from cache after this time.

Definition at line 153 of file dns.c.

Is this a reverse (addr-to-hostname) lookup?

Definition at line 152 of file dns.c.

Position of this element in the heap.

Definition at line 158 of file dns.c.

Connections that want to know when we get an answer for this resolve.

Definition at line 156 of file dns.c.

Definition at line 150 of file dns.c.

Is this cached entry pending/done/valid/failed?

Definition at line 151 of file dns.c.

What TTL did the nameserver tell us?

Definition at line 154 of file dns.c.


The documentation for this struct was generated from the following file: