Reverse DNS on noosl01
Shadow Hawkins on Monday, 15 September 2008 13:01:42
Hi
It seems that the authoritative servers for the zone 8.d.6.1.1.0.0.2.ip6.arpa. are not v6-connected.
;; ANSWER SECTION:
8.d.6.1.1.0.0.2.ip6.arpa. 60 IN SOA ns1.q.port80.se. registry.port80.se. 2008091001 21600 3600 1209600 86400
;; AUTHORITY SECTION:
8.d.6.1.1.0.0.2.ip6.arpa. 2419200 IN NS ns1.q.port80.se.
8.d.6.1.1.0.0.2.ip6.arpa. 2419200 IN NS ns2.q.port80.se.
8.d.6.1.1.0.0.2.ip6.arpa. 2419200 IN NS ns3.q.p80.net.
8.d.6.1.1.0.0.2.ip6.arpa. 2419200 IN NS ns4.q.p80.net.
;; ADDITIONAL SECTION:
ns1.q.port80.se. 1814400 IN A 217.75.109.220
ns2.q.port80.se. 600 IN A 82.96.2.250
ns3.q.p80.net. 600 IN A 82.96.9.250
ns4.q.p80.net. 600 IN A 82.96.8.250
Is it worth emailing them about it?
Reverse DNS on noosl01
Jeroen Massar on Monday, 15 September 2008 13:09:56
That is the case for most ISPs, even the ones participating in SixXS.
As there is no root IPv6 glue anyway, this does not matter.
Next to the fact that you have IPv4 simply because of the fact that you are taking a tunnel, which goes over IPv4; thus you can resolve any issue with this by simply NATting IPv4 and doing native (well tunneled, but not translated :) IPv6.
Having a local IPv4/IPv6 connected resolver is anyways a good thing. I can't claim that you are unable to use Google anymore (actually, they don't have IPv6 records for their nameservers, nor their load-balancer either, thus you would not be able to reach them IPv6 only), but there are a lot of resources on the Internet you could not reach anymore; now the moment you include an IPv6/IPv4 proxy, that thing can do the resolving also for you, thus problem resolved again.
Posting is only allowed when you are logged in. |