# ASL3 Reported node cannot be found!"

**URL:** <https://community.allstarlink.org/t/asl3-reported-node-cannot-be-found/22087>\
**Category:** Archive\
**Created:** [October 19, 2024, 1:20pm UTC](https://community.allstarlink.org/t/asl3-reported-node-cannot-be-found/22087 "2024-10-19T13:20:43Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![N4IRS](https://community.allstarlink.org/user_avatar/community.allstarlink.org/n4irs/32/548_2.png) [@N4IRS](https://community.allstarlink.org/u/N4IRS)\
**Post date:** [October 19, 2024, 1:20pm UTC](https://community.allstarlink.org/t/asl3-reported-node-cannot-be-found/22087/1 "2024-10-19T13:20:43Z")

</div>

I am connecting to a existing hub in the cloud (2100) from my LAN. My IP has not changed in 4 years. 9 time out of 10 (a phrase, not a actual number) I can connect to 2100. Every once in a while I get this on the ASL console:

app\_rpt.c:6572 rpt\_exec: Reported node 459510 cannot be found!!

Nothing has changed, and on the next attempt I get a valid connection.  
I am running apt\_rpt in: node\_lookup\_method = dns

dig on the 2100 host returns a valid TXT record for 459510.  
I sure don’t want to revert to the node list, and yes, I can do both.

73, Steve N4IRS
