Just a sample of the Echomail archive
[ << oldest | < older | list | newer > | newest >> ]
|  Message 8352  |
|  Rick Smith to Oli  |
|  error getting address  |
|  25 Feb 23 10:10:56  |
 REPLY: 2:280/464.47 63f9cbfe MSGID: 1:105/81@fidonet 63fa4f4e CHRS: UTF-8 2 TZUTC: -0800 Hello Oli! Saturday February 25 2023 09:51, you wrote to me: Ol> * Forwarded from area 'BINKD' Ol> Rick wrote (2023-02-24): RS>> Hello All! RS>> I have noticed on my hub that one of my BBS's can not be polled, RS>> I havent made any changes at all to that setup here is whats RS>> showing in binkd.log RS>> 1:105/85 RS>> 07:29 [33121] BEGIN, binkd/1.1a-115/Linux -p -P1:105/85 RS>> /etc/ftn/binkd.cfg 07:29 [33121] creating a poll for RS>> 1:105/85@fidonet (`d' flavour) 07:29 [33121] clientmgr started $ RS>> -d 1:105/85@fidonet + 07:29 [33122] call to 1:105/85@fidonet + RS>> 07:29 [33122] getaddrinfo failed: No address associated with RS>> hostname (-5) 07:29 [33121] rc(33122)=0 RS>> 07:29 [33121] the queue is empty, quitting... RS>> I have verified all address's in binkd.cfg and the nodelist etc. RS>> I tried changing from fqdn to local ip in binkd.cfg it does not RS>> change the error. RS>> Any ideas? Ol> Is it still a problem? I can poll 1:105/85. Maybe a (temporary) DNS Ol> problem? oddly it just resolved. So I would say it was some sort of a DNS problem Regards, Rick ... To go where no man has gone before... BBSing! --- GoldED+/LNX 1.1.5-b20220504 * Origin: Awesome Net- Oregon FTN Hub - www.awesomenet.us (1:105/81) SEEN-BY: 1/123 15/0 90/1 105/7 10 11 44 81 85 500 106/201 114/709 SEEN-BY: 123/131 129/305 153/7715 218/700 226/30 227/114 229/111 112 SEEN-BY: 229/113 200 206 307 317 424 426 428 470 550 664 700 266/512 SEEN-BY: 282/1038 292/854 317/3 320/219 322/757 342/200 396/45 633/280 SEEN-BY: 712/848 PATH: 105/81 229/426 |
[ << oldest | < older | list | newer > | newest >> ]