* Carlos E. R. <[EMAIL PROTECTED]> [07-13-07 16:46]: > Last Tuesday I got a delay notice triggered by an email I sent to the list. > That's unimportant, but while looking at it I saw this header: > > Received-SPF: none (Address does not pass the Sender Policy Framework) > SPF=HELO; sender=lists4.suse.de; remoteip=::ffff:195.135.221.135; > remotehost=lists4.suse.de; helo=lists4.suse.de; receiver=exa.billmerriam.com; > > > I noticed the ipv6 address, and I was curious to check who it was: > > [EMAIL PROTECTED]:~> host "::ffff:195.135.221.135" > Host 7.8.d.d.7.8.3.c.f.f.f.f.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa > not found: 3(NXDOMAIN) > > > Huh? > > I then checked the ipv4 part: > > [EMAIL PROTECTED]:~> host 195.135.221.135 > 135.221.135.195.in-addr.arpa domain name pointer lists4.suse.de. > > > Clearly the address does exist. Now, who/what is to blame about the > ipv6 counterpart? Guesses: > > - Linux's 'host' program is not yet ipv6 aware. > - Linux's 'named' daemon is not yet ipv6 aware, or not configured > properly > - Ditto dns servers worldwide, or at suse, not yet ipv6 aware or not > configured properly > - Human (ie, my) error. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
high probability :^) 17:08 wahoo:~ > host ffff:195.135.221.135 ffff:195.135.221.135.wahoo.no-ip.org has address 65.185.141.84 17:09 wahoo:~ > host ::ffff:195.135.221.135 7.8.d.d.7.8.3.c.f.f.f.f.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa.wahoo.no-ip.org has no PTR record have a good day :^) -- Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://counter.li.org -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
