Problems connecting to Internet

  • Thread starter Thread starter Chris Dove
  • Start date Start date
C

Chris Dove

The clients connect to the internet directly through the Router. In order
for this to work I have to make as external DNS server the Primary DNS on
the Clients and our Internal DNS server as the Secondary.

Is there any way to configure the DNS so our Internal DNSserver is the
Primary server in the list?

Any help would be appreciated

Chris
 
In
Chris Dove said:
The clients connect to the internet directly through the Router. In
order for this to work I have to make as external DNS server the
Primary DNS on the Clients and our Internal DNS server as the
Secondary.

Is there any way to configure the DNS so our Internal DNSserver is the
Primary server in the list?

Any help would be appreciated

Chris
Click to expand...

Never use your ISP's in an AD environment. Otherwise you will be
guaranteeing problems.

Here's a repost of something I posted the other day for someone else that I
was trying to help with which may/will apply to your scenario. It also
provides some links you can read up on AD's requirements and such:
==================================
First thing I would check and make absolutely sure that you do NOT have any
external DNS servers in all of your machines' IP properties. This is
problematic with AD.

During many domain
communication and functions, the clients and DCs query the DNS server for
the location of domain services and resources, which is what the SRV records
store. If using an ISP's DNS in your IP properties, then numerous numerous
errors will abound, one of which long logon times or cannot logon, will
occur. So what's happening probably is that they maybe trying to query the
external DNS for that domain name's LDAP services, which it does not have an
answer for, so the need to point to your own DNS that's hosting the AD zone
is essential in an AD infrastructure, no matter how small.

So, if using an external DNS or the Netware DNS, they need to be removed and
only use your own internal DNS. To achieve efficient Internet resolution (if
required if not using Proxy), then suggested to configure a forwarder

Here's how to configure a forwarder. If the option is grayed out, delete the
root zone. This will show how:
http://support.microsoft.com/?id=300202

Here's more info on DNS and AD's requirements:
http://support.microsoft.com/?id=291382

Here's an AD and DNS troubleshooting guide:
http://www.microsoft.com/windows2000/dns/tshoot/dns_tshoot2A.asp

How to configure a DC with a single label DNS domain name"
http://support.microsoft.com/?id=300684
(notice this is just a bandaid because XP pro clients will not be able to
use a single label name in a domain and will have numerous problems
accessing domain resources due to this).
======================================


--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
In
Chris Dove said:
The clients connect to the internet directly through the Router. In
order for this to work I have to make as external DNS server the
Primary DNS on the Clients and our Internal DNS server as the
Secondary.

Is there any way to configure the DNS so our Internal DNSserver is the
Primary server in the list?

Any help would be appreciated

Chris
Click to expand...

The internal DNS should be the only DNS server used by internal clients.
Then configure the internal DNS server as per this KB: 300202 - HOW TO:
Configure DNS for Internet Access in Windows 2000
http://support.microsoft.com/?id=300202&FR=1

If you are using DHCP on the router you should disable it and use DHCP on
Win2k it will support AD functions.
 
Clients and the server should only point at the internal DNS server. Once this is setup, please reference this article for configuring the Windows 2000 DNS
server for Internet access. 300202 HOW TO: Configure DNS for Internet Access in Windows 2000 http://support.microsoft.com/?id=300202

Thank you,
Mike Johnston
Microsoft Network Support

--

This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread from which they originated.
 
Back
Top