Hey folks,

Just thought I'd let you know that fsxnet is now supporting DNS nodelist queries. (FTS-5004)

Paul delegated z21.fsxnet.nz to clrghouz, which means your node and BBS name, including operating ports are available in the DNS.

The syntax is [pP.]fX.nY.z21.fsxnet.nz, where P is the point address (this is optional, and clrghouz doesnt have any point definitions in it). X is your node number and Y is your net number.

So for my BBS, its f116.n2.z21.fsxnet.nz. Querying a TXT record you should get back the BBS name (Alterant):

For clrghouz:
host -t TXT f100.n3.z21.fsxnet.nz
f100.n3.z21.fsxnet.nz descriptive text "Clearing Houz"

Querying for a SRV record, you prefix that with _binkp._tcp..., so for clrghouz:
host -t SRV _binkp._tcp.f100.n3.z21.fsxnet.nz
_binkp._tcp.f100.n3.z21.fsxnet.nz has SRV record 0 0 24554 clrghouz.bbs.dege.au.

and emsi...
host -t SRV _ifcico._tcp.f100.n3.z21.fsxnet.nz _ifcico._tcp.f100.n3.z21.fsxnet.nz has SRV record 0 1 60179 clrghouz.bbs.dege.au.

This is only useful to you, if you have a mailer that supports DNS queries. Currently Synchronet does, and I believe binkd does as well - not sure about other software.

If your details are not correct, make sure your hub has the updated information, which is sent on Thursday's to Paul for inclusion in the next nodelist. For Hub 3 nodes, you can update your details in clrghouz, and it'll be visible immediately.


...δεσ∩
--- SBBSecho 3.20-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)

Hey folks,

Just thought I'd let you know that fsxnet is now supporting DNS nodelist queries. (FTS-5004)

Paul delegated z21.fsxnet.nz to clrghouz, which means your node and BBS name, including operating ports are available in the DNS.

Good job!

--- BBBS/Li6 v4.10 Toy-6
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)

BY: deon (21:2/116)

|11d|09> |10Just thought I'd let you know that fsxnet is now supporting DNS nodelist|07
|11d|09> |10queries. (FTS-5004)|07

Wow, super cool. Thanks for sharing. It works for me, I guess I should add support for this into wwiv's ftn/binkp code now :)

|11r|09ushfan|07



--- WWIV 5.9.0.3686[Linux 5.10.0-20]
* Origin: Mystic Rhythms BBS (21:2/115)

On 05 Oct 2023 at 03:43p, deon pondered and said...

Hey folks,

Just thought I'd let you know that fsxnet is now supporting DNS nodelist queries. (FTS-5004)

Paul delegated z21.fsxnet.nz to clrghouz, which means your node and BBS name, including operating ports are available in the DNS.

thanks for all your hard work on this Deon, really appreciated :)

