Thanks Joshua, but what about absolute url’s being recorded in the database, and moving a database to another server. How do you keep a knowledge base portable through history.
Ken > On Mar 3, 2016, at 1:45 PM, Joshua Judson Rosen <[email protected]> > wrote: > > On 03/03/2016 12:18 AM, Kenneth Fields wrote: >> Hi, >> My server has both on ipv6 and ipv4 address. >> So it has domain names: anysite.io and ipv6.anysite.io. >> >> If I’m on an ipv6 network, I can surf the site on ipv6.anysite.io >> If I have ipv4, I surf on anysite.io. >> >> Originally, GnuS links were absolute links, so if I post on ipv4, >> the permalink is anysite.io/post. Or my user path is anysite.io/user1 >> >> thus the problem, >> If I am on ipv6 and click on the link, i switch back to being >> on an ipv4 network. That’s not the preferred behaviour I’m looking for. >> >> So we changed all our code to work with relative paths. >> ipv6.anysite.io/user1 >> anysite.io/user1 >> is the same thing. >> >> Am I managing this correctly? > > Why don't you just create an AAAA record in DNS for > the same domain as you have the A record for, > and then let the name resolve in whichever address-space > (IPv4 or IPv6) is appropriate for the client? > > -- > "Don't be afraid to ask (λf.((λx.xx) (λr.f(rr))))."
