ryanczak at arin.net
Tue Jun 13 14:23:09 CEST 2006
We're working with our IPv6 provider to resolve this issue. We have
found that this IPv6 connection is often times not reachable from
various parts of the IPv6 Internet. It does appear that most people have
As for not being reachable over IPv4, I have an idea of what might be
causing this. The IP address for tinnie.arin.net changed last Thursday
do to internal renumbering at ARIN, it should be resolving to
220.127.116.11 for you, but you may be getting 18.104.22.168 because of a
glue record that network solutions inserted into the .net gltd for
tinnie.arin.net. ARIN did not ask for this "service" and we are working
with them to resolve the issue.
On Tue, 2006-06-13 at 01:54 -0700, Doug Barton wrote:
> Rob Shakir wrote:
> > c.22.214.171.124.2.ip6.arpa. 84600 IN NS tinnie.arin.net.
> > c.126.96.36.199.2.ip6.arpa. 84600 IN NS ns.lacnic.net.ip6.arpa.
> Well the lacnic entry is fixed, but tinnie.arin.net is not responding on v4
> or v6, which is bad since it's mentioned in a lot of delegations. Is anyone
> from ARIN on the case?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 191 bytes
Desc: This is a digitally signed message part
Url : http://lists.cluenet.de/pipermail/ipv6-ops/attachments/20060613/26181c6c/attachment.bin
More information about the ipv6-ops