|
|
Hi all,
Got a problem with a new setup.
I have the following:
domain.com <= Registered, so publically accessible.
Then have the DNS managed for domain.com controlled by the ISP that is
hosting the site, etc. But we also run Server 2008 internally, so have AD
setup with internal dns. The internal is configured as ad.domain.com, and
the office router is setup with a public IP that resolves to ad.domain.com
Now, we have:
domain.com
www.domain.com <= External Web server by ISP
ad.domain.com <= Subdomain that points to the office AD setup
office.domain.com <= This is an alias setup on ISP's DNS that points to
ad.domain.com
Everything works fine, but everyone has gotten used to using
office.domain.com to access the office system externally - but of course
this does not resolve internally. Apart from creating the complete DNS zone
for domain.com (and adding www, mail, etc) is there any way of just
redirecting a single domain (i.e. office.domain.com) in the Server 2008 DNS
system?
Regards,
Andy Neillans
|
|
In news:6685D1C4-A158-4C43-B6DD-921F77FC8F68[ at ]microsoft.com,
Andy Neillans <andy[ at ]neillans.co.uk> requesting assistance, typed the
following:
[Quoted Text] > Hi all,
>
> Got a problem with a new setup.
>
> I have the following:
>
> domain.com <= Registered, so publically accessible.
>
> Then have the DNS managed for domain.com controlled by the ISP that is
> hosting the site, etc. But we also run Server 2008 internally, so
> have AD setup with internal dns. The internal is configured as
> ad.domain.com, and the office router is setup with a public IP that
> resolves to ad.domain.com
> Now, we have:
>
> domain.com
> www.domain.com <= External Web server by ISP
> ad.domain.com <= Subdomain that points to the office AD setup
> office.domain.com <= This is an alias setup on ISP's DNS that
> points to ad.domain.com
>
> Everything works fine, but everyone has gotten used to using
> office.domain.com to access the office system externally - but of
> course this does not resolve internally. Apart from creating the
> complete DNS zone for domain.com (and adding www, mail, etc) is there
> any way of just redirecting a single domain (i.e. office.domain.com)
> in the Server 2008 DNS system?
>
> Regards,
>
> Andy Neillans
Good reason to choose a different internal name than external, such as
domain.local, domain.corp, or domain.internal.
If I understand you correct that office.doamin.com is an internal machine in
your infrastructure, simply provide the internal private IP address.
--
Ace
This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.
Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCT
Microsoft Certified Trainer
For urgent issues, you may want to contact Microsoft PSS directly.
Please check http://support.microsoft.com for regional support phone
numbers.
|
|
[Quoted Text] > Good reason to choose a different internal name than external, such as
> domain.local, domain.corp, or domain.internal.
Indeed! Unfortunatly I can't tear it down now ;)
>
> If I understand you correct that office.doamin.com is an internal machine
> in your infrastructure, simply provide the internal private IP address.
Where do I provide this? Ideally I'd like to effectively posion the DNS
internally only, so that the MS DNS service serves up the private up address
for a few specific hosts - preferably, without having to create a full zone
for the domain.com with references to all the other external servers ... is
this possible?
Andy
|
|
In news:565770F3-1353-447D-B506-318375770C7F[ at ]microsoft.com,
Andy Neillans <andy[ at ]neillans.co.uk> requesting assistance, typed the
following:
[Quoted Text] >> Good reason to choose a different internal name than external, such
>> as domain.local, domain.corp, or domain.internal.
>
> Indeed! Unfortunatly I can't tear it down now ;)
>
>>
>> If I understand you correct that office.doamin.com is an internal
>> machine in your infrastructure, simply provide the internal private
>> IP address.
>
> Where do I provide this? Ideally I'd like to effectively posion the
> DNS internally only, so that the MS DNS service serves up the private
> up address for a few specific hosts - preferably, without having to
> create a full zone for the domain.com with references to all the
> other external servers ... is this possible?
>
> Andy
Well, I know it's not what you want to hear, but yes, it looks like you need
to create the domain.com zone internally and add all the records. The reason
is you are apparently hosting the domain.com services and resources (www,
ftp, mail, etc), internally with private IPs that are being port remapped at
the router from the outside to the inside. However from the inside, if it
resolves to your router's outside address, routers do not have the ability
to provide a "U-Turn" to come back in and proxy the traffic back to an
internal requesting host. This is one of the limitations of hosting
internally, whether with the same name domain or a different name domain.
It's a router/firewall/proxy sever limitation.
btw - How many records are you talking about?
Ace
|
|
|