Node allstarlink registration - custom port not working anymore possibly since updating node

[n8lbv]

I opened a new Topic over here.
Unless I am terribly mistaken or being really stupid, I think I am seeing a major service affecting problem with the backend.

Allstar registration not syncing to backend DNS not updating

I’ve been watching this for about four hours. From what I am seeing on my end, it appears that registration events are not updating part of the backend and what eventually makes it to DNS. I moved a node earlier today to a different Internet connection. It is registering properly with Allstar but is not updating DNS and thus the nodes list is not being updated properly. My node (27298) was intentionally changed to a different public facing IP address earlier today. And is on a different Int…