Kerr Avon [Blake's 7] 'I'm not expendable, I'm not stupid and I'm not going' avon[at]bbs.nz | bbs.nz | fsxnet.nz

--- Mystic BBS v1.12 A48 (Linux/64)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

Re: DNS Nodelist available for fsxnet
By: deon to All on Thu Oct 05 2023 03:43 pm

Hey folks,

Just thought I'd let you know that fsxnet is now supporting DNS nodelist queries. (FTS-5004)

Paul delegated z21.fsxnet.nz to clrghouz, which means your node and BBS name, including operating ports are available in the DNS.

The syntax is [pP.]fX.nY.z21.fsxnet.nz, where P is the point address (this is optional, and clrghouz doesnt have any point definitions in it). X is your node number and Y is your net number.

So for my BBS, its f116.n2.z21.fsxnet.nz. Querying a TXT record you should get back the BBS name (Alterant):

For clrghouz:
host -t TXT f100.n3.z21.fsxnet.nz
f100.n3.z21.fsxnet.nz descriptive text "Clearing Houz"

Querying for a SRV record, you prefix that with _binkp._tcp..., so for clrghouz:
host -t SRV _binkp._tcp.f100.n3.z21.fsxnet.nz _binkp._tcp.f100.n3.z21.fsxnet.nz has SRV record 0 0 24554 clrghouz.bbs.dege.au.

$ host -t SRV _binkp._tcp.f100.n3.z21.fsxnet.nz
Host _binkp._tcp.f100.n3.z21.fsxnet.nz not found: 2(SERVFAIL)

:-(
--
digital man (rob)

Synchronet "Real Fact" #31:
The Synchronet IRC server (ircd) was written in JS by Randy Sommerfeld (Cyan) Norco, CA WX: 60.8°F, 37.0% humidity, 0 mph ENE wind, 0.00 inches rain/24hrs --- SBBSecho 3.20-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (21:1/183)

Re: Re: DNS Nodelist available for fsxnet
By: Avon to deon on Mon Oct 09 2023 09:16 pm

On 05 Oct 2023 at 03:43p, deon pondered and said...

Hey folks,

Just thought I'd let you know that fsxnet is now supporting DNS nodelist queries. (FTS-5004)

Paul delegated z21.fsxnet.nz to clrghouz, which means your node and BBS name, including operating ports are available in the DNS.

thanks for all your hard work on this Deon, really appreciated :)

Head's up, the DNS support doesn't seem to be working at the moment.
--
digital man (rob)

This Is Spinal Tap quote #14:
The Boston gig has been cancelled. [Don't] worry, it's not a big college town. Norco, CA WX: 60.8°F, 37.0% humidity, 0 mph ENE wind, 0.00 inches rain/24hrs --- SBBSecho 3.20-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (21:1/183)

On Fri, 10 Nov 2023 20:03:44 -0800
"Digital Man" (21:1/183) <Digital.Man@f183.n1.z21.fidonet> wrote:

Re: DNS Nodelist available for fsxnet
By: deon to All on Thu Oct 05 2023 03:43 pm

Hey folks,

Just thought I'd let you know that fsxnet is now supporting DNS
nodelist queries. (FTS-5004)

Paul delegated z21.fsxnet.nz to clrghouz, which means your node
and BBS name, including operating ports are available in the DNS.

The syntax is [pP.]fX.nY.z21.fsxnet.nz, where P is the point
address (this is optional, and clrghouz doesnt have any point
definitions in it). X is your node number and Y is your net number.

So for my BBS, its f116.n2.z21.fsxnet.nz. Querying a TXT record
you should get back the BBS name (Alterant):

For clrghouz:
host -t TXT f100.n3.z21.fsxnet.nz
f100.n3.z21.fsxnet.nz descriptive text "Clearing Houz"

Querying for a SRV record, you prefix that with _binkp._tcp..., so
for clrghouz:
host -t SRV _binkp._tcp.f100.n3.z21.fsxnet.nz _binkp._tcp.f100.n3.z21.fsxnet.nz has SRV record 0 0 24554 clrghouz.bbs.dege.au.

$ host -t SRV _binkp._tcp.f100.n3.z21.fsxnet.nz
Host _binkp._tcp.f100.n3.z21.fsxnet.nz not found: 2(SERVFAIL)

:-(

Seems to be working ok here


bbs@bbs:~$ host -t TXT f100.n3.z21.fsxnet.nz
f100.n3.z21.fsxnet.nz descriptive text "Clearing Houz"
bbs@bbs:~$ host -t SRV _binkp._tcp.f100.n3.z21.fsxnet.nz _binkp._tcp.f100.n3.z21.fsxnet.nz has SRV record 0 1 24554 clrghouz.bbs.dege.au. bbs@bbs:~$ host -t SRV
_ifcico._tcp.f100.n3.z21.fsxnet.nz _ifcico._tcp.f100.n3.z21.fsxnet.nz
has SRV record 0 1 60179 clrghouz.bbs.dege.au.
--
End Of The Line BBS - Plano, TX
telnet endofthelinebbs.com 23
--- SBBSecho 3.20-Linux
* Origin: End Of The Line BBS - endofthelinebbs.com (21:2/101)

Re: DNS Nodelist available for fsxnet
By: Digital Man to deon on Fri Nov 10 2023 08:03 pm

Howdy,

$ host -t SRV _binkp._tcp.f100.n3.z21.fsxnet.nz
Host _binkp._tcp.f100.n3.z21.fsxnet.nz not found: 2(SERVFAIL)

:-(

Odd, I just did it and it worked for me.

[deon@vps-7c13b6c6 ~]$ host -t SRV _binkp._tcp.f100.n3.z21.fsxnet.nz _binkp._tcp.f100.n3.z21.fsxnet.nz has SRV record 0 1 24554 clrghouz.bbs.dege.au.

Your message is timed 4 hrs ago, but the earliest query I had for that fqdn today was 1 hr ago...

Still not working for you?


...δεσ∩
--- SBBSecho 3.20-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)

Re: Re: DNS Nodelist available for fsxnet
By: Digital Man to Avon on Fri Nov 10 2023 08:05 pm

Head's up, the DNS support doesn't seem to be working at the moment.

Actually the problem might be somewhere else - I've responded 4,213 times today to DNS queries in the domain fsxnet.nz




...δεσ∩
--- SBBSecho 3.20-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)

Hello Deon!

On 11 Nov 2023, deon said the following...

Actually the problem might be somewhere else - I've responded 4,213
times today to DNS queries in the domain fsxnet.nz

Yep. For me, it doesn't work when using the DNS of my ISP, but it works just fine when using one of Google's DNS servers or clrghouz.bbs.dege.au directly:

bbs@glimmer:~$ host -vvv -t SRV _binkp._tcp.f202.n1.z21.fsxnet.nz 83.255.255.1 Trying "_binkp._tcp.f202.n1.z21.fsxnet.nz"
Using domain server:
Name: 83.255.255.1
Address: 83.255.255.1#53
Aliases:

Host _binkp._tcp.f202.n1.z21.fsxnet.nz not found: 2(SERVFAIL)
Received 51 bytes from 83.255.255.1#53 in 8 ms

bbs@glimmer:~$ host -vvv -t SRV _binkp._tcp.f202.n1.z21.fsxnet.nz 83.255.255.2 Trying "_binkp._tcp.f202.n1.z21.fsxnet.nz"
;; communications error to 83.255.255.2#53: timed out
Using domain server:
Name: 83.255.255.2
Address: 83.255.255.2#53
Aliases:

Host _binkp._tcp.f202.n1.z21.fsxnet.nz not found: 2(SERVFAIL)
Received 51 bytes from 83.255.255.2#53 in 8 ms

bbs@glimmer:~$ host -vvv -t SRV _binkp._tcp.f202.n1.z21.fsxnet.nz 8.8.8.8 Trying "_binkp._tcp.f202.n1.z21.fsxnet.nz"
Using domain server:
Name: 8.8.8.8
Address: 8.8.8.8#53
Aliases:

;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 42
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;_binkp._tcp.f202.n1.z21.fsxnet.nz. IN SRV

;; ANSWER SECTION:
_binkp._tcp.f202.n1.z21.fsxnet.nz. 19910 IN SRV 0 1 24554 scbbs.nsupdate.info.

Received 90 bytes from 8.8.8.8#53 in 16 ms

bbs@glimmer:~$ host -vvv -t SRV _binkp._tcp.f202.n1.z21.fsxnet.nz clrghouz.bbs.dege.au
Trying "_binkp._tcp.f202.n1.z21.fsxnet.nz"
Using domain server:
Name: clrghouz.bbs.dege.au
Address: 115.70.188.114#53
Aliases:

;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6842
;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;_binkp._tcp.f202.n1.z21.fsxnet.nz. IN SRV

;; ANSWER SECTION:
_binkp._tcp.f202.n1.z21.fsxnet.nz. 86400 IN SRV 0 1 24554 scbbs.nsupdate.info.

Received 90 bytes from 115.70.188.114#53 in 320 ms
bbs@glimmer:~$

Not sure of the best way to pinpoint this, though. Could there be something "firewallish" preventing some of the "upstream" DNSes from getting answers from clrghouz.bbs.dege.au? Or perhaps they have restricted the allowed queries... Strange.

Best regards
Zip

--- Mystic BBS v1.12 A49 2023/04/30 (Linux/64)
* Origin: Star Collision BBS, Uppsala, Sweden (21:1/202)

Re: DNS Nodelist available for fsxnet
By: Zip to deon on Sat Nov 11 2023 11:39 am

Yep. For me, it doesn't work when using the DNS of my ISP, but it works just fine when using one of Google's DNS servers or clrghouz.bbs.dege.au directly:

bbs@glimmer:~$ host -vvv -t SRV _binkp._tcp.f202.n1.z21.fsxnet.nz 83.255.255.1 Trying "_binkp._tcp.f202.n1.z21.fsxnet.nz"
Using domain server:
Name: 83.255.255.1
Address: 83.255.255.1#53
Aliases:

Host _binkp._tcp.f202.n1.z21.fsxnet.nz not found: 2(SERVFAIL)
Received 51 bytes from 83.255.255.1#53 in 8 ms

Although you have mentioned server 83.255.255.1, I actually have an IP block on 83.255.224.0/24 (perhaps 255.1 uses?). When I enabled the DNS queries, several servers in this block were hammering clrghouz - 10+ queries a second, and to the same records (so not honouring the TTL).

The TTL (negative) cache time might actually be my problem - I may not be returning the right response for an NXDOMAIN, its something I need to double check on to be sure (I think I need to included an SOA record in the authority record of the response), which I'm not doing.

I'll disabled that block for now - let me know if it works for you.


...δεσ∩
--- SBBSecho 3.20-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)

Hello Deon!

Thank you for your reply!

On 11 Nov 2023, deon said the following...

Although you have mentioned server 83.255.255.1, I actually have an IP block on 83.255.224.0/24 (perhaps 255.1 uses?). When I enabled the DNS queries, several servers in this block were hammering clrghouz - 10+ queries a second, and to the same records (so not honouring the TTL).

Yep! That netblock belongs to Tele2, one of the major ISPs here in Sweden (who in recent years acquired a company called ComHem, one of the major players in residential broadband here).

The TTL (negative) cache time might actually be my problem - I may not be returning the right response for an NXDOMAIN, its something I need to double check on to be sure (I think I need to included an SOA record in the authority record of the response), which I'm not doing.

Negative TTLs are a pain, and DNS troubleshooting can be, too! :)

