asked on How to set up an internal DNS zone for a single public domain DNS address
Greetings,
I have a client on a Windows 2012 server domain, which includes a Windows 2012 DC that is also running Exchange 2013 Standard. The client has a regular external domain for its web site, call it mycompany.com., with their website at www.mycompany.com The Active Directory DNS name for the internal company network is mynetwork.com, so the server that is the DC + Exchange 2013 server has an internal DNS name of exchange1.mynetwork.com. The internal IP address of the DC / Exchange server is 192.168.1.10. In the DNS records for mycompany.com, I've set up an A record of web1.mycompany.com that corresponds to the public IP address of the exchange server in order to provide iPhone email and OWA access. Company iPhones are set up to access their email using web1.mycompany.com as the server. This works fine when users are outside the office, and they can access web1.mycompany.com from their iPhones. The problem I'm facing is how to give users iPhone access to their email when they're inside the office and using the internal wifi. The wireless units get their DNS from either the DC or from the local ISP, but either way, it's not possible for web1.mycompany.com to resolve properly to the Exchange server when in the office. As a test, I added a new Forwarding Zone to the DNS running on the DC for mycompany.com, and after adding an A record for web1.mycompany.com with an IP address of 192.168.1.10 to that DNS zone, my iPhone was able to resolve to get its email at web1.mycompany.com, but as you can figure, it also messed up being able to get to the company website www.mycompany.com when browsing from any PC within the office. I'm guessing I could modify the wireless units with something similar to a hosts file entry where web1.mycompany.com resolves to 192.168.1.10 but I'd prefer to do this by properly modifying the DNS on the DC, and the wireless units would then pull the DNS from the DC. Can someone please provide the steps involved or a web link to how to do this? Thanks in advance for your assistance.
I have a client on a Windows 2012 server domain, which includes a Windows 2012 DC that is also running Exchange 2013 Standard. The client has a regular external domain for its web site, call it mycompany.com., with their website at www.mycompany.com The Active Directory DNS name for the internal company network is mynetwork.com, so the server that is the DC + Exchange 2013 server has an internal DNS name of exchange1.mynetwork.com. The internal IP address of the DC / Exchange server is 192.168.1.10. In the DNS records for mycompany.com, I've set up an A record of web1.mycompany.com that corresponds to the public IP address of the exchange server in order to provide iPhone email and OWA access. Company iPhones are set up to access their email using web1.mycompany.com as the server. This works fine when users are outside the office, and they can access web1.mycompany.com from their iPhones. The problem I'm facing is how to give users iPhone access to their email when they're inside the office and using the internal wifi. The wireless units get their DNS from either the DC or from the local ISP, but either way, it's not possible for web1.mycompany.com to resolve properly to the Exchange server when in the office. As a test, I added a new Forwarding Zone to the DNS running on the DC for mycompany.com, and after adding an A record for web1.mycompany.com with an IP address of 192.168.1.10 to that DNS zone, my iPhone was able to resolve to get its email at web1.mycompany.com, but as you can figure, it also messed up being able to get to the company website www.mycompany.com when browsing from any PC within the office. I'm guessing I could modify the wireless units with something similar to a hosts file entry where web1.mycompany.com resolves to 192.168.1.10 but I'd prefer to do this by properly modifying the DNS on the DC, and the wireless units would then pull the DNS from the DC. Can someone please provide the steps involved or a web link to how to do this? Thanks in advance for your assistance.
DNSWireless Networking
Last Comment
jkirman
SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
I like this solution as well. Never heard of ot to be honest.
For my understanding the trick here is simply add zone web01 with only a no named A record pointing to the Exchange server IP-adres and all other queries will be forwarded normally?!
For my understanding the trick here is simply add zone web01 with only a no named A record pointing to the Exchange server IP-adres and all other queries will be forwarded normally?!
ASKER
Patricksr1972, here's what I did:
1) added a Forward Lookup Zone called web1.mycompany.com
2) added an A record with:
- no name
- IP address of 192.168.1.10
That was it. By leaving the name blank, it defaults to "(same as parent folder)". So internal DNS inquiries to web1.mycompany.com will resolve to the Exchange server, but any other inquiries to mycompany.com will be handled via the main server and will be forwarded to DNS forwarders and/or root hints.
1) added a Forward Lookup Zone called web1.mycompany.com
2) added an A record with:
- no name
- IP address of 192.168.1.10
That was it. By leaving the name blank, it defaults to "(same as parent folder)". So internal DNS inquiries to web1.mycompany.com will resolve to the Exchange server, but any other inquiries to mycompany.com will be handled via the main server and will be forwarded to DNS forwarders and/or root hints.
Cheers!