Hello Tommi!

27 Sep 25 09:11, you wrote to me:

It's showing the same result as yours.

fido:/var/spool/ftn/filebase/nodelist$ drill SRV _binkp._tcp.f360.n221.z2.binkp.net
;; ->>HEADER<<- opcode: QUERY, rcode: NOERROR, id: 48424
;; flags: qr rd ra ; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;; _binkp._tcp.f360.n221.z2.binkp.net. IN SRV

;; ANSWER SECTION:
_binkp._tcp.f360.n221.z2.binkp.net. 14400 IN SRV 0 0 360 f360.n221.z2.rbb.fidonet.fi.

;; AUTHORITY SECTION:

;; ADDITIONAL SECTION:

;; Query time: 390 msec
;; SERVER: 10.10.20.150
;; WHEN: Sat Sep 27 10:19:46 2025
;; MSG SIZE rcvd: 99

Hi Javier.

26 Sep 25 15:48:04, you wrote to me:

f360.n221.z2.binkp.net:24554 [51.38.115.207]

Now your binkd here is using the standard binkp port instead of
what is in the nodelist and in the binkp.net dns srv record. :(

I've seen this happening in windows...

I'm running binkd in a FreeBSD jail.

tommi@mxo:~$ dig +short SRV _binkp._tcp.f360.n221.z2.binkp.net
0 0 360 f360.n221.z2.rbb.fidonet.fi.
=== <- There is the port to poll by binkp.

Your FreeBSD must be based on windows then! :D

'Tommi

---
* Origin: Point One (2:221/1.1)

Javier


--- GoldED+/BSD 1.1.5-b20170303-b20170303 + HPT 1.9.0 + Binkd 1.1a-115
* Origin: FIDONODO DE JAS | ¯\_(O,O)_/¯ (4:900/733)

On 29.09.2025 1:53, Javier Sturman wrote:

27 Sep 25 09:11, you wrote to me:

It's showing the same result as yours.

As it should.

The question is, why is your binkd (as well as the windows version of mine) not using the correct port?

fido:/var/spool/ftn/filebase/nodelist$ drill SRV _binkp._tcp.f360.n221.z2.binkp.net
;; ->>HEADER<<- opcode: QUERY, rcode: NOERROR, id: 48424
;; flags: qr rd ra ; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;; _binkp._tcp.f360.n221.z2.binkp.net. IN SRV

;; ANSWER SECTION:
_binkp._tcp.f360.n221.z2.binkp.net. 14400 IN SRV 0 0 360 f360.n221.z2.rbb.fidonet.fi.

'Tommi

---
* Origin: nntp://news.fidonet.fi (2:221/360.0)

Hello Tommi,

On Tuesday September 30 2025 08:15, you wrote to Javier Sturman:

It's showing the same result as yours.

As it should.

The question is, why is your binkd (as well as the windows version of mine) not using the correct port?

Because the Windows version of binkd does no read the SERV record when using binkd.net. My version of binkd - running on Win7 - has the same - annoying - shortcoming. It does not look this is going to be fixed any time soon. Let's get rid of IPv4. With IPv6 there is no need to meddle with non standard ports any more...


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: http://www.vlist.eu (2:280/5555)

Hi Michiel.

30 Sep 25 10:12:40, you wrote to me:

It's showing the same result as yours.

As it should.

The question is, why is your binkd (as well as the windows version
of mine) not using the correct port?

Because the Windows version of binkd does no read the SERV record when using binkd.net.

No shit Sherlock! :D

'Tommi

---
* Origin: Point One (2:221/1.1)

Good ${greeting_time}, Tommi!

30 Sep 25 08:15, you wrote to Javier Sturman:

The question is, why is your binkd (as well as the windows version of mine) not using the correct port?

IIRC, I tried it a couple of years ago on Linux and it didn't work. Does your binkp look up SRV records?

* Origin: kakistocracy (2:280/464.47)

Hi Oli.

30 Sep 25 09:58, you wrote to me:

IIRC, I tried it a couple of years ago on Linux and it didn't work. Does your
binkp look up SRV records?

It does.

grep f360 /var/log/named/query.log
30-Sep-2025 12:25:34.206 client @0x7f66fc2f2d48 127.0.0.1#36838 (_binkp._tcp.f360.n221.z2.binkp.net): query: _binkp._tcp.f360.n221.z2.binkp.net IN SRV + (127.0.0.1)
30-Sep-2025 12:25:34.206 client @0x7f66fc2f2d48 127.0.0.1#43829 (f360.n221.z2.rbb.fidonet.fi): query: f360.n221.z2.rbb.fidonet.fi IN A + (127.0.0.1)
30-Sep-2025 12:25:34.206 client @0x7f66fc01d1a8 127.0.0.1#43829 (f360.n221.z2.rbb.fidonet.fi): query: f360.n221.z2.rbb.fidonet.fi IN AAAA + (127.0.0.1)

'Tommi

--- GoldED+/LNX 1.1.5-b20250409
* Origin: nntps://news.fidonet.fi (2:221/1)