Dns Dart Reference Documentation

CkDns

Current Version: 11.6.1

Chilkat.Dns

Configure DNS resolution and query DNS records directly from Chilkat.

Chilkat.Dns is a focused class for DNS configuration and DNS record querying. It allows applications to control the nameservers used by Chilkat, query common DNS record types into JSON, configure DNS-over-TLS preference, set DNS query timeouts, and obtain useful diagnostics through LastErrorText.

DNS record queries

Query common DNS record types and receive structured JSON results that are easy to inspect or pass to other application logic.

Nameserver control

Configure the nameservers Chilkat uses instead of relying only on the operating system's default DNS configuration.

DNS-over-TLS preference

Prefer DNS-over-TLS when appropriate for applications that need encrypted DNS lookups.

Timeout settings

Control how long DNS queries may wait before failing, which is useful for responsive applications and troubleshooting.

Application-wide behavior

Nameserver settings affect DNS resolution across Chilkat classes, not only the current Dns object.

Diagnostics

Use LastErrorText to troubleshoot DNS configuration, lookup failures, timeout problems, or nameserver connectivity issues.

Common pattern: Use Dns either to perform direct DNS lookups, or to configure the DNS behavior used by Chilkat as a whole. Because nameserver changes can affect DNS resolution across Chilkat classes, treat them as application-wide configuration rather than object-local state.

Object Creation

// pubspec.yaml:
//     dependencies:
//       chilkat: ^11.6.1

import 'package:chilkat/chilkat.dart';

// Once per process, before any other Chilkat call:
Chilkat.unlockBundle('Anything for 30-day trial');   // shorthand for CkGlobal().unlockBundle(..)

final dns = CkDns();
// ... the native object is released when `dns` is garbage collected, or now with dns.dispose().
CkDns CkDns()

Creates the underlying native Chilkat object. Use a CkDns only from the isolate that created it: Chilkat objects cannot be sent between isolates. Every call is synchronous; in a Flutter app, run long operations (network, large files) inside Isolate.run, creating the Chilkat objects inside the isolate.

void dispose()

Releases the native object immediately instead of waiting for garbage collection (useful for a large CkBinData or an open socket). Calling it more than once is harmless; any other use of the object afterwards throws a StateError. isDisposed tells whether it has been called.

Errors

A method that can fail throws a ChilkatException: a method whose only outcome is success or failure returns void and throws on failure; a method producing a String or an object returns it and throws where Chilkat would have returned null. The exception carries the object's LastErrorText at the time of the failure (lastErrorText), the class and method names (className, methodName) and a one-line message. Properties never throw, and methods that answer a question (has..., is..., ...) return a plain bool.

try {
  dns.someMethod(...);
} on ChilkatException catch (e) {
  print(e);                // CkDns.someMethod failed: <reason>
  print(e.lastErrorText);  // the full Chilkat log of the failed call
}

Properties

DebugLogFilePath
// read/write
String get debugLogFilePath
set debugLogFilePath(String value)

If set to a file path, this property logs the LastErrorText of each Chilkat method or property call to the specified file. This logging helps identify the context and history of Chilkat calls leading up to any crash or hang, aiding in debugging.

Enabling the VerboseLogging property provides more detailed information. This property is mainly used for debugging rare instances where a Chilkat method call causes a hang or crash, which should generally not happen.

Possible causes of hangs include:

  • A timeout property set to 0, indicating an infinite timeout.
  • A hang occurring within an event callback in the application code.
  • An internal bug in the Chilkat code causing the hang.

More Information and Examples
top
HeartbeatMs
// read/write
int get heartbeatMs
set heartbeatMs(int value)
Introduced in version 9.5.0.96

The interval in milliseconds between each AbortCheck event callback, which enables an application to abort certain method calls before they complete. By default, HeartbeatMs is set to 0, meaning no AbortCheck event callbacks will trigger.

More Information and Examples
top
LastErrorHtml
// read-only
String get lastErrorHtml

Provides HTML-formatted information about the last called method or property. If a method call fails or behaves unexpectedly, check this property for details. Note that information is available regardless of the method call's success.

