"Grant Taylor" <> wrote in message news:hoh7uv$kj8$...
> Ace Fekay [MVP-DS, MCT] wrote:
>> Read more at my blog...
>>
>> Split Zone or no Split Zone - Can't Access Internal Website with
>> External Name
>> http://msmvps.com/blogs/acefekay/arc...rnal-name.aspx
>
> Nice blog article Ace.
>
> (Sub your own domain in place of "domain.tld".)
>
> Would it also be possible for Ramon to use a deviation of Scenario 2 in
> your article in that a new zone named "www.domain.tld" and use a "blank
> host record" resolving to the internal IP?
>
> This would provide the same effect with out the need or worry about
> "...any and all external records, such as webmail..." likely exist in
> the parent domain "domain.tld".
>
>
>
> Grant. . . .
Thanks, Grant.
Yes, he can do that as well. Essentially if he does create a
www.domain.tld, he is creating a separate namespace. This means that any queries for domain.tld will not be checked against that zone, since they are different. Then just create a blank hostname entry giving it the internal IP.
Even though it will alleviate having to create all the external resources, the only thing is all connections to that address must be done with the www. If attempting to go to
http://domain.tld, it will resolve the external IP. The only way around that is create the domain.tld zone, and create everything outside in it, too.
--
Ace
This posting is provided "AS-IS" with no warranties or guarantees and confers no rights.
Please reply back to the newsgroup or forum for collaboration benefit among responding engineers, and to help others benefit from your resolution.
Ace Fekay, MVP, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE & MCSA 2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer
Microsoft MVP - Directory Services
If you feel this is an urgent issue and require immediate assistance, please contact Microsoft PSS directly. Please check
http://support.microsoft.com for regional support phone numbers.