I'll disabled that block for now - let me know if it works for you.

Thanks! It seems that this changed things a little -- querying 83.255.255.1 or 83.255.255.2 multiple times in a row now returns either SERVFAIL or a correct answer in an alternating fashion, e.g.:

bbs@glimmer:~$ host -vvv -t SRV _binkp._tcp.f202.n1.z21.fsxnet.nz 83.255.255.2 Trying "_binkp._tcp.f202.n1.z21.fsxnet.nz"
Using domain server:
Name: 83.255.255.2
Address: 83.255.255.2#53
Aliases:

Host _binkp._tcp.f202.n1.z21.fsxnet.nz not found: 2(SERVFAIL)
Received 51 bytes from 83.255.255.2#53 in 8 ms

bbs@glimmer:~$ host -vvv -t SRV _binkp._tcp.f202.n1.z21.fsxnet.nz 83.255.255.2 Trying "_binkp._tcp.f202.n1.z21.fsxnet.nz"
Using domain server:
Name: 83.255.255.2
Address: 83.255.255.2#53
Aliases:

;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 44666
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;_binkp._tcp.f202.n1.z21.fsxnet.nz. IN SRV

;; ANSWER SECTION:
_binkp._tcp.f202.n1.z21.fsxnet.nz. 86238 IN SRV 0 1 24554 scbbs.nsupdate.info.

