forum.pistar.uk

In the last several days, XLX139 was brought online after a previous iteration was removed from service. The new IP is 45.79.59.24

The Reflector List on the XLX dashboards has the proper URL and PhoneHome is functional. http://xlx139.dyndns.org

Can get this get updated? I have refreshed/updated tow pi-star instances and they still yeild the old IP as shown at https://www.pistar.uk/downloads/XLXHosts.txt

Very strange, as Pistar pulls xlx ip addresses directly from xlx.

ran a manual update agn to get the latest host updates. Pistar server syncs data a few times a day. You might of pulled the update previous to it syncing new data.

If its still not updating the correct data let me know and well take a closer look, but atm im not in front of anything to check


Sent via smoke signals from my SM-G935F M1DNS (Admin)

Yes... very starnge.

The XLXDMRMaster file has the bad IP address for XLX139. I looked at the DExtra_Hosts (XRF139 = 45.79.59.24) it is correct but DPlus_Hosts (REF139) and DCS_Hosts (DCS139) are not correct. The incorrect ones have the old IP, 66.42.93.25. The new IP is 45.79.59.24

So are these seperate reflectors or are they all running via ur xlx.

ie xlx is handling all protocols.

And im going to suppose the reflector no. hasn't been in use before by another party.

ie no one else is already running a ref139 or dcs139. Because if so those addresses would be pulled from another source.


Also theres this DDNS currently set.
139 = xlx139.lmarc.net

Have you updated your new DNS record, as whats reported is this one above.

Sent via smoke signals from my SM-G935F M1DNS (Admin)

From what I read at https://lmarc.net/club/: 2022/11/16 – XRF139 (or XLX / DCS depending on your use) has been retired! The LMARC XLX/XRF/DCS 139 reflector has been retired as of 11/16/2022. 

So maybe they did not remove the DNS listing?

I hoping to use REF, XRF, DCS and XLX iterations of the 139 number.

I have registered:
xlx139.dyndns.org Host 45.79.59.24

Terry

Update ur dns record to the new one.
And itll be sorted and will continue to run without any futhur issue, and morein with no additional intervention by us, ad: most of what happens on the back end of pistar is automonous now.

Sent via smoke signals from my SM-G935F M1DNS (Admin)

Was not sure what you meant by updating my DNS? I verified that my host designation at DynDNS is correct. It is working. The old URL and IP are non-functional. I understand that pi-star gets its info from the XLX system… and the info on Reflector tab of any XLX system is correct. So I am not sure where it is broken?

http://xlx351.dyndns.org/index.php?show=reflectors

Suggestions? Thank you.

Ok so this is whats reporting to us...

- edited just to show ur entries -


DCS_Hosts.txt updated
--- CURRENT DCS_Hosts.txt 2023-01-14 01:17:40.936840542 +0000
+++ UPDATED DCS_Hosts.txt 2023-01-14 02:17:40.465395883 +0000
@@ -138 +138 @@
-DCS139 66.42.93.25
+DCS139 xlx139.lmarc.net
@@ -153 +153 @@


DPlus_WithXRF_Hosts.txt updated
--- CURRENT DPlus_WithXRF_Hosts.txt 2023-01-14 01:17:43.044872766 +0000
+++ UPDATED DPlus_WithXRF_Hosts.txt 2023-01-14
-REF139 66.42.93.25
+REF139 xlx139.lmarc.net
@@ -157 +157 @@


XLXHosts.txt updated
--- CURRENT XLXHosts.txt 2023-01-14 01:17:42.296861331 +0000
+++ UPDATED XLXHosts.txt 2023-01-14 02:
+139;xlx139.lmarc.net;4004
@@ -211 +211 @@


ur old DNS entry is still active, somewhere.

Sent via smoke signals from my SM-G935F M1DNS (Admin)

I found another source of D—Star hosts and submitted corrections/updates:

http://arrg.us/HF/index.htm
DEXTRA http://www.arrg.us/HF/DExtra_Hosts.txt
DPLUS http://www.arrg.us/HF/DPlus_Hosts.txt
DCS http://www.arrg.us/HF/DCS_Hosts.txt

I am still seeing this entry at: 139;xlx139.lmarc.net;4004 as downloaded just now at https://www.pistar.uk/downloads/XLXHosts.txt

The file says it is sourced from http://xlxapi.rlx.lu/api.php?do=GetXLXDMRMaster which shows:
XLX139 45.79.59.24

I have nothing to do with the previous iteration of XLX139, so there is not much I can do about that old domain name.

I do see this on one of my linux boxes:

dig -t NS xlx139.lmarc.net

; <<>> DiG 9.11.4-P2-RedHat-9.11.4-26.P2.el7_9.13 <<>> -t NS xlx139.lmarc.net
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 58311
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;xlx139.lmarc.net. IN NS

;; AUTHORITY SECTION:
lmarc.net. 1800 IN SOA dns1.namecheaphosting.com. cpanel.tech.namecheap.com. 1674660066 86400 7200 3600000 86400

;; Query time: 25 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Tue Feb 07 16:50:00 EST 2023
;; MSG SIZE rcvd: 128

And my version of xlx139.dyndns.org appears correctly:
dig -t NS xlx139.dyddns.org

; <<>> DiG 9.11.4-P2-RedHat-9.11.4-26.P2.el7_9.13 <<>> -t NS xlx139.dyddns.org
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 21303
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;xlx139.dyddns.org. IN NS

;; ANSWER SECTION:
xlx139.dyddns.org. 300 IN NS ns111373.ztomy.com.
xlx139.dyddns.org. 300 IN NS ns211373.ztomy.com.

;; Query time: 125 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Tue Feb 07 16:51:10 EST 2023
;; MSG SIZE rcvd: 101