All Images are Broken when Browsing via NAT64

[wswartzendruber]

None of the images on LucasForums.com seem to show when browsing via a NAT64 connection. This is because each image is sourced using an IPv4 literal, like so:

http://64.20.36.214/lucasforums.com/images/default/lf_menulogo_top.gif

The source of the problem is in bold. Additionally, it also appears that the website's domain name is being appended to the IPv4 address, for whatever reason.

The normal solution to this problem is to replace the IPv4 address with a domain name, allowing things to work with NAT64 connections. It appears, though, that there's something weird going on with how these image URLs are being generated.

Questions are welcome.

EDIT: Linked stylesheets on the main page are also broken, as they are referenced using IPv4 literals.

[stoffe]

Originally Posted by wswartzendruber

None of the images on LucasForums.com seem to show when browsing via a NAT64 connection. This is because each image is sourced using an IPv4 literal, like so:

http://64.20.36.214/lucasforums.com/images/default/lf_menulogo_top.gif

The source of the problem is in bold. Additionally, it also appears that the website's domain name is being appended to the IPv4 address, for whatever reason.

64.20.36.214 is a separate web server used to serve static content such as images, stylesheets and javascript for performance reasons. It does currently not have any domain name associated with it. (The website's domain name is the name of a directory on that server containing the content belonging to a particular site, lucasforums.com in this case.)

[wswartzendruber]

All right then, as long as you're aware of it.

T-Mobile is currently implementing NAT64 for their subscribers. It's possible, though, that they'll filter IPv4 literals out and replace them with synthesized IPv6 ones.

EDIT: I have checked with someone who already has T-Mobile with NAT64, and this website doesn't even load in a timely manner. The HTTP requests for images are timing out because his host doesn't even have an IPv4 address to begin with. It's just that mine's smart enough to immediately fail.