Received 90 bytes from 83.255.255.2#53 in 4 ms

bbs@glimmer:~$ host -vvv -t SRV _binkp._tcp.f202.n1.z21.fsxnet.nz 83.255.255.2 Trying "_binkp._tcp.f202.n1.z21.fsxnet.nz"
Using domain server:
Name: 83.255.255.2
Address: 83.255.255.2#53
Aliases:

Host _binkp._tcp.f202.n1.z21.fsxnet.nz not found: 2(SERVFAIL)
Received 51 bytes from 83.255.255.2#53 in 8 ms

Judging from the intermittent failures, it appears that some TTL stuff could indeed be affecting things...

Best regards
Zip

--- Mystic BBS v1.12 A49 2023/04/30 (Linux/64)
* Origin: Star Collision BBS, Uppsala, Sweden (21:1/202)

On Fri, 10 Nov 2023 20:03:44 -0800
"Digital Man" (21:1/183) <Digital.Man@f183.n1.z21.fidonet> wrote:

Re: DNS Nodelist available for fsxnet By: deon to All on Thu Oct 05
2023 03:43 pm

Hey folks,

Just thought I'd let you know that fsxnet is now supporting DNS
nodelist queries. (FTS-5004)

Paul delegated z21.fsxnet.nz to clrghouz, which means your node and
BBS name, including operating ports are available in the DNS.

