Archived from groups: microsoft.public.win2000.dns (
More info?)
Hi again,
Maybe it was my mistake on clarifying it. Here it is again.
We have AD domain and internal and external name is the same. I also have
forwardign enabled.
Here is an example:
Right now our AD DNS is abc.com....and we host blah.abc.com on our site
which wokrs fine. (since blah has an internal ip address) but if we were to
point blah.abc.com ip address(Authorative DNS) to different (off site)host ip
....we can't get to it unless we manuanlly enter the ip in the DNS for the
different host.
if this is the case than a failover wouldn't work since our lan dns would
always look for (off site) ip for blah.abc.com.
How can i have the dns setup so blah.abc.com is resolved if is host
internally or externally.
Many thanks again.
sach
"Ace Fekay [MVP]" wrote:
> In news
E6B2BFC-AFB0-4CB1-B7AF-60B29770F05F@microsoft.com,
> sach <sach@discussions.microsoft.com> made this post, which I then commented
> about below:
> > Hello,
> >
> > We have same domain/dns for external and internal called abc.com. I
> > have forwarders enabled to our local ISP dns incase something goes
> > screwy. We have two problems.
> > 1) We have two location a and b. first the host.abc.com points to
> > location a but in a failover situation it is pointed to location b.
> > If location a ever fails our internal user cannot see the location B
> > failover unless the host static entry is entered in to the dns.
>
> Assuming that all DNS servers in your infrastructure have the SAME EXACT
> DATA, and you are using either Primary/Secondary zones or AD Integrated
> zones, then why would you ever need to enter any static entries in DNS??
>
>
> > 2) How can i find out if the forwarders works. Right now
> > host.abc.com is pointed location b.
>
> Are you saying location B has a DNS server that has nothing to do with the
> DNS server in location A?
>
> > It only works if the entry for
> > host is entered in to the dns otherwise it doesn't see it. globally
> > everyones sees it but our LAN.
>
> Globally? Internet you mean?
>
> >
> > Hope this is clear.
>
> Unfortunately, no it is not clear. Do you have AD running? Your AD domain
> name is the same as the external name? If so, the internal DNS would have
> nothing to do with the external DNS. Internally, for example to get to your
> external website, you would create a www record under your internal zone,
> and provide the actual external public IP address. If the website is hosted
> internally for the public, then you would provide the internal private IP
> address.
>
>
> > Many thanks,
> >
> > sach
>
> Maybe if you can elaborate with actual names and describe why you have
> separate DNS servers at each location with separate data, if you have AD,
> etc, that would help us understand your infrastructure.
>
> Thanks,
>
> --
> Regards,
> Ace
>
> If this post is viewed at a non-Microsoft community website, and you were to
> respond to it through that community's website, I may not see your reply.
> Therefore, please direct all replies ONLY to the Microsoft public newsgroup
> this thread originated in so all can benefit.
>
> This posting is provided "AS-IS" with no warranties or guarantees and
> confers no rights.
>
> Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
> Microsoft Windows MVP - Windows Server - Directory Services
> Infinite Diversities in Infinite Combinations.
> =================================
>
>
>
>
>
Facebook
Twitter
Instagram