XLXHOST.TXT

Suggest new features here
Post Reply
VK2YMU
Posts: 18
Joined: Wed Apr 11, 2018 11:42 pm

XLXHOST.TXT

Post by VK2YMU » Wed Jun 27, 2018 4:00 am

Is it possible to have domain name instead of IP for individual XLX entries
The reason for this is that some XLX use dynamic IP should for any reason that IP changes, the XLX is no longer reachable.
For a current example, XLX 389 has changed IP and the new IP has not propagated to the XLXHOST file, requiring manual entry in the file to make that service work.

Why not let the DNS mechanism resolve IP's
Thanks.

w7efs
Posts: 44
Joined: Sun Apr 22, 2018 4:26 pm

Re: XLXHOST.TXT

Post by w7efs » Sat Jun 30, 2018 4:39 pm

VK2YMU wrote:
Wed Jun 27, 2018 4:00 am
... Why not let the DNS mechanism resolve IP's
Thanks.
The primary reason is that all IP addresses are resolved at ircddbgatewayd start-up. This adds a very substantial delay while awaiting the DNS timeouts for unresolveable domains.

VK2YMU
Posts: 18
Joined: Wed Apr 11, 2018 11:42 pm

Re: XLXHOST.TXT

Post by VK2YMU » Wed Jul 11, 2018 12:04 am

Thank you for your response, so why when I manually edit the file, placing the domain name of the host whose IP is wrong, I then can reach that host?

M0GLJ
Posts: 76
Joined: Thu Apr 05, 2018 2:48 am
Location: United Kingdom
Contact:

Re: XLXHOST.TXT

Post by M0GLJ » Wed Jul 18, 2018 6:18 pm

w7efs wrote:
Sat Jun 30, 2018 4:39 pm


The primary reason is that all IP addresses are resolved at ircddbgatewayd start-up. This adds a very substantial delay while awaiting the DNS timeouts for unresolveable domains.
When an XLX or any reflector changes IP address it takes a little time to propagate to the rest of the network. Pi-Star has an update system in place that import the information and your Pi-Star downloads the information during the automatic update process that happens around 3am in you local time zone. You can if you choose to do a MANUAL update at anytime
Adrian
M0GLJ

ZUMradio ■ ZUMspot ■ DV-Mega

D-star --> IC-E92D
DMR --> DM-4600 ■ DM-4601 ■ MD-380 ■ RT-82

w7efs
Posts: 44
Joined: Sun Apr 22, 2018 4:26 pm

Re: XLXHOST.TXT

Post by w7efs » Thu Jul 19, 2018 10:03 pm

VK2YMU wrote:
Wed Jul 11, 2018 12:04 am
Thank you for your response, so why when I manually edit the file, placing the domain name of the host whose IP is wrong, I then can reach that host?
For the simple reason that the particular DNS entry you made was resolvable ... not all of them are, and those that are sometimes don't have a correct DNS zone file that allows IP<->DNS. As a matter of fact the xlx/xrf hosts have more unresolvable domain names than any of the other digital modes/protocols. As an advanced example, we check for how many IP entries already exist in XLXHosts.txt (there are 2 "s" in the filename, and Linux is case-sensitive):

[email protected](ro):~$ grep -c [0-254].[0-254].[0-254].[0-254] /usr/local/etc/XLXHosts.txt
156

Now we can check for how many of those can be resolved, as I installed a handy perl script for such things:

[email protected](ro):~$ jdresolve -r -a -n /usr/local/etc/XLXHosts.txt | grep -c [0-254].[0-254].[0-254].[0-254]
67

So we see that 67/156 or 43% of the currently known XLXHosts.txt are unresolvable.

Post Reply