The syntax is [pP.]fX.nY.z21.fsxnet.nz, where P is the point address
(this is optional, and clrghouz doesnt have any point definitions
in it). X is your node number and Y is your net number.

So for my BBS, its f116.n2.z21.fsxnet.nz. Querying a TXT record you
should get back the BBS name (Alterant):

For clrghouz: host -t TXT f100.n3.z21.fsxnet.nz f100.n3.z21.fsxnet.nz
descriptive text "Clearing Houz"

Querying for a SRV record, you prefix that with _binkp._tcp..., so
for clrghouz: host -t SRV _binkp._tcp.f100.n3.z21.fsxnet.nz
_binkp._tcp.f100.n3.z21.fsxnet.nz has SRV record 0 0 24554
clrghouz.bbs.dege.au.

$ host -t SRV _binkp._tcp.f100.n3.z21.fsxnet.nz Host
_binkp._tcp.f100.n3.z21.fsxnet.nz not found: 2(SERVFAIL)

:-(

Seems to be working ok here

bbs@bbs:~$ host -t TXT f100.n3.z21.fsxnet.nz f100.n3.z21.fsxnet.nz descriptive text "Clearing Houz" bbs@bbs:~$ host -t SRV _binkp._tcp.f100.n3.z21.fsxnet.nz _binkp._tcp.f100.n3.z21.fsxnet.nz
has SRV record 0 1 24554 clrghouz.bbs.dege.au. bbs@bbs:~$ host -t
SRV _ifcico._tcp.f100.n3.z21.fsxnet.nz
_ifcico._tcp.f100.n3.z21.fsxnet.nz has SRV record 0 1 60179 clrghouz.bbs.dege.au. -- End Of The Line BBS - Plano, TX telnet endofthelinebbs.com 23
--- SBBSecho 3.20-Linux
* Origin: End Of The Line BBS - endofthelinebbs.com (21:2/101)

How would I do this in windows? I tried nslookup, but it failed on the
domain.

---
Shurato, Sysop Shurato's Heavenly Sphere (ssh, telnet, pop3, ftp,nntp)
(ports 22, 23, 110, 21, 119) (ssh: login bbs password shsbbs)


*** THE READER V4.50 [freeware]
---
* Origin: Shurato's Heavenly Sphere telnet://shsbbs.net (21:2/148)

Re: Re: DNS Nodelist available for fsxnet
By: Shurato to Nigel Reed on Sat Nov 11 2023 20:12:00

How would I do this in windows? I tried nslookup, but it failed on the domain.

nslookup -q=TXT f100.n3.z21.fsxnet.nz

But Google would have told you that, too.
--- SBBSecho 3.20-Linux
* Origin: End Of The Line BBS - endofthelinebbs.com (21:2/101)

Re: Re: DNS Nodelist available for fsxnet
By: Zip to deon on Sat Nov 11 2023 03:25 pm

Howdy,

Although you have mentioned server 83.255.255.1, I actually have an IP block on 83.255.224.0/24 (perhaps 255.1 uses?). When I enabled the DNS queries, several servers in this block were hammering clrghouz - 10+ queries a second, and to the same records (so not honouring the TTL).

Yep! That netblock belongs to Tele2, one of the major ISPs here in Sweden (who in recent years acquired a company called ComHem, one of the major players in residential broadband here).

So I updated clrghouz yesterday as per RFC2308 and included an SOA record with negative hits. This has reduced the queries dramaticaly coming from this net block, so I wont re-enable the block. (Since I have a TTL of 1 day, hopefully those server errors on queries should be gone now.)

I'm still getting queries every minute or so for 21:1/1, 21:1/2 and 21:1/3.

[2023-11-13 07:55:37] production.INFO: PD-:= DNS Query from [::ffff:83.255.224.43] for [_binkp._tcp.f1.n1.z21.fsxnet.nz] {"pid":1690}
[2023-11-13 07:56:56] production.INFO: PD-:= DNS Query from [::ffff:83.255.224.35] for [_binkp._tcp.f3.n1.z21.fsxnet.nz] {"pid":1692}
[2023-11-13 07:56:58] production.INFO: PD-:= DNS Query from [::ffff:83.255.224.35] for [_binkp._tcp.f3.n1.z21.fsxnet.nz] {"pid":1693}

I'm curious (only because you mentioned you use a DNS server in the 83.255/16 block) - do you have something trying to talk to those hosts? Those servers are querying for those FTNs quite often (and they dont exist).


...δεσ∩
--- SBBSecho 3.20-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)

