Hello All!

I am wondering if anyone knows why this happens? Its not all the time but the same node always? It has a node statement, address correct etc...

11:01 [31401] call to 1:105/11@fidonet
+ 11:01 [31401] getaddrinfo failed: Name or service not known (-2)
11:01 [31400] rc(31401)=0

Regards,

Rick

... Co-ed naked BBSing -- We make constant connections!
--- GoldED+/LNX 1.1.5-b20180707
* Origin: Awesome Net- Oregon FTN Hub - www.awesomenet.us (1:105/81)

Hello, Rick!

Sunday March 17 2024 11:01, from Rick Smith -> All:

I am wondering if anyone knows why this happens? Its not all the time
but the same node always? It has a node statement, address correct
etc...

11:01 [31401] call to 1:105/11@fidonet
+ 11:01 [31401] getaddrinfo failed: Name or service not known (-2)
11:01 [31400] rc(31401)=0

Increase the *loglevel* and it might give you more info.

Best Regards, Nil
--- GoldED+/LNX 1.1.5-b20240306
* Origin: FidoNet member since 1995 (1:16/101)

Hello Rick,

Sunday March 17 2024, Rick Smith wrote to All:

I am wondering if anyone knows why this happens? Its not all the time
but the same node always? It has a node statement, address correct
etc...

11:01 [31401] call to 1:105/11@fidonet
+ 11:01 [31401] getaddrinfo failed: Name or service not known (-2)
11:01 [31400] rc(31401)=0

Your wh2bbs.us domain has an A record:

$ dig a wh2bbs.us

; <<>> DiG 9.18.24 <<>> a wh2bbs.us
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 62766
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;wh2bbs.us. IN A

;; ANSWER SECTION:
wh2bbs.us. 600 IN A 65.102.14.166

;; Query time: 47 msec
;; SERVER: 127.0.0.53#53(127.0.0.53) (UDP)
;; WHEN: Sun Mar 17 22:49:23 MSK 2024
;; MSG SIZE rcvd: 54

But it looks like your bbs.wh2bbs.us domain does not have such a record, and it should have one.

$ dig a bbs.wh2bbs.us

; <<>> DiG 9.18.24 <<>> a bbs.wh2bbs.us
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 25605
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;bbs.wh2bbs.us. IN A

;; AUTHORITY SECTION:
wh2bbs.us. 1653 IN SOA curitiba.ns.porkbun.com. dns.cloudflare.com. 2335454762 10000 2400 604800 1800

;; Query time: 0 msec
;; SERVER: 127.0.0.53#53(127.0.0.53) (UDP)
;; WHEN: Sun Mar 17 22:46:12 MSK 2024
;; MSG SIZE rcvd: 116

Michael

... node (at) f1042 (dot) ru
--- GoldED+/LNX 1.1.5-b20231008
* Origin: Moscow, Russia (2:5020/1042)

Rick Smith wrote to All <=-

Hello All!

I am wondering if anyone knows why this happens? Its not all the
time but the same node always? It has a node statement, address
correct etc...

11:01 [31401] call to 1:105/11@fidonet
+ 11:01 [31401] getaddrinfo failed: Name or service not known
(-2)
11:01 [31400] rc(31401)=0

Something wrong with the DNS configuration for that hostname.



... A house is a place to keep your stuff while you go out and get more stuff. === MultiMail/Linux v0.52
--- SBBSecho 3.20-Linux
* Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (1:135/115)

Hello Michael!

Sunday March 17 2024 23:05, you wrote to me:

Hello Rick,

Sunday March 17 2024, Rick Smith wrote to All:

I am wondering if anyone knows why this happens? Its not all the
time but the same node always? It has a node statement, address
correct etc...

It does lead me to another ? tho. I had a nodestatement for that node that just had wh2bbs.us but binkd was trying bbs.wh2bbs.us? So it makes me wonder if I had a node statement in binkd.cfg why did it use the nodelist instead of that node statement?

Regards,

Rick

... YKYHW: You consider BBSing better than sex.
--- GoldED+/LNX 1.1.5-b20180707
* Origin: Awesome Net- Oregon FTN Hub - www.awesomenet.us (1:105/81)

Hello Rick,

Monday March 18 2024, Rick Smith wrote to Michael Dukelsky:

I am wondering if anyone knows why this happens? Its not all the
time but the same node always? It has a node statement, address
correct etc...

It does lead me to another ? tho. I had a nodestatement for that node that just had wh2bbs.us but binkd was trying bbs.wh2bbs.us? So it
makes me wonder if I had a node statement in binkd.cfg why did it use
the nodelist instead of that node statement?

Do you use nodelist.pl in your binkd.cfg? Or maybe you have a different binkd.cfg with bbs.wh2bbs.us in it and sometimes you start binkd with that binkd.cfg? Try to find the second configuration:

sudo updatedb
locate binkd

Michael

... node (at) f1042 (dot) ru
--- GoldED+/LNX 1.1.5-b20231008
* Origin: Moscow, Russia (2:5020/1042)

Greetings Michael!

Tuesday March 19 2024 10:16, you wrote to me about an urgent matter!:

* Forwarded from area 'BINKD'
Hello Rick,

Monday March 18 2024, Rick Smith wrote to Michael Dukelsky:

I am wondering if anyone knows why this happens? Its not all
the time but the same node always? It has a node statement,
address correct etc...

It does lead me to another ? tho. I had a nodestatement for that
node that just had wh2bbs.us but binkd was trying bbs.wh2bbs.us?
So it makes me wonder if I had a node statement in binkd.cfg why
did it use the nodelist instead of that node statement?

Do you use nodelist.pl in your binkd.cfg? Or maybe you have a
different binkd.cfg with bbs.wh2bbs.us in it and sometimes you start
binkd with that binkd.cfg? Try to find the second configuration:

I do use binkd style nodelist so in my binkd.cfg I have all of my node statements and after the node statements I have an include for the nodelist. So does binkd read the nodelist before the node statements?

----
Regards,


Rick Smith (Nitro)

... Sleep... The thing "some" SysOps go without, cuz BBSing is too fun;-)
--- GoldED+/LNX 1.1.5-b20180707
* Origin: ----> Abacus BBS! --->>>>bbs.abon.us:2323 (1:105/10)

Hello Nil!

17 Mar 2024 14:50, Nil Alexandrov wrote to Rick Smith:

11:01 [31401] call to 1:105/11@fidonet
+ 11:01 [31401] getaddrinfo failed: Name or service not known (-2)
11:01 [31400] rc(31401)=0

Increase the *loglevel* and it might give you more info.

means dns is either not working or node is have hostname that have no ip in dns


Regards Benny

... too late to die young :)

--- Msged/LNX 6.1.2 (Linux/6.9.3-gentoo-dist (x86_64))
* Origin: gopher://fido.junc.eu/ (2:230/0)