PHWinfo - Afficher un message - AD DNS subdomains fail when internet lost

14/06/2007, 22h18

should i be doing this?

To Add the Organization's Main DNS Servers to the List of Forwarders on the
Windows Server 2003 Computer
1. Click Start, point to Programs, click Administrative Tools, and
then click DNS to open the DNS Management Console.
2. Right-click the DNS Server object for your server, and then click
Properties.
3. Click the Forwarders tab, type the IP address of the DNS server to
which you want to forward non-local queries, and then click Add.
4. Continue adding the IP addresses of any additional DNS servers to
be used as forwarders until you have added all forwarders.
5. Click OK to save the settings and return to the DNS Management
Console.

Rather than my current forwarders config which is
"DNS domain: All other DNS domains"
and forwarder IP address list empty

thanks,
Trevor

"Trevor Christie" <bbtrev@gmail.com> wrote in message
news:i8hci.18453$vT6.38@edtnps90...
> Sorry Paul, I neglected to mention that all clients point only to internal
> DNS servers and each of the DNS servers points to one another. none of
> them points to an external DNS server.
>
>
> "Paul Bergson [MVP-DS]" <pbergson@allete_nospam.com> wrote in message
> news:ObbX%23mqrHHA.500@TK2MSFTNGP02.phx.gbl...
>> These two systems should be totally disconnected from one another when it
>> comes to name resolution.
>>
>> Your internal AD dns servers should not have any reference to external
>> dns servers. What you want to do is forward any external requests to
>> your ISP and all your clients should be requesting all dns queries to
>> your AD dns server.
>>
>> Take a look at
>> http://support.microsoft.com/kb/323418/
>>
>> With particular interest in the paragraph -> To Integrate Windows Server
>> 2003 DNS into Your existing DNS Domain
>>
>> --
>> Paul Bergson
>> MVP - Directory Services
>> MCT, MCSE, MCSA, Security+, BS CSci
>> 2003, 2000 (Early Achiever), NT
>>
>> http://www.pbbergs.com
>>
>> Please no e-mails, any questions should be posted in the NewsGroup
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>> "Trevor Christie" <bbtrev@gmail.com> wrote in message
>> news:2Deci.18421$vT6.12639@edtnps90...
>>> Yesterday, we lost our ISA server and while it was down, internal DNS
>>> went
>>> in the toilet.
>>>
>>> Our internal DNS is AD integrated. Our domain is internal.mycompany.com
>>> (clients are set to append this suffix). We have 2 subdomains,
>>> printers.internal.mycompany.com and net.internal.mycompany.com. When the
>>> internet was lost, and therefore external DNS was lost, clients became
>>> unable to contact resources in either of the 2 subdomains by name unless
>>> they specified the fully qualified name. We've since restored the
>>> internet connection, so things are operating properly again, but there
>>> is obviously a misconfiguration somewhere that I want to get resolved in
>>> case the internet is lost again.
>>>
>>>
>>
>>
>
>

14/06/2007, 22h18	#4
Trevor Christie Messages: n/a Hébergeur:	Re: AD DNS subdomains fail when internet lost should i be doing this? To Add the Organization's Main DNS Servers to the List of Forwarders on the Windows Server 2003 Computer 1. Click Start, point to Programs, click Administrative Tools, and then click DNS to open the DNS Management Console. 2. Right-click the DNS Server object for your server, and then click Properties. 3. Click the Forwarders tab, type the IP address of the DNS server to which you want to forward non-local queries, and then click Add. 4. Continue adding the IP addresses of any additional DNS servers to be used as forwarders until you have added all forwarders. 5. Click OK to save the settings and return to the DNS Management Console. Rather than my current forwarders config which is "DNS domain: All other DNS domains" and forwarder IP address list empty thanks, Trevor "Trevor Christie" <bbtrev@gmail.com> wrote in message news:i8hci.18453$vT6.38@edtnps90... > Sorry Paul, I neglected to mention that all clients point only to internal > DNS servers and each of the DNS servers points to one another. none of > them points to an external DNS server. > > > "Paul Bergson [MVP-DS]" <pbergson@allete_nospam.com> wrote in message > news:ObbX%23mqrHHA.500@TK2MSFTNGP02.phx.gbl... >> These two systems should be totally disconnected from one another when it >> comes to name resolution. >> >> Your internal AD dns servers should not have any reference to external >> dns servers. What you want to do is forward any external requests to >> your ISP and all your clients should be requesting all dns queries to >> your AD dns server. >> >> Take a look at >> http://support.microsoft.com/kb/323418/ >> >> With particular interest in the paragraph -> To Integrate Windows Server >> 2003 DNS into Your existing DNS Domain >> >> -- >> Paul Bergson >> MVP - Directory Services >> MCT, MCSE, MCSA, Security+, BS CSci >> 2003, 2000 (Early Achiever), NT >> >> http://www.pbbergs.com >> >> Please no e-mails, any questions should be posted in the NewsGroup >> This posting is provided "AS IS" with no warranties, and confers no >> rights. >> >> "Trevor Christie" <bbtrev@gmail.com> wrote in message >> news:2Deci.18421$vT6.12639@edtnps90... >>> Yesterday, we lost our ISA server and while it was down, internal DNS >>> went >>> in the toilet. >>> >>> Our internal DNS is AD integrated. Our domain is internal.mycompany.com >>> (clients are set to append this suffix). We have 2 subdomains, >>> printers.internal.mycompany.com and net.internal.mycompany.com. When the >>> internet was lost, and therefore external DNS was lost, clients became >>> unable to contact resources in either of the 2 subdomains by name unless >>> they specified the fully qualified name. We've since restored the >>> internet connection, so things are operating properly again, but there >>> is obviously a misconfiguration somewhere that I want to get resolved in >>> case the internet is lost again. >>> >>> >> >> > >