Re: Re: DNS Nodelist available for fsxnet
By: Nigel Reed to Shurato on Sun Nov 12 2023 02:14 am

How would I do this in windows? I tried nslookup, but it failed on the
domain.

nslookup -q=TXT f100.n3.z21.fsxnet.nz
But Google would have told you that, too.

And it did, but when I used my address it failed.

C:\Users\Owner>nslookup -q=TXT f148.n2.z21.fsxnet.nz
Server: modem.Home
Address: 192.168.0.1

*** modem.Home can't find f148.n2.z21.fsxnet.nz: Server failed

I must be doing something else wrong...
--- SBBSecho 3.20-Win32
* Origin: -=[conchaos.synchro.net | ConstructiveChaos BBS]=- (21:4/141)

Re: Re: DNS Nodelist available for fsxnet
By: Shurato to Nigel Reed on Sun Nov 12 2023 20:54:11

C:\Users\Owner>nslookup -q=TXT f148.n2.z21.fsxnet.nz
Server: modem.Home
Address: 192.168.0.1

*** modem.Home can't find f148.n2.z21.fsxnet.nz: Server failed

C:\Users\nigel>nslookup -q=TXT f148.n2.z21.fsxnet.nz
Server: gateway.lan
Address: fd3a:ae24:b05c::1

Non-authoritative answer:
f148.n2.z21.fsxnet.nz text =

"Shurato's Heavenly Sphere BBS"

Dunno what to tell you. Works here.
--- SBBSecho 3.20-Linux
* Origin: End Of The Line BBS - endofthelinebbs.com (21:2/101)

On 11 Nov 2023, Shurato said the following...

How would I do this in windows? I tried nslookup, but it failed on the domain.

nslookup -type=TXT f100.n3.z21.fsxnet.nz clrghouz.bbs.dege.au

Server: UnKnown
Address: 2406:3400:314:2497:d0c:202:0:f

f100.n3.z21.fsxnet.nz text =

"Clearing Houz"

nslookup -type=SRV _binkp._tcp.f100.n3.z21.fsxnet.nz

Server: UnKnown
Address: 10.0.1.1

Non-authoritative answer:
_binkp._tcp.f100.n3.z21.fsxnet.nz SRV service location:
priority = 0
weight = 1
port = 24554
svr hostname = clrghouz.bbs.dege.au


Jay

... It takes guts to be an organ donor

--- Mystic BBS v1.12 A49 2023/04/30 (Linux/64)
* Origin: Northern Realms (21:3/110)

Hello Deon!

Thank you for your reply and for looking into this!

