RE: [ActiveDir] DNS Issues

[Robert Rutherford]

Why don’t you forward the root DC/s out to your ISP’s DNS server/s? See if that works.   If you do an nslookup from the root DC, can you resolve correctly?   From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rimmerman, Russ Sent: 16 November 2004 13:58 To: [EMAIL PROTECTED] Subject: RE: [ActiveDir] DNS Issues   Yes, all DNS is working fine except for some rare instances of hostnames we've run into.  Last week we couldn't get to ftp.nai.com but now we can.  All our workstations are pointed to our child DCs for DNS.  They are set to forward to our empty root DCs, and the empty root DCs have the root-hints, and the firewall allows them out port 53.   From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Robert Rutherford Sent: Tuesday, November 16, 2004 7:53 AM To: [EMAIL PROTECTED] Subject: RE: [ActiveDir] DNS Issues I’d advise using forwarding for the functions you require.   It may seem stupid… but I take it the DNS server/s have appropriate rules in your firewall/s?   From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rimmerman, Russ Sent: 16 November 2004 13:48 To: [EMAIL PROTECTED] Subject: [ActiveDir] DNS Issues   Since changing our DNS design from forwarding to our old firewall which had root-hints built into it, to forwarding our DNS to our empty forest root domain controllers with the root-hints on them, we are not getting all our DNS lookups.   For example, http://www.volksbanksalzburg.at right now is not resolving for us.  Yet if we RDP into one of our home PCs, it resolves fine.  So my question is, is there anything weird about Windows 2000 root-hints or DNS servers that would cause us to not be able to look up some hostnames properly in DNS?  Or what would cause this issue? ======================================================================= Scanned for virus infection by Messagelabs ======================================================================= ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ This e-mail is confidential, may contain proprietary information of the Cooper Cameron Corporation and its operating Divisions and may be confidential or privileged. This e-mail should be read, copied, disseminated and/or used only by the addressee. If you have received this message in error please delete it, together with any attachments, from your system. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ======================================================================= Scanned for virus infection by Messagelabs ======================================================================= ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ This e-mail is confidential, may contain proprietary information of the Cooper Cameron Corporation and its operating Divisions and may be confidential or privileged. This e-mail should be read, copied, disseminated and/or used only by the addressee. If you have received this message in error please delete it, together with any attachments, from your system. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~