Test domain resolution

[lferran]

In order to test the domain change (.info → .net) we could do something:

1. Add orxonox.net as a hostname entry in the new server, pointing to localhost.
2. Change our working stations DNS resolutions of www.orxonox.net to point to the new server whenever we are working on it.
3. Make all the changes in the configuration, and test this way.

It might be a way to make the migration more "transparent" to the users, or reduce the bunch of time that the old services are down.

This way we could spread the migration in time a bit more (i.e: no need to shut down everyithing for one entire week)

If we would add therese entries in my local resolv.conf to point to the new server's IP… it would work. I haven't tested it though.

[lferran]

How to do it

1. Add aliases for orxonox.net in /etc/hosts of the new server, pointing to its own IP

   37.120.188.187  orxonox.info ... orxonox.net orxonox mail.orxonox.net www.orxonox.net lists.orxonox.net
   

2. Then you can start modifying the configuration of all these services!

3. We might have a problem with reverse lookups!!!

4. On the local computer of the admin, for testing purposes, add the following lines to /etc/hosts to bypass DNS resolution, and make .net point to the new server:

   127.0.0.1       localhost
   127.0.1.1       inspiron
   37.120.188.187  orxonox.net www.orxonox.net lists.orxonox.net svn.orxonox.net
   

[lferran]

References used:

• ​https://rimuhosting.com/knowledgebase/linux/misc/bypassing-dns-servers-using-etc-hosts
• ​http://serverfault.com/questions/520710/bypass-dns-server-lookup-by-using-etc-hosts-when-using-a-dynamic-ip-address

[lferran]

It seems to work We must remove it after migration!!