Has anyone gotten Ozymandns or NSTX to work? Are they just a cruel hoax
created to fool those of us with little enough DNS knowledge to believe
such a thing is actually possible?
Ozymandns:
$ sudo ./nomde.pl -i 0.0.0.0 metal.modernduck.com
Dealing with ...
couldn't create TCP socket: Invalid argument at
/usr/lib/perl5/Net/DNS/Nameserver.pm line 139
Net::DNS::Nameserver::new('Net::DNS::Nameserver', 'LocalPort',
53, 'ReplyHandler', 'CODE(0x860ec88)', 'Verbose', 2) called at
./nomde.pl line 352
couldn't create nameserver object
creating TCP socket for scjody@boom:~/o$
NSTX:
No errors, but nothing happens. A steady stream of queries can be seen
using tcpdump, even when nothing is running:
00:00:36.475042 IP (tos 0x0, ttl 64, id 1646, offset 0, flags [DF], proto: UDP
(17), length: 87) 192.168.4.1.53 > 205.233.219.236.53: 38626 [1au] TXT? cTaboeR
Hz.metal.modernduck.com. ar: . (59)
00:00:37.474145 IP (tos 0x0, ttl 64, id 561, offset 0, flags [DF], proto: UDP (
17), length: 94) 205.233.219.236.53 > 192.168.4.1.53: 62018* q: TXT? cTabjeSai.
metal.modernduck.com. 1/0/0 cTabjeSai.metal.modernduck.com. (66)
00:00:37.474173 IP (tos 0x0, ttl 64, id 562, offset 0, flags [DF], proto: UDP (
17), length: 94) 205.233.219.236.53 > 192.168.4.1.53: 35152* q: TXT? cTabkeRHz.
metal.modernduck.com. 1/0/0 cTabkeRHz.metal.modernduck.com. (66)
00:00:37.505192 IP (tos 0x0, ttl 64, id 1647, offset 0, flags [DF], proto: UDP (17), length: 87) 192.168.4.1.53 > 205.233.219.236.53: 60870 [1au] TXT? cTabpeR
Hz.metal.modernduck.com. ar: . (59)
Any ideas?
Cheers,
Jody