Re: Nameserver scenario with advertisers and resolvers
- From: "ACE-Joe" <ACEJoe@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 23 Aug 2005 08:47:44 -0700
Sorry, but here is another question, if I have my resolvers setup correctly,
which I do, I setup forwarders to the public DNS servers of our ISP, and left
the root hints. Now when I setup my internal DNS servers to query my
resolvers, what configuration should I use for internal DNS? Should I
disable root hints? And exclusively use the forwarders?
Thanks
Joe
"Ace Fekay [MVP]" wrote:
> In news:4AEEF246-7E02-487B-AC72-B7DCE559422A@xxxxxxxxxxxxx,
> ACE-Joe <ACEJoe@xxxxxxxxxxxxxxxxxxxxxxxxx> made this post, which I then
> commented about below:
> > Hi all,
> >
> > If I am going to setup a DMZ with two main DNS servers in a
> > Primary/Secondary configuration, but also use 2 advertisers and 2
> > resolvers on separate servers, how do I setup the NS records and
> > basic DNS configuration? I.E. I have 6 test domains registered. I
> > want to setup the nameservers to point to the DNS servers in my DMZ.
> > But do I setup nameservers for each of the servers including the
> > advertisers/resolvers? Any general configuration tips or suggestions
> > here? I'm not very familiar with this type of configuration.
> >
> > Thanks
> > Joe
>
> Still at it? :-)
>
> Keep in mind, the advertiser is the machine that will be hosting your public
> records for your clients and the Internet. The nameserver records on these
> machines are these machines' nameserver FQDN and IP addresses, since they
> are the machines regstered as the nameservers for your external domain name
> when you registered them or changed them to. That's important. Keep in mind
> as well, they do not have any references to the internal domain whatsoever.
> If you put the internal domain data on them, it will 'lame' them. Your
> internal DNS have nothing to do with these guys. The only thing on the
> internal DNS is to create shadow copies of resources (www, ftp, etc) to
> either the external IPs or the internal private IPs, depending on where the
> webserver or ftp server, etc, are being hosted.
>
> The resolver will be the ones that are being used as a forwardee from the
> internal DNS servers. The resolver, as far as the public is concerned, do
> not exist to them. The nameserver records on them do not matter.
>
> Both will be sitting on your DMZ. The internal DNS will have forwarding set
> to the 'resolver' which in turn will resolve external names by forwarding to
> some external server.
>
> --
> Regards,
> Ace
>
> Please direct all replies ONLY to the Microsoft public newsgroups
> 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.
> =================================
>
>
>
>
.
- Follow-Ups:
- References:
- Nameserver scenario with advertisers and resolvers
- From: ACE-Joe
- Re: Nameserver scenario with advertisers and resolvers
- From: Ace Fekay [MVP]
- Nameserver scenario with advertisers and resolvers
- Prev by Date: Re: Nameserver scenario with advertisers and resolvers
- Next by Date: Re: RDNS LOOPING
- Previous by thread: Re: Nameserver scenario with advertisers and resolvers
- Next by thread: Re: Nameserver scenario with advertisers and resolvers - Solution Sum
- Index(es):
Relevant Pages
|
Loading
