[opensuse] Email, suse, and ipv6 name resolution curiosity.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, 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: cer@nimrodel:~> 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: cer@nimrodel:~> 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. - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFGl+RDtTMYHG2NR9URAsV9AJ90eajQwzA7R+7DnnCPHt7sZJkNagCgiTTx 27b6CjJkuD9QY8LxSkaQ1Iw= =ncLz -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
* Carlos E. R.
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:
cer@nimrodel:~> 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:
cer@nimrodel:~> 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: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
* Patrick Shanahan
- 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 :^)
Then, again.... I probably jump toooooo quickly :^). I agree with your original findings after another Budweiser :^) -- 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: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Friday 2007-07-13 at 17:15 -0400, Patrick Shanahan wrote:
* Patrick Shanahan <> [07-13-07 17:13]:
- 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
Huh? the rDNS should be a name, not an IP.
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 :^)
Then, again.... I probably jump toooooo quickly :^).
I agree with your original findings after another Budweiser :^)
:-) I know almost nothing about ipv6, but I'm curious. I simply copied over the ip address as given on the header, I thought it should be correct syntax, but I don't know. I thought that "::" should mean perhaps "fill with zeroes". Anyway, I tried your way and it fails here: cer@nimrodel:~> host ffff:195.135.221.135 Host ffff:195.135.221.135 not found: 3(NXDOMAIN) So either my local named can't handle it, or upstream they can't (I pull first from my providers, then from the root servers). - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFGmB3mtTMYHG2NR9URAiqQAJ9ltjBW1ocMW8oYRPXZpwHOy+N1gwCfZhR8 zImS4Wd6BTT6SHOR550nZKc= =L3Rh -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Fri, 13 Jul 2007, by robin.listas@telefonica.net:
Hi,
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:
That is not an IPv6 address. IPv6 addresses are written with hex notation, e.g. 2001:888:10:90f::2 i.e. 8193.2184.16.2319.0.0.0.2 when written in decimal. What the meaning is of the '::ffff:' part I don't know, but it has nothing to do with IPv6 afaik. So your analysis has no meaning. theo -- Theo v. Werkhoven Registered Linux user# 99872 http://counter.li.org ICBM 52 13 26N , 4 29 47E. + ICQ: 277217131 SUSE 10.2 + Jabber: muadib@jabber.xs4all.nl Kernel 2.6.20 + See headers for PGP/GPG info. Claimer: any email I receive will become my property. Disclaimers do not apply. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Sunday 2007-07-15 at 01:24 +0200, Theo v. Werkhoven wrote:
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:
That is not an IPv6 address. IPv6 addresses are written with hex notation, e.g. 2001:888:10:90f::2 i.e. 8193.2184.16.2319.0.0.0.2 when written in decimal. What the meaning is of the '::ffff:' part I don't know, but it has nothing to do with IPv6 afaik. So your analysis has no meaning.
Wrong. Ipv6 addresses can be written in several different formats. The "::ffff" part is equivalent to :0:0:0:0:ffff. Further info: http://en.wikipedia.org/wiki/IPv4_mapped_address ] As a special exception to IPv6 addresses notation, IPv4 mapped addresses ] are commonly represented with their last 32 bits notated as an IPv4 ] address. As such, ::ffff:c000:280 would typically be notated ] ::ffff:192.0.2.128 instead. And rfc4291. More proofs: cer@nimrodel:~> 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) See? The host command knows how to read and interpret it, so it is standard notation. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFGmXaStTMYHG2NR9URAkfBAJ94ZtAT/e1UqiElcjF6oLOCFwGdbwCbBcLu fu3zktW1o8mWd1cewR4q4J4= =nG5R -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Sun, 15 Jul 2007, by robin.listas@telefonica.net:
The Sunday 2007-07-15 at 01:24 +0200, Theo v. Werkhoven wrote:
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:
That is not an IPv6 address. IPv6 addresses are written with hex notation, e.g. 2001:888:10:90f::2 i.e. 8193.2184.16.2319.0.0.0.2 when written in decimal. What the meaning is of the '::ffff:' part I don't know, but it has nothing to do with IPv6 afaik. So your analysis has no meaning.
Wrong.
Ipv6 addresses can be written in several different formats. The "::ffff" part is equivalent to :0:0:0:0:ffff.
Right. But there is no valid (public) address range in IPv6 that starts with ::ffff , so this address can never be resolved by an Internet DNS.
cer@nimrodel:~> 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)
See? The host command knows how to read and interpret it, so it is standard notation.
You were right there, but not by trying to reverse resolve it, that's just wrong. Theo -- Theo v. Werkhoven Registered Linux user# 99872 http://counter.li.org ICBM 52 13 26N , 4 29 47E. + ICQ: 277217131 SUSE 10.2 + Jabber: muadib@jabber.xs4all.nl Kernel 2.6.20 + See headers for PGP/GPG info. Claimer: any email I receive will become my property. Disclaimers do not apply. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sunday 15 July 2007 11:52:54 Theo v. Werkhoven wrote:
Right. But there is no valid (public) address range in IPv6 that starts with
::ffff , so this address can never be resolved by an Internet DNS.
Yes there is, that is how ipv4 addresses are mapped into the ipv6 address space. http://www.tcpipguide.com/free/t_IPv6IPv4AddressEmbedding-2.htm -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Theo v. Werkhoven wrote:
Sun, 15 Jul 2007, by robin.listas@telefonica.net:
The Sunday 2007-07-15 at 01:24 +0200, Theo v. Werkhoven wrote:
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:
That is not an IPv6 address. IPv6 addresses are written with hex notation, e.g. 2001:888:10:90f::2 i.e. 8193.2184.16.2319.0.0.0.2 when written in decimal. What the meaning is of the '::ffff:' part I don't know, but it has nothing to do with IPv6 afaik. So your analysis has no meaning.
Wrong.
Ipv6 addresses can be written in several different formats. The "::ffff" part is equivalent to :0:0:0:0:ffff.
Right. But there is no valid (public) address range in IPv6 that starts with ::ffff , so this address can never be resolved by an Internet DNS.
Actually there is, it's called an IPv4 mapped address.
From the IBM TCP/IP Tutorial and Technical Overview redbook"
"IPv4-mapped address (::FFFF:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Sunday 2007-07-15 at 11:52 +0200, Theo v. Werkhoven wrote:
Wrong.
Ipv6 addresses can be written in several different formats. The "::ffff" part is equivalent to :0:0:0:0:ffff.
Right. But there is no valid (public) address range in IPv6 that starts with ::ffff , so this address can never be resolved by an Internet DNS.
cer@nimrodel:~> 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)
See? The host command knows how to read and interpret it, so it is standard notation.
You were right there, but not by trying to reverse resolve it, that's just wrong.
It is an IPv4 address converted to IPv6, so it must be resolvable. In fact, you can see in the header that they resolved it: ] 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; So, if they did, why can't I? That's the question. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFGmgzrtTMYHG2NR9URAn1nAJ4heuLH4eytvz7sdpv8G/XlVRXGVgCfeNt/ blhN8DuV5+/R49AnHpNSH0g= =1EFP -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Theo v. Werkhoven wrote:
Fri, 13 Jul 2007, by robin.listas@telefonica.net:
Hi,
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:
That is not an IPv6 address. IPv6 addresses are written with hex notation, e.g. 2001:888:10:90f::2 i.e. 8193.2184.16.2319.0.0.0.2 when written in decimal. What the meaning is of the '::ffff:' part I don't know, but it has nothing to do with IPv6 afaik. So your analysis has no meaning.
theo
Actually, I believe it is. the :: refers to a continuous block of zeros. It's been a while since I read about it, but I believe the above is the way an IPv4 is expressed as an IPv6 address. -- Use OpenOffice.org http://www.openoffice.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Doesn't anyone learn Hex coding anymore? On Saturday 14 July 2007 19:24, Theo v. Werkhoven wrote:
Fri, 13 Jul 2007, by robin.listas@telefonica.net:
Hi,
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:
That is not an IPv6 address. IPv6 addresses are written with hex notation, e.g. 2001:888:10:90f::2 i.e. 8193.2184.16.2319.0.0.0.2 when written in decimal. What the meaning is of the '::ffff:' part I don't know, but it has nothing to do with IPv6 afaik. So your analysis has no meaning.
theo -- Theo v. Werkhoven Registered Linux user# 99872 http://counter.li.org ICBM 52 13 26N , 4 29 47E. + ICQ: 277217131 SUSE 10.2 + Jabber: muadib@jabber.xs4all.nl Kernel 2.6.20 + See headers for PGP/GPG info. Claimer: any email I receive will become my property. Disclaimers do not apply. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Mon, 16 Jul 2007, by jcmcgil@attglobal.net:
Doesn't anyone learn Hex coding anymore?
Dunno. What about correct quoting? I'm sure anyone can pick that up in less time than it takes to use hex. Theo -- Theo v. Werkhoven Registered Linux user# 99872 http://counter.li.org ICBM 52 13 26N , 4 29 47E. + ICQ: 277217131 SUSE 10.2 + Jabber: muadib@jabber.xs4all.nl Kernel 2.6.20 + See headers for PGP/GPG info. Claimer: any email I receive will become my property. Disclaimers do not apply. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (6)
-
Anders Johansson -
Carlos E. R. -
James Knott -
john -
Patrick Shanahan -
Theo v. Werkhoven