Domain Rename -- Can I just remove and reinstall my entire Exchange Server?

AmongTheChosenX

Supreme [H]ardness
Joined
Sep 24, 2007
Messages
7,151
I have an Exchange server at home that I set up for partial use, but didn't really use -- it was just for a lab configuration.

Long story short, I finally acquired Dynamic DNS for my domain name (atozcc.net) via No IP Services, except now I'm realizing that my internal domain name (also atozcc.net) is causing lookup issues from home, so now I need to revert the domain name to atozcc.int or atozcc.local

Was planning on following this guide (since he is also using Server 2012), but I see minimal mentions on the web about the Exchange Server simply being able to be uninstalled and reinstalled on the new domain.

https://mizitechinfo.wordpress.com/...to-rename-domain-name-in-windows-server-2012/

Insight would be appreciated.

Thanks,

Adam
 
I was going to suggest Split brain DNS as well. Have your internal clients use your internal DNS, and external clients use No IP Services. Just make sure that you enter each DNS entry in both locations.

Examples (Note, only DNS entries, ports are done via firewall rules) :
Internally hosted system with Firewall holes:
smtp.atozcc.net (Internal) A Record = 192.168.1.5
smtp.atozcc.net (external) A Record = 68.254.36.112

Externally hosted website:
www.atozcc.net (internal) CNAME = site55.webhost.net
www.atozcc.net (external) CNAME = site55.webhost.net

So internal DNS records would be on your Domain Controller, and external records would be on No IP's servers.

Does that make sense?
 
You cannot change a domain name when exchange is installed. Exchange will cease to function after the domain rename and subsequent dual reboots. The best option is to use a split dns by simply adding the A records for www etc to point to the external IP of your website and mail point to your internal IP of the exchange server. Have the mail clients point to mail. or whatever your SSL certificate reads and it will work internally and externally.

Unfortunately, the only way to rename your domain when exchange is involved is to build a new domain and do a cross forest migration. Not worth in your instance nor is it required. Trust me when I say that it's so important to think carefully when creating your internal domain name.
 
You cannot change a domain name when exchange is installed. Exchange will cease to function after the domain rename and subsequent dual reboots. The best option is to use a split dns by simply adding the A records for www etc to point to the external IP of your website and mail point to your internal IP of the exchange server. Have the mail clients point to mail. or whatever your SSL certificate reads and it will work internally and externally.

Unfortunately, the only way to rename your domain when exchange is involved is to build a new domain and do a cross forest migration. Not worth in your instance nor is it required. Trust me when I say that it's so important to think carefully when creating your internal domain name.

The problem is that I have dynamic IP, which means that anytime I need something to go out using a www. record and my IP has changed, it's going to fail... The idea is that this can be autonomous... Whether I'm inside or outside my network, Atozcc.net will always go to the internet, while atozcc.int will stay inside...

The other problem is I have other services that are using alternate HTTPS ports. Since I only have one IP address, I have to use Web Redirects (for instance, owncloud.atozcc.net will need to redirect to "https://atozcc.net:8443/owncloud"). If owncloud could run without :8443/owncloud then split brain DNS would work. Since I don't have this ability, it becomes an issue.

I suppose I could rectify this by implementing a router that will do port translation (for instance, traffic going to specific internal host would be redirect to port 8443 internally), but now I'm into buying hardware which I'm trying to avoid.

I have no other way to configure my OwnCloud on the network, so my best bet is to rename the domain at this point--especially since I don't actually need the Exchange server in it's current configuration (there is no mail on it that is necessary). I could feasibly remove and reinstall Exchange without any issues.

Thoughts on this?

EDIT: I'm in the process of removing Exchange 2013 completely right now. Ran the prerequisites to uninstall the database. Once it's removed, I'm either going to use the rendom utility, or I'm going to manually create a new forest and domain and migrate all files and computers accordingly.
 
Last edited:
Trust me when I say that it's so important to think carefully when creating your internal domain name.

QFT.

Ran into many scenarios when it was never thought through and then something like this happened. One guy even renamed the domain and the mail server went null. When i was brought in the news I gave made heads hit the table.
 
QFT.

Ran into many scenarios when it was never thought through and then something like this happened. One guy even renamed the domain and the mail server went null. When i was brought in the news I gave made heads hit the table.

Jesus, that's scary crap...

The reason for this problem in the first place was that I had my domain originally set to ATOZCC.LOCAL, which was fine, except I screwed up the Exchange server I had set up, so in the middle of this I decided to rebuild my entire home server infrastructure, which led me to setting the new domain name to ATOZCC.NET (because HEY, Why shouldn't it match my internet domain name?!).... I didn't think about the issue of not only have only 1 IP address, but also that Dynamic DNS for an internet domain would cause such incompatibilities...

So yeah, it's pretty frustrating.

Exchange has been removed. I'm going to use this guide I found to rename the domain:

https://mizitechinfo.wordpress.com/...to-rename-domain-name-in-windows-server-2012/

After taking a backup, of course. LOL
 
Back
Top