The library includes tools for querying DNS servers and iterative DNS Resolution.
- Error recovery in DNS configurations.
- Experimental investigation of possibilities in the DNS.
- Development of ways to optimize client implementations.
- Understanding DNS.
- UDP and TCP clients.
- IPv4 and IPv6 (dual stack) support.
- Synchronous and asynchronous request methods.
- Interactively controllable resolution iterator.
- Event based logging.
// using Boethin.Net.DnsTools.DnsClient;
// using Boethin.Net.DnsTools.DnsClient.DNS;
// Get all RRs of www.example.com
using (IDnsClient client = new DnsUdpClient())
{
// a.iana-servers.net. is authoritative for www.example.com.
client.Connect("199.43.132.53");
// Perform non-recursive DNS request
Response response = client.Process(new Request(false,
new Question("www.example.com.", QTYPE.ANY)));
// Display result
Console.WriteLine("Request: \"{0}\" sent to 199.43.132.53", response.Questions.First());
if (response.Header.RCODE == RCODE.NoError) // response OK
{
foreach (RR rr in response.AnswerRecords)
Console.WriteLine("Answer: \"{0}\"", rr);
}
else // error
Console.WriteLine("Unexpected RCODE: {0}", response.Header.RCODE.ToString());
}
Request: "www.example.com. IN ANY" sent to 199.43.132.53 Answer: "www.example.com. 172800 IN A 192.0.43.10" Answer: "www.example.com. 172800 IN AAAA 2001:500:88:200::10" Answer: "www.example.com. 172800 IN TXT "v=spf1 -all"" Answer: "www.example.com. 172800 IN [46] [159 bytes]"
The RRs denoted as [46] within the response are RRSIG RRs. Since DNSSEC is not yet implemented, these RRs are not parsed. However you can access their raw byte data through the answer RRs.
// using Boethin.Net.DnsTools.DnsClient;
// using Boethin.Net.DnsTools.DnsClient.DNS;
// using Boethin.Net.DnsTools.Resolution;
// using Boethin.Net.DnsTools.Resolution.Iterators;
// using Boethin.Net.DnsTools.Resolution.Extensions;
// Perform an iterative reverse PTR lookup for 192.0.43.10
using (DomainResolver resolver = new DomainResolver(
IPAddress.Parse("192.0.43.10").GetArpaDomain())) // 10.43.0.192.in-addr.arpa
{
// use UDP
resolver.Connect(new DnsUdpClient());
using (ResolutionIterator iterator = resolver.GetIterator(QTYPE.PTR))
{
while (iterator.MoveNext())
{
Console.WriteLine("Request: \"{0}\" sent to {1}",
iterator.Current.Request.Questions.First(),
iterator.Current.Authorities.Selected.Name);
}
// Display result
if (iterator.Current.Response.Header.RCODE == RCODE.NoError) // response OK
{
foreach (RR rr in iterator.Current.Response.AnswerRecords)
Console.WriteLine("Answer: \"{0}\"", rr);
}
else // error
Console.WriteLine("Unexpected RCODE: {0}", iterator.Current.Response.Header.RCODE.ToString());
}
}
Request: "10.43.0.192.in-addr.arpa. IN PTR" sent to k.root-servers.net. Request: "10.43.0.192.in-addr.arpa. IN PTR" sent to a.in-addr-servers.arpa. Request: "w.arin.net. IN A" sent to j.root-servers.net. Request: "w.arin.net. IN A" sent to g.gtld-servers.net. Request: "w.arin.net. IN A" sent to ns2.arin.net. Request: "10.43.0.192.in-addr.arpa. IN PTR" sent to w.arin.net. Request: "ns.icann.org. IN A" sent to m.root-servers.net. Request: "ns.icann.org. IN A" sent to c0.org.afilias-nst.info. Request: "10.43.0.192.in-addr.arpa. IN PTR" sent to ns.icann.org. Answer: "10.43.0.192.in-addr.arpa. 21600 IN PTR 43-10.any.icann.org."
The resolution process starts with a root name server and ends up with an authoritty for the name in question. During the resolution process, there are several address resolutions performed in order to get name server addresses. The final result shows, that the IP address 192.0.43.10 points to the hostname 43-10.any.icann.org.
- Implementation of EDNS RFC 2671.
- Validation DNSSEC zones.
- Improving of caching mechanisms.
- Utilizing the resolver for consistency and existence tests.
This project contains a DNS client interface IDnsClient and a mapping of DNS data to a serializable class structure. The interface is implemented by two classes:
- DnsUdpClient: A UDP client, extending System.Net.Sockets.UdpClient.
- DnsTcpClient: A TCP client, extending System.Net.Sockets.TcpClient.
The client classes are implemented as extensions of the standard network clients provided by the .NET framework. This way the greatest possible flexibility is ensured with minimal implementation effort.
This project depends on the DnsClient project and contains an interactively controllable DNS resolver.
The resolver is serializable such that it's state can be saved after each iteration step. This way it's possible to implement an iterative step-by-step resolution (within a web application for example).
The mapping of IP addresses to ARPA domains for reverse resolution is implemeted by way of an extension of the System.Net.IPAddress class.
A WinForm application utilizing the DNS client.
An interactive console application providing iterative name resolution.
(Open Boethin.Net.DnsTools.Tests.sln for accessing the test projects.)
- RFC 1035 Domain Names - Implementation and Specification.
- RFC 2181 Clarifications to the DNS Specification.
- RFC 3425 Obsoleting IQUERY.
- RFC 1996 A Mechanism for Prompt Notification of Zone Changes (DNS NOTIFY)
- RFC 3596 DNS Extensions to Support IP Version 6 (AAAA RRs).
- RFC 2782 A DNS RR for specifying the location of services (SRV RRs).
- RFC 3403 Dynamic Delegation Discovery System (NAPTR RRs).
- RFC 4408 Sender Policy Framework (SPF RRs).
The resolver library contains a mirror of the IANA Root Hints File wich needs to be synchronized.
- The library is implemented in .NET 3.5. Both Visual Studio solutions (Boethin.Net.DnsTools.sln and Boethin.Net.DnsTools.Tests.sln) can be opened with Visual studio 2010 express.
- The code is compatible with Mono JIT compiler 2.6.7.