# Nodes.allstarlink.org DNS Service Update

**URL:** <https://community.allstarlink.org/t/nodes-allstarlink-org-dns-service-update/21879>\
**Category:** AllStarLink\
**Created:** [September 13, 2024, 9:57pm UTC](https://community.allstarlink.org/t/nodes-allstarlink-org-dns-service-update/21879 "2024-09-13T21:57:01Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![N8EI](https://community.allstarlink.org/user_avatar/community.allstarlink.org/n8ei/32/4254_2.png) [@N8EI](https://community.allstarlink.org/u/N8EI)\
**Post date:** [September 13, 2024, 9:57pm UTC](https://community.allstarlink.org/t/nodes-allstarlink-org-dns-service-update/21879/1 "2024-09-13T21:57:01Z")

</div>

Over the last few months, there have been sporadic problems with the DNS-based node lookup introduced with ASL3. Most of these issues revolved around how certain ISPs behaved with the information being provided from servers for `nodes.allstarlink.org`. Early this morning, a new service was brought online to serve the DNS-based node lookups and it appears from early results that these issues are resolved.

If you were having a problem connecting to other nodes and you followed the suggestion to change `node_lookup_method`, please revert that change. The change to `file` from either `dns` (preferred) or `both` in `/etc/asterisk/rpt.conf` should be changed back to your original setting and restart asterisk. We would like additional testing and confirmation that these issues have been resolved.

Please note that a certain subset of users who were experiencing the issues described in GitHub items [#390](https://github.com/AllStarLink/app_rpt/issues/390) and [#392](https://github.com/AllStarLink/app_rpt/issues/392) **may** find the situation improved but those are still an outstanding bug to resolve.

N8EI

---

<div class="post-metadata">

**Author:** ![KG5DRT](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/k/77aa72/32.png) [@KG5DRT](https://community.allstarlink.org/u/KG5DRT)\
**Post date:** [September 19, 2024, 2:10pm UTC](https://community.allstarlink.org/t/nodes-allstarlink-org-dns-service-update/21879/2 "2024-09-19T14:10:39Z")

</div>

I switched to dns just now and was able to successfully connect to another node with 5 digits via dtmf where previously it would always fail. Now after testing 3 different nodes, it works every time. I opened [#390](https://github.com/AllStarLink/app_rpt/issues/390) Asterisk 20.9.1+asl3-3.0.4-1.deb12

---

<div class="post-metadata">

**Author:** ![N8EI](https://community.allstarlink.org/user_avatar/community.allstarlink.org/n8ei/32/4254_2.png) [@N8EI](https://community.allstarlink.org/u/N8EI)\
**Post date:** [September 19, 2024, 3:51pm UTC](https://community.allstarlink.org/t/nodes-allstarlink-org-dns-service-update/21879/3 "2024-09-19T15:51:56Z")

</div>

TERRIFIC!! Thanks for the positive feedback. That’s the kind of improvement we were hoping to see.