ASL V3 DDNS Problem

AllStarLink
1

How do I fix this?

This is a friends ASL node and his resolv.conf file has an additional set of data which I can't seem to remove.

His DDNS will not resolve from anywhere. e.g. nslookup #####.nodes.allstarlink.org yields nothing. AS a result his node is not working right.

Roger
WA1NVC

Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)

DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN

127.0.0.53 is the systemd-resolved stub resolver.

run "resolvectl status" to see details about the actual nameservers.

nameserver 1.1.1.1
nameserver 1.0.0.1

nameserver 1.1.1.1
nameserver 1.0.0.1
nameserver 192.168.1.1
search mynetworksettings.com

2

What node #?

Also, they should check their "Portal" / "Node Settings" on www.allstarlink.org and check that the "Is node a remote base station" value set to "No". If the node was set as a remote base then the DNS name would be #####.remotebase.nodes.allstarlink.org.

3

The DNS resolver settings have nothing to do with the nodes.allstarlink.org. That's purely a function of registation.

4

True.

  • you need a viable DNS configuration that can resolve names
  • your node needs to successfully register, else we don't publish any DNS records for the node
  • the node configuration does impact what DNS records are published (####.nodes.allstarlink.org vs. ####.remotebase.allstarlink.org)
5

There is clearly a Linux problem. The second set of nameserver definitions should not be present. How do I fix it? I tried using nmcli but neither eth0 or ipv4.dns is recognised.

nameserver 1.1.1.1
nameserver 1.0.0.1

nameserver 1.1.1.1
nameserver 1.0.0.1
nameserver 192.168.1.1
search mynetworksettings.com

6

What does sudo resolvconf -l report on your system ?

Asking because one of my systems has the first 2 lines from "tun.wg0" (this particular node is configured to use 44Net) and the last lines are from "NetworkManager".

7

Nameservers of 1.1.1.1 and 1.0.0.1 is Cloudflare DNS. Unless the local network is blocking outbound DNS, that isn't a problem. It may not be want you want, but it shouldn't be broken.

8

And I guess that brings up the question... what exactly are you trying to have the configuration be?