top
LastErrorText
// read-only
String get lastErrorText

Provides plain text information about the last called method or property. If a method call fails or behaves unexpectedly, check this property for details. Note that information is available regardless of the method call's success.

top
LastErrorXml
// read-only
String get lastErrorXml

Provides XML-formatted information about the last called method or property. If a method call fails or behaves unexpectedly, check this property for details. Note that information is available regardless of the method call's success.

top
LastMethodSuccess
// read/write
bool get lastMethodSuccess
set lastMethodSuccess(bool value)

Indicates the success or failure of the most recent method call: true means success, false means failure. This property remains unchanged by property setters or getters. This method is present to address challenges in checking for null or Nothing returns in certain programming languages. Note: This property does not apply to methods that return integer values or to boolean-returning methods where the boolean does not indicate success or failure.

top
MaxWaitMs
// read/write
int get maxWaitMs
set maxWaitMs(int value)
Introduced in version 9.5.0.96

The maxiumum number of milliseconds to wait for the answer to a DNS query. A value of 0 is to wait indefinitely (no timeout). It's not a good idea to specify 0 (infinite timeout) or a value less than 1000 (1 second). The default value is 10000 milliseconds.

top
NumNameservers
// read-only
int get numNameservers
Introduced in version 9.5.0.96

The number of nameservers currently being used by Chilkat for DNS queries in all objects/classes, such as for HTTP, Email, FTP, SSH, etc.

top
TlsPref
// read/write
int get tlsPref
set tlsPref(int value)
Introduced in version 9.5.0.96

Specifies the TLS preference. Possible values are:

  • 0 = No TLS
  • 1 = Prefer TLS if possible.
  • 2 = Require TLS

The default value is 0. If TLS is preferred then DNS nameservers with TLS capability will be tried first. If none succeed, then UDP/TCP will be tried. If TLS is required, then only TLS capable nameservers will be tried and all DNS queries will use TLS.

Note: To use TLS, your application needs to first specify nameservers by calling AddNameserver once per nameserver with the supportsTls argument set to true.

top
UncommonOptions
// read/write
String get uncommonOptions
set uncommonOptions(String value)
Introduced in version 11.4.0

This is a catch-all property to be used for uncommon needs. This property defaults to the empty string and should typically remain empty.

top
VerboseLogging
// read/write
bool get verboseLogging
set verboseLogging(bool value)

If set to true, then the contents of LastErrorText (or LastErrorXml, or LastErrorHtml) may contain more verbose information. The default value is false. Verbose logging should only be used for debugging. The potentially large quantity of logged information may adversely affect peformance.

top
Version
// read-only
String get version

Version of the component/library, such as "10.1.0"

More Information and Examples
top

Methods

AddDefaultNameservers
void addDefaultNameservers()
Introduced in version 9.5.0.96

Adds the default (auto-assigned) nameservers to the collection of nameservers used by Chilkat for DNS queries and domain to IP address lookups.

top
AddNameserver
void addNameserver(String ipAddr, bool supportsTls)
Introduced in version 9.5.0.96

Adds a new nameserver to the collection of nameservers used by Chilkat for DNS queries and domain to IP address lookups. The ipAddr specifies the IPv4 address of the nameserver. The supportsTls indicates if the namserver supports DoT (DNS over TLS. DoT uses port 853 for encrypted DNS communication.) If the TlsPreference property is set to 1 or 2, then Chilkat will use TLS nameservers.

top
GetNameserver
String getNameserver(int index)
Introduced in version 9.5.0.96

Returns the IP address of the Nth nameserver currently used by Chilkat for DNS queries and domain to IP address lookups. The index specifies the index of the nameserver. The 1st nameserver is at index 0.

Throws a ChilkatException on failure (where the description says null is returned, the Dart method throws instead).

More Information and Examples
top
Query
void query(String recordType, String domain, CkJsonObject answer)
Introduced in version 9.5.0.96

Performs an DNS query for domain and returns the answer in answer. The type of DNS query is specified in recordType and can be A, AAAA, ALIAS, CAA, MX, NS, SOA, TXT. Additional record types can be added as needed.

