Suggestion - dedicated IP for ipv4.tunnelbroker.net

[ranpha franboise]

Can I suggest that the URL 'ipv4.tunnelbroker.net' may have its own IPv4 address? Currently, ipv4.tunnelbroker.net resolves to 64.62.200.2. The same IPv4 address is also being used for www.tunnelbroker.net and in fact, if you enter the said IPv4 address on your browser, the main tunnelbroker.net website will be loaded.

As I configured my router (RouterOS) to use only IPv6-only nameservers (the connection itself is capable of IPv4 traffic), I will not be able to update my tunnel with my new (dynamically assigned) IPv4 address with my updater if I were to use http://ipv4.tunnelbroker.net/ipv4_end.php. Using http://64.62.200.2/ipv4_end.php will not work for sure, for the reason mentioned in the paragraph above. If 'ipv4.tunnelbroker.net' has its own IPv4 address, I will be able to update my tunnel purely via the IPv4 address alone with something like http://new-dedicated-IP-address-here/ipv4_end.php, because I will not be able to access my IPv6-only DNS servers (I use Google's) until the tunnel has been updated.

Thanks for the consideration.

[kcochran]

Did you try it before posting?

The three variants of the site are simply pointers into the same content.  Whether you're arriving at www., ipv4., ipv6. or just tunnelbroker.net, it's the same stuff.

[ranpha franboise]

OMG, http://64.62.200.2/ipv4_end.php works!! I thought the website use virtual hosting features, that's why I'm asking.

Thanks.

[kasperd]

As I configured my router (RouterOS) to use only IPv6-only nameservers

I had a bit of a problem understanding what you meant with "IPv6-only nameservers", but I think I get it now. It is not that the nameservers only support IPv6, it is that you configured the client to only use IPv6 for the communication between client and recursive resolver. And that created a cyclic dependency for you in that after your IPv4 address changes you cannot use IPv6 before you have send the update request, and you cannot resolve the servername before you can use IPv6.

Looks like you found a solution that works. If you can tolerate that in the unlikely event that the IPv4 address of the server changes, your connection may be down until you realize this is what has happened and then update your configuration, then you should probably just stick with what you have now.

But there are some alternatives (some of the alternatives may not work with your particular router).
- You could insert the mapping in /etc/hosts or whatever the equivalent is called on your router.
- You could have the router use 74.82.42.42 as the last DNS server after 2001:470:20::2
- You could have a cron job check once per day if the IP address changed (it may not be able to update the router directly, but notifying you would work as well)

If you have some other machine on your network that you keep always online, then I would definitely go for the cron job. The cron job will only fail if both the IPv4 address of the server and your own IPv4 address changes between two runs. If the IPv4 address of the server changes you just need to notice it before your own IPv4 address changes as well. If your router is always online, then both events should be rare enough that the chance of both happening within the same 24 hour window is pretty slim.

[ranpha franboise]

For context- my tunnel is located in Hong Kong.

The main reason why I don't want to use HE anycast nameservers is because that if I go to Google by typing http://www.google.com at the browser's address bar, I will be redirected to Google Hong Kong search page (google.com.hk), which is in Traditional Chinese. I can also opt to use Google Public DNS servers (8.8.8.8 and 8.8.4.4) which means I will be redirected to the correct Google page for my country (google.com.my) but this has the drawbacks of failing the optional DNS test at http://test-ipv6.com/. Only if I use Google Public DNS IPv6 servers (2001:4860:4860::8888 and 2001:4860:4860::8844) everything will be fine.

[kasperd]

I can also opt to use Google Public DNS servers (8.8.8.8 and 8.8.4.4) which means I will be redirected to the correct Google page for my country (google.com.my) but this has the drawbacks of failing the optional DNS test at http://test-ipv6.com/. Only if I use Google Public DNS IPv6 servers (2001:4860:4860::8888 and 2001:4860:4860::8844) everything will be fine.

This doesn't sound right. The Google DNS servers do not have full IPv6 support. If you use the Google DNS servers you should be told about this shortcoming when you visit http://test-ipv6.com/. A score higher than 9/10 is not supposed to be possible using the Google DNS servers, until Google completes the IPv6 support on those DNS servers.