On 13 Nov 2023, deon said the following...

record with negative hits. This has reduced the queries dramaticaly
coming from this net block, so I wont re-enable the block. (Since I have
a TTL of 1 day, hopefully those server errors on queries should be gone now.)

I'm still getting intermittent SERVFAILs here, but perhaps that will subside with time.

I'm curious (only because you mentioned you use a DNS server in the 83.255/16 block) - do you have something trying to talk to those hosts?

Nope, sorry, not that I know of...

Also, I'm guessing that the different IPs you're seeing is likely due to some load balancing at their end (customers might only get .1 and .2, and can only communicate with those, but queries to those are forwarded to a larger number of machines, which might be sitting on the same subnet).

Best regards
Zip

--- Mystic BBS v1.12 A49 2023/04/30 (Linux/64)
* Origin: Star Collision BBS, Uppsala, Sweden (21:1/202)

Re: Re: DNS Nodelist available for fsxnet
By: deon to Zip on Mon Nov 13 2023 08:10 am

Re: Re: DNS Nodelist available for fsxnet
By: Zip to deon on Sat Nov 11 2023 03:25 pm

Howdy,

Although you have mentioned server 83.255.255.1, I actually have an IP block on 83.255.224.0/24 (perhaps 255.1 uses?). When I enabled the DNS queries, several servers in this block were hammering clrghouz - 10+ queries a second, and to the same records (so not honouring the TTL).

Yep! That netblock belongs to Tele2, one of the major ISPs here in Sweden (who in recent years acquired a company called ComHem, one of the major players in residential broadband here).

So I updated clrghouz yesterday as per RFC2308 and included an SOA record with negative hits. This has reduced the queries dramaticaly coming from this net block, so I wont re-enable the block. (Since I have a TTL of 1 day, hopefully those server errors on queries should be gone now.)

I'm still getting queries every minute or so for 21:1/1, 21:1/2 and 21:1/3.

[2023-11-13 07:55:37] production.INFO: PD-:= DNS Query from [::ffff:83.255.224.43] for [_binkp._tcp.f1.n1.z21.fsxnet.nz] {"pid":1690} [2023-11-13 07:56:56] production.INFO: PD-:= DNS Query from [::ffff:83.255.224.35] for [_binkp._tcp.f3.n1.z21.fsxnet.nz] {"pid":1692} [2023-11-13 07:56:58] production.INFO: PD-:= DNS Query from [::ffff:83.255.224.35] for [_binkp._tcp.f3.n1.z21.fsxnet.nz] {"pid":1693}

I'm curious (only because you mentioned you use a DNS server in the 83.255/16 block) - do you have something trying to talk to those hosts? Those servers are querying for those FTNs quite often (and they dont exist).

It appears BIND doesn't like your nameserver configuration:

2023-11-13T11:28:13.722844-08:00 git named[897]: skipping nameserver 'clrghouz.bbs.dege.au' because it is a CNAME, while resolving 'f183.n1.z21.fsxnet.nz/TXT'

https://serverfault.com/questions/822241/bind-recursive-not-resolving-some-domains
--
digital man (rob)

Rush quote #41:
Angels and demons dancing in my head, lunatics and monsters underneath my bed Norco, CA WX: 63.0°F, 37.0% humidity, 0 mph ENE wind, 0.00 inches rain/24hrs --- SBBSecho 3.20-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (21:1/183)

Re: Re: DNS Nodelist available for fsxnet
By: Digital Man to deon on Mon Nov 13 2023 08:06 pm

Howdy,

It appears BIND doesn't like your nameserver configuration:

2023-11-13T11:28:13.722844-08:00 git named[897]: skipping nameserver 'clrghouz.bbs.dege.au' because it is a CNAME, while resolving 'f183.n1.z21.fsxnet.nz/TXT'

Its interesting, because I use bind as well (not authorative for the domains in question), and dont have any trouble. Its probably because my bind forwards to upstream DNSes that handle it OK.

