The discussion on the DNS cache file and how it is/can be use has
been fascinating but may I humbly bring the discussion back to the initial
requirement.
The main problem is with addresses which never resolve, take the
range 24.0.0.0 - 24.23.255.255 which apparently has been allocated to
homenet.com.
This covers over 1.5 Million addresses and every time a new one from
this range access your site it involves a DNSlookup which will not be
resolved.
Preloading the DNS cache file with all these addresses and then
loading them into analog seems a complete waste of time.
This seems even more so when I can use HOSTALIAS to get the
domain/org information for my report with the following 3 lines.
HOSTALIAS REGEXP:^(24\.[0-9]\..*)$ $1.homenet.com
HOSTALIAS REGEXP:^(24\.1[0-9]\..*)$ $1.homenet.com
HOSTALIAS REGEXP:^(24\.2[0-3]\..*)$ $1.homenet.com
Here is the real CRUNCH question. What problems would it cause to
do the HOSTALIAS'ing before the DNS lookup code ?
If we did it HOSTALIAS processing first then the DNS lookup would
not happen as we have what now looks like a hostname,
Result is no 3-10 second lookup, no entry "time n.n.n.n *"
for an unresolved address in the DNS cache
This gives faster run of analog, smaller DNS cache and everybody
happy (well me at least).
I can't think why you want to HOSTALIAS a range of addresses and
also have a DNS lookup performed on them as well - what am I missing
(logically not personally please)
Regards Jamie
+------------------------------------------------------------------------
| This is the analog-help mailing list. To unsubscribe from this
| mailing list, go to
| http://lists.isite.net/listgate/analog-help/unsubscribe.html
|
| List archives are available at
| http://www.mail-archive.com/[email protected]/
| http://lists.isite.net/listgate/analog-help/archives/
+------------------------------------------------------------------------
