North American Network Operators Group

Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical

Re: IPv6 reverse lookup - lame delegation?

  • From: Mark Andrews
  • Date: Tue Feb 10 18:55:59 2004

In article <[email protected]> you write:
>
>	if i try to log into my machines back in tokyo by IPv6 SSH, it takes
>	very long time.  i guess i found the reason - (possible) lame delegation
>	of blah.ip6.int.  ip6.arpa. query returns instantly.
>	how could we fix it?
>
>itojun
>
>
>% dig
>e.5.5.e.2.4.e.f.f.f.e.4.5.0.2.0.0.0.0.0.0.0.0.1.0.0.7.3.e.f.f.3.ip6.int.
>ptr
>
>; <<>> DiG 9.2.3 <<>>
>e.5.5.e.2.4.e.f.f.f.e.4.5.0.2.0.0.0.0.0.0.0.0.1.0.0.7.3.e.f.f.3.ip6.int.
>ptr
>;; global options:  printcmd
>;; connection timed out; no servers could be reached
>
>% dig
>e.5.5.e.2.4.e.f.f.f.e.4.5.0.2.0.0.0.0.0.0.0.0.1.0.0.7.3.e.f.f.3.ip6.arpa.
>ptr
>
>; <<>> DiG 9.2.3 <<>>
>e.5.5.e.2.4.e.f.f.f.e.4.5.0.2.0.0.0.0.0.0.0.0.1.0.0.7.3.e.f.f.3.ip6.arpa.
>ptr
>;; global options:  printcmd
>;; Got answer:
>;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 19137
>;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
>
>;; QUESTION SECTION:
>;e.5.5.e.2.4.e.f.f.f.e.4.5.0.2.0.0.0.0.0.0.0.0.1.0.0.7.3.e.f.f.3.ip6.arpa.
>IN PTR
>
>;; AUTHORITY SECTION:
>ip6.arpa.               10569   IN      SOA     dns1.icann.org.
>hostmaster.icann.org. 2003080400 3600 1800 604800 10800
>
>;; Query time: 1 msec
>;; SERVER: 127.0.0.1#53(0.0.0.0)
>;; WHEN: Tue Feb 10 21:57:17 2004
>;; MSG SIZE  rcvd: 151

	The correct fix to this will be to just stop making IP6.INT
	queries.

	The best think that could be done is for the PTB to install
	"IP6.INT. DNAME IP6.ARPA." *now*.  This will allow the legacy
	resolvers to get a answer and allow vendors to stop shipping
	legacy aware resolver in the vague hope that they will get
	a answer from IP6.INT that they didn't get from IP6.ARPA.

	Mark