Salaam!
For years, I have been using the AnalogX "QuickDNS" (v2.00,
8/12/2000) to build my dns.txt file for Analog. However, with a DNS
file of 850,000 IP addresses, I have run into a problem, and my
solutions have been a bit short. Here is the problem:
Some canonical names are excessively long, and QDNS cannot handle
them; some canonical names contain an asterisk, which seems to cause
other problems; and when attempting to merge new entries, I
occasionally get a "can't read memory at" some address. This always
indicates a series of non-printable characters at the end of one
canonical name, which causes QDNS to stop reading the dns file ~ the
number of "DNS entries loaded" is far short of the entire file, and of
course the resulting new dns.txt file is several megabytes shorter.
So I am now resolving new entries into a temporary dnst.txt file,
which I edit to remove those problematic entries, then merge it with
the main dns.txt file. With a dns.txt file of some 47 megabytes, not
even my metapad text editor can edit the file and successfully save it
to the drive. With the smaller file of new entries, QDNS can handle it.
However, when I resolve a few thousand entries, and have that
dnst.txt file ready to merge, QDNS treats these resolved entries as
unresolved, and does its lookups before adding them to the main
dns.txt file. Usually, it fails to resolve all of them, so that they
do not all get added to the dns.txt file. This remains true no matter
how soon after the original resolution (into the dnst.txt file) QDNS
does its second (unnecessary) set of lookups.
I know a lot of people use QDNS for Analog. Has anyone else
encountered this kind of problem? Two questions:
1. How do I prevent QDNS from attempting to add these bogus
canonical names ~ the too-long names and the names containing
asterisks or unprintable characters ~ to the dns.txt file, or ignoring
them when it encounters the unprintable characters in the dns.txt
file? and
2. How do I make QDNS simply merge the resolved entries in the
temporary dnst.txt file into the main dns.txt file without trying to
resolve them (they're already resolved!!!)?
Or perhaps a third question: Where do I look for answers to these
questions? QDNS is, in my opinion, a marvelous companion to Analog,
of comparable workmanship, but has not been updated since 2000. Is
there a solution for this?
was-salaam,
abujamal
+------------------------------------------------------------------------
| TO UNSUBSCRIBE from this list:
| http://lists.meer.net/mailman/listinfo/analog-help
|
| Analog Documentation: http://analog.cx/docs/Readme.html
| List archives: http://www.analog.cx/docs/mailing.html#listarchives
| Usenet version: news://news.gmane.org/gmane.comp.web.analog.general
+------------------------------------------------------------------------
For years, I have been using the AnalogX "QuickDNS" (v2.00,
8/12/2000) to build my dns.txt file for Analog. However, with a DNS
file of 850,000 IP addresses, I have run into a problem, and my
solutions have been a bit short. Here is the problem:
Some canonical names are excessively long, and QDNS cannot handle
them; some canonical names contain an asterisk, which seems to cause
other problems; and when attempting to merge new entries, I
occasionally get a "can't read memory at" some address. This always
indicates a series of non-printable characters at the end of one
canonical name, which causes QDNS to stop reading the dns file ~ the
number of "DNS entries loaded" is far short of the entire file, and of
course the resulting new dns.txt file is several megabytes shorter.
So I am now resolving new entries into a temporary dnst.txt file,
which I edit to remove those problematic entries, then merge it with
the main dns.txt file. With a dns.txt file of some 47 megabytes, not
even my metapad text editor can edit the file and successfully save it
to the drive. With the smaller file of new entries, QDNS can handle it.
However, when I resolve a few thousand entries, and have that
dnst.txt file ready to merge, QDNS treats these resolved entries as
unresolved, and does its lookups before adding them to the main
dns.txt file. Usually, it fails to resolve all of them, so that they
do not all get added to the dns.txt file. This remains true no matter
how soon after the original resolution (into the dnst.txt file) QDNS
does its second (unnecessary) set of lookups.
I know a lot of people use QDNS for Analog. Has anyone else
encountered this kind of problem? Two questions:
1. How do I prevent QDNS from attempting to add these bogus
canonical names ~ the too-long names and the names containing
asterisks or unprintable characters ~ to the dns.txt file, or ignoring
them when it encounters the unprintable characters in the dns.txt
file? and
2. How do I make QDNS simply merge the resolved entries in the
temporary dnst.txt file into the main dns.txt file without trying to
resolve them (they're already resolved!!!)?
Or perhaps a third question: Where do I look for answers to these
questions? QDNS is, in my opinion, a marvelous companion to Analog,
of comparable workmanship, but has not been updated since 2000. Is
there a solution for this?
was-salaam,
abujamal
+------------------------------------------------------------------------
| TO UNSUBSCRIBE from this list:
| http://lists.meer.net/mailman/listinfo/analog-help
|
| Analog Documentation: http://analog.cx/docs/Readme.html
| List archives: http://www.analog.cx/docs/mailing.html#listarchives
| Usenet version: news://news.gmane.org/gmane.comp.web.analog.general
+------------------------------------------------------------------------