I would like to move forward with my use of DNN, since starting with next to no knowledge a year ago.

I do run back-ups etc, when updating modules, DNN or anything major... but I've never had a test site.  I want to set this up, as a duplicate of my existing DNN setup (if possible).

Now, I copy the database into a new 'Dev' database... so there are 2 identical databases running so I can leave the live one alone.  I then copy the DNN files into a new 'Dev' directory, and change the web.config file to point to the new 'Dev' database. Is that ok so far?

After that I have setup a new A record (Dev.) for the domain and pointing this to a new IP address, setup as a website in IIS pointing at the new directory (different TCP port).  I also add dev.domain.com to the portal aliases so it should work... my theory anyway.

The problem I have is that it still seems to point to the old site... when I make a change at dev.domain.com it is changing the live site for some reason... not the separate development/testing copy I have made.  Is there something I missed, or a way I can check this?

Thanks

Thanks for that...

I am still struggling with this and I really don't know why.

It still "attacks" the same website.

I started again and I -

1. Created new database (Dev1), restore copy from other into this separate database file
2. Copied all DNN files into a new Dev1 folder
3. Changed the web.config for the Dev1 DNN to point to the Dev1 database
4. In IIS added a website for an unused IP to point to the new DNN Dev1 folder (it said problem as exists, though new folder. Needed diff TCP port to work)
5. Add new A Record for domain (dev1.domain.com to point to the new IP)
6. Changed first PortalAlias entry in table for new Dev1 database to dev1.domain.com, removed others

I think that is everything I have done.  I am guessing the problem is with IIS somehow saying it already exists... why would this be happening?

When I go to dev1.domain.com and modify anything, it changes the www.domain.com although they should be completely separate.

Any help on this would be much appreciated.

Thanks

Ok... not quite there.  Was close to needing urgent help just a minute ago.

Although I got the new DNN Dev1 working... I hadn't realised it pulled down the live website!  I then had problems with the TCP port again in IIS but this time with the original live website, not anything new.

Is it right to think that DNN can only work as a single instance through the same TCP port?  I am fairly new to this, got the basics ok but anything else and as you can see I have to learn and understand.