So two issues here since my last post.
First, the nameservers for enigmaconsult.com are pointed to ns181.securenet-server.net and ns180.securenet-server.net. While it is possible to have different nameservers for dev.enigmaconsult.com they don’t seem to be created, and that is an advanced DNS feature not used by many. The purpose of using “*.dreamhosters.com” sub-domain for creating the mirror is because that domain always has dreamhost nameservers. (all dreamhost customers can create sub-domains on dreamhosters.com for this exact purpose.)
Bottom line, your creation of dev.enigmaconsult.com didn’t do anything for you, the DNS for that sub-domain is still controlled elsewhere.
Which brings us to the second issue. In my last post I said:
I probably should have worded that using the I would not use the “mirror” dreamhosters.com method with wordpress.
The problem here is within wordpress. It stores hard links in it’s database. If you use a mirrored domain during setup, like say enigmaconsult_com.dreamhosters.com then all the internal links that WP creates and stores within its database are to enigmaconsult_com.dreamhosters.com instead of just enigmaconsult.com. This leaves you with a cleanup step later on, that you can simply avoid now.
How to do what you are wanting to do: There are two methods to choose between. Either edit your host file on your local computer, OR change your local DNS to use dreamhost nameservers.
Method 1, change your host file: On “manage domains” in the dreamhost panel, you click DNS under the enigmaconsult.com entry. Find the dreamhost generated entries, the first of which is an A-record with an IP address as its value, that IP address is the one you need. Now EDIT the HOSTS file on your local computer, create a record for enigmaconsult.com with that IP address. Now when you visit enigmaconsult.com in YOUR browser your hostfile entry will override internet DNS and you will go to the dreamhost site, rather than be directed to the site everyone else goes to when they type enigmaconsult.com in their browsers.
Method 2, depending on your local setup this method can be either easier or messier than method 1. The idea here is to tell your local system to use dreamhost nameservers instead of your local default nameservers supplied by your ISP. Some people switch to alternative DNS like google’s at 18.104.22.168, the idea here is the same except using dreamhost’s nameservers (22.214.171.124, 126.96.36.199, 188.8.131.52). In general, this is messier for a quick change to a local system. If changing the local computer, method 1 above is simpler and I would recommend that method.
HOWEVER, I have discovered method 2 can be easier IF you can use with your local router (and of course your router is compatible). When I want to use dreamhost nameservers locally what I do is log into my router and change local DNS to use 184.108.40.206, 220.127.116.11, 18.104.22.168 as nameserver for my entire local network. Your mileage may vary here, depending on your local router. In my case, I just change a radio button selection from default to custom OR custom to default and reboot the router. (I set the custom IP’s for the custom nameserver the first time, the router remembers them anyway even when they are deselected). I find this method to be simple and fast for me.