= phenomenon =
Redirect nspluginwrapper.org to http://nspluginwrapper.davidben.net/ (a new upstream pages).
= reason =
nspluginwrapper.org domain is owned by Red Hat (and managed by Fedora team) and nspluginwrapper project has a new upstream pages. So please redirect nspluginwrapper.org to it.
Do you want a actual redirect from here to there?
Or would you just want us to change DNS to point to 18.181.0.46 ?
Currently, it looks like it's pointed at our load balancer, but there's no setup for it, so it just doesn't load at all as far as I can tell.
18.181.0.46 is scripts.mit.edu so the redirect may be an easiest way.
Well, for us, just changing DNS is much easier. ;)
As far as I can tell there's nothing for this site setup at all, so we would need to setup virtual host configs, setup the redirect, etc. Also, people would see it hit us and load and then reload the real site.
I can do that if you think it's best, but changing DNS is just a lot easier. ;)
If you manage it by simple A DNS record feel free to do it, I really don't care, my DNS knowledge is pretty limited ;) My only concern is that 18.181.0.46 is translated to http://scripts.mit.edu site, not the http://nspluginwrapper.davidben.net/.
For what it's worth, nspluginwrapper.davidben.net currently points to (18.181.0.46) scripts.mit.edu, which suggests that an A record can be made to work. However, the administrator of that site will probably have to add this domain as documented at http://scripts.mit.edu/faq/14/do-cnames-work-with-the-script-service.
Okay, please set the A record and I'll notice http://scripts.mit.edu admins.
Done. Should propigate out soon.
Let us know if there is anything more we can do from here.
Thanks! (Only just found out how to get an account on this thing...)
Could www.nspluginwrapper.org also be pointed to the IP? Probably best to get both working since I think some software likes to prepend www.
Done.
Login to comment on this ticket.