Package: dnsdoctor
Version: 1.0.0-2

The choice of the rootservers set in /etc/dnsdoctor/rootservers is exclusive. I can set up the machine running dnsdoctor to use either the root server list from orsn as correct or from icann but not both. Chosen the orsn variant, all domains using icann servers fail and vice versa: The test result is:

Fatal
 Root-servers list is not consistent with ICANN

The root-server list (a.root-servers.net., b.root-servers.net., c.root-servers.net., d.root-servers.net., e.root-servers.net., f.root-servers.net., g.root-servers.net., h.root-servers.net., i.root-servers.net., j.root-servers.net., k.root-servers.net., l.root-servers.net., m.root-servers.net.) is not identicall to ICANN list (e.orsn-servers.net., h.orsn-servers.net., g.orsn-servers.net., j.orsn-servers.net., i.orsn-servers.net., b.orsn-servers.net., k.orsn-servers.net., a.orsn-servers.net., d.orsn-servers.net., c.orsn-servers.net., m.orsn-servers.net.).

(The above error shows up when using orsn on the dnsdoctor server querying a domain using icann servers. Note also, the errormessage is somewhat confusing...)

It would be nicer to have a mechanism to add a rootserver set to the rootserver set of icann. For example as a suggestion: Treat any file in the config dir named rootservers.<rootServerSetName> as a valid list of rootservers.

Regards, Adrian.


-- System Information:
Debian Release: 3.1
APT prefers testing
APT policy: (500, 'testing')
Architecture: alpha
Kernel: Linux 2.4.27-1-smp
Locale: LANG=en_GB.ISO-8859-15, LC_CTYPE=en_GB.ISO-8859-15 (charmap=ISO-8859-15)


Versions of packages dnsdoctor depends on:
ii iputils-ping 3:20020927-2 Tools to test the reachability of
ii libiconv-ruby 0.4.5+ruby1.8-8 A Wrapper class of iconv for the R
ii librexml-ruby 2.7.1-8 pure Ruby non-validating XML parse
ii libyaml-ruby 0.60-8 YAML for Ruby
ii ruby 1.8.1-8 An interpreter of object-oriented


-- no debconf information


-- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Reply via email to