I think this is one of those cases, where the spec was written in 1997 and hasnt modernised to today's use of the internet. I recall great debate about this around 2009, because MX records too shouldnt have CNAMEs and there were a few that had (IMHO) valid opinions of why it can/should. Bind does have an option for it to accept CNAME MX records, havent tested it to see if it accepts CNAME NS records (or there is another override).

The implementation of CNAMEs can be useful in todays hosted and distributed world, and I know many (major?) DNS servers can handle it (evident by the number of queries making it to me).

Anyway, I've asked Paul to change to use my CNAME target for z21 (which does have the A/AAAA records), which will hopefully help those that are seeing the server errors.


...δεσ∩
--- SBBSecho 3.20-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)

Re: Re: DNS Nodelist available for fsxnet
By: deon to Digital Man on Fri Nov 17 2023 02:25 pm

Its interesting, because I use bind as well (not authorative for the domains in question), and dont have any trouble. Its probably because my bind forwards to upstream DNSes that handle it OK.

And I don't have my bind server configured to forward requests.

Anyway, I've asked Paul to change to use my CNAME target for z21 (which does have the A/AAAA records), which will hopefully help those that are seeing the server errors.

Cool. I'll keep an eye out and keep re-testing from here.
--
digital man (rob)

Synchronet/BBS Terminology Definition #38:
GIF = Graphics Interchange Format (pronounced "JIFF")
Norco, CA WX: 57.9°F, 91.0% humidity, 0 mph ENE wind, 0.00 inches rain/24hrs --- SBBSecho 3.20-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (21:1/183)

On 17 Nov 2023 at 02:25p, deon pondered and said...

Anyway, I've asked Paul to change to use my CNAME target for z21 (which does have the A/AAAA records), which will hopefully help those that are seeing the server errors.

apologies, I'm late to this... will act on the request tonight and post here when done :)

Kerr Avon [Blake's 7] 'I'm not expendable, I'm not stupid and I'm not going' avon[at]bbs.nz | bbs.nz | fsxnet.nz

--- Mystic BBS v1.12 A48 (Linux/64)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

On 21 Nov 2023 at 11:58a, Avon pondered and said...

On 17 Nov 2023 at 02:25p, deon pondered and said...

Anyway, I've asked Paul to change to use my CNAME target for z21 (whi does have the A/AAAA records), which will hopefully help those that a seeing the server errors.

apologies, I'm late to this... will act on the request tonight and post here when done :)

..and it's updated now... hopefully this will help with your tests :)

Kerr Avon [Blake's 7] 'I'm not expendable, I'm not stupid and I'm not going' avon[at]bbs.nz | bbs.nz | fsxnet.nz

--- Mystic BBS v1.12 A48 (Linux/64)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

Re: Re: DNS Nodelist available for fsxnet
By: Avon to deon on Tue Nov 21 2023 07:33 pm

Anyway, I've asked Paul to change to use my CNAME target for z21 (whi does have the A/AAAA records), which will hopefully help those that a seeing the server errors.

apologies, I'm late to this... will act on the request tonight and post here when done :)

..and it's updated now... hopefully this will help with your tests :)

It's now working for me:
$ host -t TXT f183.n1.z21.fsxnet.nz
f183.n1.z21.fsxnet.nz descriptive text "Vertrauen BBS"
--
digital man (rob)

Breaking Bad quote #48:
I am not in danger, Skyler. I am the danger. - Walter White
Norco, CA WX: 67.0°F, 47.0% humidity, 1 mph E wind, 0.00 inches rain/24hrs
--- SBBSecho 3.20-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (21:1/183)

On 03 Dec 2023 at 02:38p, Digital Man pondered and said...

..and it's updated now... hopefully this will help with your tests :)

It's now working for me:
$ host -t TXT f183.n1.z21.fsxnet.nz
f183.n1.z21.fsxnet.nz descriptive text "Vertrauen BBS"

Thanks Rob :)

Kerr Avon [Blake's 7] 'I'm not expendable, I'm not stupid and I'm not going' avon[at]bbs.nz | bbs.nz | fsxnet.nz

--- Mystic BBS v1.12 A48 (Linux/64)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)