Internal - External

Scenario

One terminal server
Mobile Users

SBS doing dns

Internal domain .local

External domain .com



Can I create a dns record in the SBS (internal) DNS that points to the
terminal server's internal IP?

I want to be able to configure the client Term.mycompany.com to resolve
externally to the public IP and internally to the private IP

If that is possible does someone have some documentation?
I have been playing with this for awhile and if it is possible need to get
it working.

"slawrie" <> wrote in message news:9688B936-352A-4C29-B3E9-...
> Scenario
>
> One terminal server
> Mobile Users
>
> SBS doing dns
>
> Internal domain .local
>
> External domain .com
>
>
>
> Can I create a dns record in the SBS (internal) DNS that points to the
> terminal server's internal IP?
>
> I want to be able to configure the client Term.mycompany.com to resolve
> externally to the public IP and internally to the private IP
>
> If that is possible does someone have some documentation?
> I have been playing with this for awhile and if it is possible need to get
> it working.


Yes, it is possible. This is a normal solution for a scenario where a public resource is being hosted internally, but internal users can't get to it using the WAN IP address. Routers do not do what some folks call a U-Turn for an internal request to the outside interface, back in again. The only solution is to create the mycompany.com zone internally, create the necessary records, such as your 'term' "A" record, providing the internal private IP.

Also, if you are hosting your own website internally, you can create records for that as well. Keep in mind, that if your public website is hosted externally, you will need to create a www record and providing the public IP of the website to get to it, otherwise with the mycompany.com zone created internally, users will now not be able to resolve it without the www record manually created. If you want them to also get to the mycompany.com website without using the www prefix (such as http://mycompany.com), you also need to create a blank host (A) record as well. Simply right-click, new record, keep the hostname blank, provide the external Ip of your webserver.

I hope that helps.

--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and confers no rights.

Please reply back to the newsgroup/forum to benefit from collaboration among responding engineers, as well as to help others benefit from your resolution.

Ace Fekay, MCT, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSA Messaging
Microsoft Certified Trainer

http://twitter.com/acefekay

For urgent issues, you may want to contact Microsoft PSS directly. Please check http://support.microsoft.com for regional support phone numbers.

On 7/8/2009 4:46 PM, slawrie wrote:
> I want to be able to configure the client Term.mycompany.com to
> resolve externally to the public IP and internally to the private IP

If I'm reading you correct, you want one DNS server to resolve the name
"term.mycompany.com" to one IP address for internal clients and to a
different IP for external clients. Correct?

(I'm presuming that I do understand you correctly.)

In the BIND world, what you are asking for is called "views" and is
possible and trivial to enable. All be it you have two sets (or views)
of the same zone to maintain.

To the best of my knowledge, Microsoft DNS server does not implement views.

I have not needed to do this on a Microsoft DNS server to try various
options. However /if/ you can run two instances of Microsoft's DNS
server bound to different IP and port combinations, you could probably
do this. Have your normal DNS server listening on port 53 serve up your
internal view and your additional DNS server listening on a different
interface and / or port and serve up your external view.



Grant. . . .