Re: Client DNS settings
- From: "James" <James@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 2 Jun 2005 08:30:05 -0700
Thanks Laura for the info.
My AD DNS servers are configured to forward outside queries to the Unix DNS
servers. However, I noticed that reverse lookup for hosts outside the AD
domain do not work if the AD DNS servers are listed prior to the Unix ones in
the client TCP/IP configuration. Is there a way around that? Moreover, Is
there a way to push the DNS changes to the clients via a REG fix given the
fact that the DNS server list are stored in the interfaces hive (interface
based) as shown below
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{F82A7CDE-2820-4F95-98E2-0D6C714502C4}]
"NameServer"="10.1.1.20,10.1.1.30"
Thanks
"Laura E. Hunter (MVP)" wrote:
> Are your AD DNS servers configured to forward requests to the UNIX servers?
> If so, then your AD DNS servers will forward to the UNIX servers any request
> that they can't resolve themselves. (In other words, any requests outside
> of ad.corp.com)
>
> If you're using 2003, you can set up conditional forwarding to manually
> specify that requests to resolve resources in corp.com go to the DNS
> server(s) in corp.com.
>
> To improve client performance, you also have the possibility of hosting a
> secondary zone copy of corp.com on one or more of your ad.corp.com servers
> so that queries can be resolved locally.
>
> See this link for more detail on configuring DNS forwarding for Windows DNS
> servers:
> http://www.microsoft.com/technet/prodtechnol/windowsserver2003/library/ServerHelp/1cd13da9-ed0a-4814-b0bb-e46e8ac1e321.mspx
>
> --
> Laura E. Hunter
> Microsoft MVP - Windows Server Networking
> Author: _Active Directory Consultant's Field Guide_
> (http://tinyurl.com/7f8ll)
>
> All information provided "AS-IS", no warranties expressed or implied.
> Replies to newsgroup only.
>
>
> "James" <James@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:4C97B0C5-E58F-4795-89F1-1152C17E8F1E@xxxxxxxxxxxxxxxx
> > Situation: My clients are configured to pull IP addresses & DNS servers
> > list
> > from a Unix DHCP. These clients are moving into AD that has integrated DNS
> > (all DCs have DNS installed). NS records and host records of the DCs have
> > been created on the Unix DNS server. What is the best way to configure the
> > clients to ensure that the client do register themselves in AD DNS while
> > ensuring the clients are able to resolve addresses in AD & for domains
> > outside AD? Thanks
> >
> > For example:
> >
> > My corp domain is corp.com
> >
> > My corp Unix DNS server is 10.1.1.10
> >
> > My DC DNS servers are: 10.1.1.20 & 10.1.1.30 (dc1 & dc2)
> >
> > My AD domain FQDN is ad.corp.com
> >
> > These entries have been defined on the Unix DNS server (10.1.1.10)
> >
> > ad NS dc1.corp.com
> > ad NS dc2.corp.com
> >
> > dc1 A 10.1.1.20
> > dc2 A 10.1.1.30
> >
>
>
>
.
- References:
- Client DNS settings
- From: James
- Re: Client DNS settings
- From: Laura E. Hunter \(MVP\)
- Client DNS settings
- Prev by Date: LDAP Search for memberOf zero returns
- Next by Date: Account permissions
- Previous by thread: Re: Client DNS settings
- Next by thread: RE: Client DNS settings
- Index(es):
Relevant Pages
|
