#1
|
|||
|
|||
ENET.SYSOP -> R50.SYSOP: Expired DNS Нostnames
Vladimir Fyodorov написал(а) к All в Jan 16 10:28:14 по местному времени:
> Kees van Eeten (2:280/5003) сообщил о том, что в нодлисте уже больше года > находится несколько десятков узлов, чьи имена хостов не возвращают > действующие IP-адреса от DNS. Больше всего таких узлов в R50. Он > обратился к сборщикам нодлистов с просьбой проверить перечисленные узлы > и либо исправить имена хостов, либо удалить их из нодлиста. ============================================================================= * Area : R50.SYSOP * From : Oleg Pevzner, 2:464/5555 (03 Января 2016 21:42) * Subj : Expired DNS Нostnames ============================================================================= ============================================================================= * Forwarded by Oleg Pevzner (2:464/5555) * Area : ENET.SYSOP (ENET.SYSOP) * From : Kees van Eeten, 2:280/5003.4 (Sunday January 03 2016 16:13) * To : Nodelist maintainers * Subj : Expired DNS Нostnames ============================================================================= Нello Nodelist maintainers. In October 2014 I published a list of hostnames used in the Nodelist, that did not return a valid IP addrss from DNS. The respose was host unknown. My stance was that these nodes were no longer active, and their hostnames expired, when some of the dynamic dns services stopped their free service. Some reacted that these nodes were temporarily not available and would be back soon. From that day, I tried to resolve these hostnames daily. After 409 consecutive days I have a list of systems, where sysops and their nethosts have not noticed, that connections cannot be made, based on the contact information in the nodelist. My humble opinion is that these systems do not exist and should be removed from the Nodelits. days Node DNS Нostname DNS resposnse 409 # 2:240/159@fidonet flyerbbs.dyndns.org NXDOMAIN 409 # 2:240/4014@fidonet bagge.dyndns.org NXDOMAIN 409 # 2:2432/223@fidonet donnerhain.dyndns.org NXDOMAIN 409 # 2:2432/260@fidonet oal-fido.no-ip.org NXDOMAIN 409 # 2:2432/363@fidonet dance-system.dyndns.org NXDOMAIN 409 # 2:2437/1@fidonet travelbit.spdns.org NXDOMAIN 409 # 2:2449/7@fidonet ideefix.dyndns.org NXDOMAIN 409 # 2:246/1020@fidonet joschi1.nsupdate.info NXDOMAIN 409 # 2:341/204@fidonet bbs2.vampirebbs.org NXDOMAIN 409 # 2:461/112@fidonet sodin.homeip.net NXDOMAIN 409 # 2:461/155@fidonet avkorop.dyndns.org:443 NXDOMAIN 409 # 2:461/69@fidonet juzy.no-ip.org NXDOMAIN 409 # 2:4635/32@fidonet f32.homedns.org NXDOMAIN 409 # 2:4635/4@fidonet fidovicpryl.dyndns.org NXDOMAIN 409 # 2:4635/78@fidonet darkstranger.dyndns.org NXDOMAIN 409 # 2:465/204@fidonet fido.os.org.ua NXDOMAIN 409 # 2:465/259@fidonet fidolinux.com.ua NXDOMAIN 409 # 2:466/32@fidonet mscan.dyndns.info NXDOMAIN 409 # 2:469/150@fidonet fido.mdl.net NXDOMAIN 409 # 2:5000/10@fidonet f10.n5000.z2.binkp.net NXDOMAIN 409 # 2:5000/114@fidonet f114.n5000.z2.binkp.net NXDOMAIN 409 # 2:5000/13@fidonet f13.n5000.z2.binkp.net NXDOMAIN 409 # 2:5000/27@fidonet f27.n5000.z2.binkp.net NXDOMAIN 409 # 2:5000/83@fidonet f83.n5000.z2.binkp.net NXDOMAIN 409 # 2:5000/8@fidonet f8.n5000.z2.binkp.net NXDOMAIN 409 # 2:5000/95@fidonet f95.n5000.z2.binkp.net NXDOMAIN 409 # 2:5012/0@fidonet fido-kgn.ru NXDOMAIN 409 # 2:5012/200@fidonet fido-kgn.ru NXDOMAIN 409 # 2:50/13@fidonet kocharin.pp.ru NXDOMAIN 409 # 2:5015/120@fidonet hashev.dyndns.org NXDOMAIN 409 # 2:5015/167@fidonet vetka.homeip.net NXDOMAIN 409 # 2:5015/221@fidonet sstd.homeip.net NXDOMAIN 409 # 2:50/1@fidonet newworld715.dyndns.org NXDOMAIN 409 # 2:5020/2395@fidonet tsr-ftn.dtdns.net NXDOMAIN 409 # 2:5020/3904@fidonet fido.rayst.ru NXDOMAIN 409 # 2:5026/16@fidonet fido.gov.ivanovo.ru NXDOMAIN 409 # 2:5030/1488@fidonet maymak.homeip.net NXDOMAIN 409 # 2:5030/519@fidonet dmk.0x6e6d6b.com NXDOMAIN 409 # 2:5030/709@fidonet ftn.spbmed.com NXDOMAIN 409 # 2:5031/25@fidonet bbbbs.mooo.com NXDOMAIN 409 # 2:5031/50@fidonet robot.e-cons.ru NXDOMAIN 409 # 2:5031/7@fidonet shwamp.dyndns.org NXDOMAIN 409 # 2:5045/58@fidonet kraft777.dyndns.org NXDOMAIN 409 # 2:5045/64@fidonet fido.wom.ru NXDOMAIN 409 # 2:5050/13@fidonet fido.ua4wk.ru NXDOMAIN 409 # 2:5050/57@fidonet n505057.dyndns.org NXDOMAIN 409 # 2:5063/89@fidonet dsd-station.servebbs.net NXDOMAIN 409 # 2:5068/58@fidonet f58.n5068.net NXDOMAIN 409 # 2:5080/147@fidonet fido.lotsman.ru NXDOMAIN 409 # 2:5080/201@fidonet 25080201.no-ip.info NXDOMAIN 409 # 2:5080/207@fidonet 25080207.no-ip.org NXDOMAIN 409 # 2:5088/0@fidonet gengen.homelinux.net NXDOMAIN 409 # 2:5088/13@fidonet gengen.homelinux.net NXDOMAIN 409 # 2:5088/50@fidonet fido.g-net.kz NXDOMAIN 409 # 2:5095/95@fidonet tsr-ftn.dtdns.net NXDOMAIN 409 # 2:5097/24@fidonet dk24.no-ip.org NXDOMAIN 409 # 2:6004/1@fidonet rfqa.mine.nu NXDOMAIN 409 # 2:6004/3@fidonet n6004.mine.nu NXDOMAIN 409 # 2:6004/4@fidonet node4.ath.cx NXDOMAIN 409 # 2:6070/35@fidonet alexkim.dyndns.org NXDOMAIN 409 # 2:6078/5@fidonet ua2fga.homelinux.com NXDOMAIN 409 # 2:6078/6@fidonet andreyf1.homelinux.org NXDOMAIN If this is the situation, where connects can easily be checked, I fear for the quality of the Nodelist with respect to POST only nodes. There really should be more checks and balances in the process of being listed in the Nodelist. Now people just leave, often after a system crash or computer upgrade, with no means to notify their NC or RC and remain listed forever. Please check the above nodes listed in the current Nodelist and correct the listed hostnames, or remove the the nodes altogether, if it prooves that these nodes klosed down. Kees -+- GoldED+/LNX 1.1.5 + Origin: As for me, all I know is that, I know nothing. (2:280/5003.4) ============================================================================= Нello All! Обращаю внимание всех, кого затрагивает эта информация. WBR, Oleg Sunday January 03 2016 ============================================================================= --- GoldED+/W64-MSVC 1.1.5-b20151130 |