i did not understand the problem
&RQ, after a DNS failure, use a cached IP address for connecting
May be it was my mistype.
May be there was not failure. Who knows...
As I see AOL return on DNS requests different IP at different time.
This usually doing for dividing workload between several servers.
For example DNS reply at time i've writing this msg:
[login.icq.com]
Translated Name: login.login-grt.messaging.aol.com
IP Address: 64.12.161.153
IP Address: 64.12.161.185
IP Address: 64.12.200.89
IP Address: 205.188.179.233
Alias: login.icq.com
So really this may be situation when one of this server was down,
or incorrectly working.
&RQ try to connect and can't connect.
then get IP from cache, but cached address already not actual
(may be AOL switch workload to another server with different IP).
So what &RQ will do? I don't know :eek:
I think &RQ must try to connect on all returned by DNS-reply IP-addresses sequencely.
Getting IP from cache is economical but there may be probability of errors.