Re: Windows 2003 DNS & QIP DNS (Reverse Lookup)

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Joe Flynn (JoeFlynn_at_discussions.microsoft.com)
Date: 12/01/04 

Date: Wed, 1 Dec 2004 04:33:07 -0800

Can you possibly tell me why you would recommend using QIP for DNS. I am
siding with you here but our "Standards" group will sure ask me why I comment
that I want to keep windows.

"Herb Martin" wrote:

> "Joe Flynn" <JoeFlynn@discussions.microsoft.com> wrote in message
> news:3D5BB7A0-DDB4-4735-98AE-692F76B6B24A@microsoft.com...
> > My domain structure consist of 15 sites and about 29 domain controllers.
> > This is a nationwide domain. We use QIP for enterprise DNS because of all
> > the UNIX hardware. My Enterpise DNS admin wants to integrate the Windows
> DNS
> > with QIP but I was not sure of the issues with that.
>
> Don't do it. Even though it is technically doable, you will
> be very unhappy over time if you don't use a Windows DNS
> server (set) for your AD DNS support zone(s.)
>
> If you Unix admins are adamant and you share a zone then
> you should ask them to DELEGATE you a child zone for
> Windows -- if you already have your Windows 2000+ domains
> it is too late to do this.
>
>
> > Do you recommend I do
> > that to resolve the Reverse Lookup problem I am having between os platform
> > and dns....
>
> No. If you can get the admins to make the QIP dynamic
> then you should be fine, as long as you DHCP (and other
> clients) can resolve the QIP-held reverse zones (mostly
> a recursion or fowarding issue).
>
> My bet is you don't have resolution working for all possible
> forward and reverse zones.
>
> Also note: There is NO technical relationship between a
> forward and a reverse zone. (All such relationships are
> by human convention.)
>
>
> --
> Herb Martin
>
>
> >
> > "Steve Duff [MVP]" wrote:
> >
> > > With any non-Windows DNS Server, you have no
> > > participation in AD replication at all. AD will (and
> > > must) still update the QIP server through DDNS.
> > >
> > > The QIP servers must be configured to accept
> > > dynamic updates from your network, and must be
> > > configured to accept extended name syntax. Other
> > > than that, no real issues.
> > >
> > > The lack of AD replication for DNS is not usually
> > > much of a problem unless your site is very large or
> > > you have a complex domain topology. With one
> > > DNS server and DC, it becomes almost a non-issue.
> > >
> > > Steve Duff, MCSE, MVP
> > > Ergodic Systems, Inc.
> > >
> > > "Joe Flynn" <JoeFlynn@discussions.microsoft.com> wrote in message
> news:CA2931AF-44A5-446C-A2D4-A3E8572A67A8@microsoft.com...
> > > > Steve
> > > >
> > > > What else would i loose if I went to QIP DNS. Would I have any issues
> with
> > > > AD replication or anything like that.
> > > >
> > > > "Steve Duff [MVP]" wrote:
> > > >
> > > >> Your configuration kind of spells trouble. You need to decide
> > > >> which DNS you want to use, and take out the secondary. QIP/BIND
> > > >> cannot participate in AD multi-master replication, so there is
> > > >> no 'two-way' street you can setup that will insure that DDNS updates
> > > >> made to either server get propagated reliably to the other.
> > > >>
> > > >> If your Windows machines are on their own subnet, I'd suggest
> > > >> you consider using your Windows DNS as the primary (and only)
> > > >> DNS for those machines, and then place a delegation on the QIP
> > > >> farm for that reverse subnet and the zone. (A classless reverse
> > > >> is a little more work, but can be done.) Alternatively you can
> > > >> setup QIP as a secondary and perform zone pulls from the
> > > >> Windows DNS.
> > > >>
> > > >> As long as you configure the QIP servers to accept extended
> > > >> syntax on the names, you are free to use that server for all DNS
> > > >> and turn off Windows Server DNS entirely. You lose AD-integration/
> > > >> replication and secure updates, but otherwise it will work fine.
> > > >> If you want a simple topology to manage, that is a good way to go.
> > > >>
> > > >> Steve Duff, MCSE, MVP
> > > >> Ergodic Systems, Inc.
> > > >>
> > > >>
> > > >> "Joe Flynn" <JoeFlynn@discussions.microsoft.com> wrote in message
> news:D89B180F-C8F5-47DC-8B7C-44947C4C386F@microsoft.com...
> > > >> > Hello, I amlooking for any suggestions with using Windows DNS and
> QIP. I am
> > > >> > set with forward lookup zones and having my enterprise QIP DNS as a
> secondary
> > > >> > to the Windows DNS. My question is that my reverse lookup zones
> are broken.
> > > >> > I cannot use Windows Reverse to query a Unix machine and I cannot
> use QIP to
> > > >> > query a windows machine. All my windows boxes are running DHCP.
> My goal is
> > > >> > to use dynamic updates to update the reverse lookup record in QIP
> and
> > > >> > hopefully windows DNS. Not sure if this is even doable. I simply
> want to
> > > >> > get reverse DNS lookup's workgroups across platforms. We use QIP
> as the
> > > >> > enterprise DNS because we have alot of UNIX servers and
> workstations. Any
> > > >> > ideas would be great.
> > > >>
> > > >>
> > > >>
> > >
> > >
> > >
>
>
>

Quantcast