Are you talking about your "internal" domain, or your "external" one when
you said "domain. The internal domain and its AD/DNS functionalities should
be "internal", meaning that you shouldn't be using IP addresses provided by
any ISP. Of course, you CAN use publicly routable IP (provided by ISPs), but
I would not encourage that.
So, if you are talking about internal, and you agree that a private IP
scheme is OK, with you, then you shouldn't have to rely on your ISP for that
part of your configuration. IF your internal and external domain names are
the same, then you will have your provider (ISP) host the EXTERNAL part,
which will have public IPs for the records you want to make available
externally. You will host your own INTERNAL DNS servers for the internal
records that should not be accessible externally, and these will be all
private IPs.
This configuration is what is known as the "Split Brain DNS" config.
I hope I have not misinterpreted your needs.
Deji
"Maxxsir" <Maxxsir[ at ]discussions.microsoft.com> wrote in message
news:17868CAB-CC77-4C96-8618-737B52143A76[ at ]microsoft.com...
[Quoted Text] > We are moving to IP Flex Reach for VOIP and our WAN. My ISP is providing a
> block of IP addresses for each location but they say they will not provide
> DNS addresses for those IP's unless they are hosting our domain. Does this
> sound right?
>
> We have a T1 with this same ISP and that T1 does have DNS with the IP's.
>
> My question is what do I need to do to get DNS working with these new IP
> addresses? Do I need to use a custom DNS provider? I have two AD servers
> at
> each location and I don't want to just use any DNS servers and then they
> fail?
> --
> Maxxsir
|