Returns normally on success; throws a ChilkatException on failure.

top
RemoveAllNameservers
void removeAllNameservers()
Introduced in version 9.5.0.96

Removes all nameservers from the collection of nameservers used by Chilkat. An application can call this method to reset to 0 nameservers before adding new nameservers. If a DNS domain to IP address resolution is needed by Chilkat, then the auto-assigned nameserver IP addresses will be automaticaly restored.

top
RemoveNameserver
void removeNameserver(String ipAddr)
Introduced in version 9.5.0.96

Removes a nameserver from the collection of nameservers used by Chilkat. The ipAddr is the IPv4 address of the nameserver to be removed.

top

Events

All Chilkat methods are synchronous: the call returns when the work is done. During a call, CkDns raises three events so your application can show progress and offer a way out. Each event is a nullable callback property on the object; assign a function to receive it, or null to stop receiving it:

final dns = CkDns();
dns.onPercentDone = (pct) {
  print('$pct%');
  return false;   // return true to abort the method in progress
};
dns.onProgressInfo = (name, value) => print('$name: $value');
dns.heartbeatMs = 250;   // raise onAbortCheck 4 times per second during Chilkat calls
dns.onAbortCheck = () => _userPressedCancel;

AbortCheck fires at regular intervals controlled by the HeartbeatMs property (0, the default, disables it); PercentDone fires when an operation's completion percentage is known; ProgressInfo delivers named progress values. Returning true from onAbortCheck or onPercentDone aborts the running method, which then throws a ChilkatException.

Events fire on the thread that called the method, before that method returns. An exception thrown inside a callback aborts the running method and is rethrown from it once the native library has returned. In a Flutter app the callbacks run inside the worker isolate that owns the object; forward progress to the UI through a SendPort, and let onAbortCheck read a flag the UI sets the same way.

AbortCheck
// callback property; return true to abort the method in progress
bool Function()? onAbortCheck

Enables a method call to be aborted by triggering the AbortCheck event at intervals defined by the HeartbeatMs property. If HeartbeatMs is set to its default value of 0, no events will occur. For instance, set HeartbeatMs to 200 to trigger 5 AbortCheck events per second.

More Information and Examples

Example:

dns.heartbeatMs = 250;   // call onAbortCheck 4 times per second

var cancelRequested = false;
dns.onAbortCheck = () => cancelRequested;
// ... set cancelRequested = true (e.g. from a message received on a ReceivePort) to abort the method in progress
top
PercentDone
// callback property; return true to abort the method in progress
bool Function(int pctDone)? onPercentDone

This provides the percentage completion for any method involving network communications or time-consuming processing, assuming the progress can be measured as a percentage. This event is triggered only when it's possible and logical to express the operation's progress as a percentage. The pctDone argument will range from 1 to 100. For methods that finish quickly, the number of PercentDone callbacks may vary, but the final callback will have pctDone equal to 100. For longer operations, callbacks will not exceed one per percentage point (e.g., 1, 2, 3, ..., 98, 99, 100).

The PercentDone callback also acts as an AbortCheck event. For fast methods where PercentDone fires, an AbortCheck event may not trigger since the PercentDone callback already provides an opportunity to abort. For longer operations, where time between PercentDone callbacks is extended, AbortCheck callbacks enable more responsive operation termination.

To abort the operation, set the abort output argument to true. This will cause the method to terminate and return a failure status or corresponding failure value.

More Information and Examples

Example:

dns.onPercentDone = (pct) {
  // pct ranges from 1 to 100.
  print('Percent done: $pct');
  return false;   // return true to abort the method in progress
};
top
ProgressInfo
// callback property
void Function(String name, String value)? onProgressInfo

This event callback provides tag name/value pairs that detail what occurs during a method call. To discover existing tag names, create code to handle the event, emit the pairs, and review them. Most tag names are self-explanatory.

Note: Some Chilkat methods don't fire any ProgressInfo events.

More Information and Examples

Example:

dns.onProgressInfo = (name, value) => print('$name: $value');
top