Fork us on GitHub Follow us on Facebook Follow us on Twitter

Opened 9 years ago

Closed 6 years ago

#189 closed enhancement (fixed)

DNS resolver

Reported by: Jakub Jermář Owned by: Jiri Svoboda
Priority: major Milestone: 0.6.0
Component: helenos/net/other Version: mainline
Keywords: Cc:
Blocker for: Depends on: #405
See also:

Description (last modified by Jakub Jermář)

Implement the client support for the DNS protocol so that HelenOS can resolve DNS queries. It would be sufficient if the support was first delivered only in the form of a Stub Resolver, as defined by RFC 1123 in 6.1.3.1.

It is reasonable to expect this ticket to deliver the DNS resolver functionality in some sort of a library that other networking code and applications can use.

Change History (8)

comment:1 Changed 9 years ago by Jakub Jermář

Description: modified (diff)

comment:2 Changed 9 years ago by Jiri Svoboda

It would seem better in line with HelenOS design for the resolver to be a service. The resolver is likely to implement some form of caching eventually. The cache would be a shared cache (if we resolve hostname A on behalf of one task, no need to resolve it again on behalf of another task). This is easier and more elegantly achieved if there is one central resolver with applications calling it via IPC, rather than having the resolver distributed into the applications and communicating via, say, the file system.

comment:3 Changed 8 years ago by Jakub Jermář

Milestone: 0.5.00.5.1

comment:4 Changed 8 years ago by Jiri Svoboda

Depends on: #405

comment:5 Changed 7 years ago by Jakub Jermář

Milestone: 0.5.00.5.1

comment:6 Changed 7 years ago by Jiri Svoboda

Owner: set to Jiri Svoboda
Status: newaccepted

comment:7 Changed 7 years ago by Jiri Svoboda

comment:8 Changed 6 years ago by Jiri Svoboda

Resolution: fixed
Status: acceptedclosed

Merged in mainline,1818. dnsrsrv (service), dnsres (resolution utility) and dnscfg (configuration utility). Plus HelenOS utilities that take an IP adress as argument fixed to accept host name, too.

Future work:

  • recursive querying
  • domain search list
  • lazy decompression
Note: See TracTickets for help on using tickets.