Howdy,

If you wanted to try it, Clearinghouz now answers DNS queries (albeit with limited information).

I'm not sure if I have set it up properly - so if you wanted to play with it, it would help.

My idea is that when querying with a fido DNS name, ie: fXXX.nXXX.zXXX.domain, it returns a CNAME to the BBS (which is the system address field in clearinghouz). User's can update this address, otherwise its populated when I import nodelists.

At the moment, I'm not returning a DNS SRV record - perhaps I should implement that - which is really only important for those systems where BINKP/EMSI is running on non-standard ports. I probably could even provide a "telnet" SRV record, although I dont think any emulators use it?

Anyway, if you wanted to play with it, all you need to do is delegate z1337.erb.pw to clrghouz.bbs.dege.au, ie: clrghouz is the "NS" for that domain, and then you should be able to resolve the systems that clrghouz knows. EG:

EG:
;; ANSWER SECTION:
f101.n2.z1337.erb.pw. 86400 IN CNAME alterant.bbs.dege.au.

(It'll also answer to a fake TLD "ftn" - so f101.n2.z1337.tqwnet.ftn will also work - but that would require everybody updating their local DNS to know about "FTN" - which is probably not doable...)

Anyway, be curious to know if it does work :)


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

On 14 Sep 2023, deon said the following...

If you wanted to try it, Clearinghouz now answers DNS queries (albeit
with limited information).

Wow nice, sounds like fun...

I'm not sure if I have set it up properly - so if you wanted to play
with it, it would help.

Sure I can play.

My idea is that when querying with a fido DNS name, ie: fXXX.nXXX.zXXX.domain, it returns a CNAME to the BBS (which is the
system address field in clearinghouz). User's can update this address, otherwise its populated when I import nodelists.

Very cool, I just tried it with my f101.n1.z1337 and it returned my cname =)

At the moment, I'm not returning a DNS SRV record - perhaps I should implement that - which is really only important for those systems where BINKP/EMSI is running on non-standard ports. I probably could even
provide a "telnet" SRV record, although I dont think any emulators use
it?

Anyway, if you wanted to play with it, all you need to do is delegate z1337.erb.pw to clrghouz.bbs.dege.au, ie: clrghouz is the "NS" for that domain, and then you should be able to resolve the systems that clrghouz knows. EG:

I have done this now;

$ dig -t ns z1337.erb.pw @1.1.1.1 +short
clrghouz.bbs.dege.au.

Looks like it works =)

$ dig -t cname f101.n2.z1337.erb.pw

; <<>> DiG 9.18.12-0ubuntu0.22.04.2-Ubuntu <<>> -t cname f101.n2.z1337.erb.pw ;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 25416
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;f101.n2.z1337.erb.pw. IN CNAME

;; ANSWER SECTION:
f101.n2.z1337.erb.pw. 86400 IN CNAME alterant.bbs.dege.au.

;; Query time: 863 msec
;; SERVER: 192.168.0.240#53(192.168.0.240) (UDP)
;; WHEN: Thu Sep 14 09:55:24 BST 2023
;; MSG SIZE rcvd: 83

---
|14Best regards,
|11Ch|03rist|11ia|15n |11a|03ka |11Me|03aTLoT|11io|15N // @meatlotion:erb.pw

|07── |08[|10eml|08] |15ml@erb.pw |07── |08[|10web|08] |15www.erb.pw |07───┐ |07── |08[|09fsx|08] |1521:1/158 |07── |08[|11tqw|08] |151337:1/101 |07┬──┘ |07── |08[|12rtn|08] |1580:774/81 |07─┬ |08[|14fdn|08] |152:250/5 |07───┘
|07── |08[|10ark|08] |1510:104/2 |07─┘

... When cheese gets its picture taken, what does it say?

--- Mystic BBS v1.12 A48 2022/07/15 (Linux/64)
* Origin: thE qUAntUm wOrmhOlE, rAmsgAtE, uK. bbs.erb.pw (1337:1/101)