Client won't use the other DNS server for internet

  • Thread starter Thread starter Mr555
  • Start date Start date
M

Mr555

Hi everyone. I have a interesting problem. we been running
Windows 2000 for the last 2 1/2 years, very stable.
recently we had some small DNS issue, therefore we have
setup another Active Directory integrated DNS Server as
our backup. we tested by disabling DNS service on our
primary Domain controller. All clients then switches to
use the other DNS server. I can ping other computer on the
network, send e-mail except browseing the internet, I can
only browe the internet until I enable the primary DNS
Server. Have I setup something wrong or miss a step during
the DNS install ? Please help . we use DHCP and WINS on
our network.

Thanks

Mr555
 
If you set up another DC w/DNS, you don't have a "backup" DNS server per
se - it's a copy of the main AD DNS.

All servers and workstations should specify *only* the internal
AD-integrated DNS server's IP address in their network settings. The
AD-integrated DNS server should be set up with forwarders to several of your
ISP's DNS servers for external resolution.

See http://support.microsoft.com/default.aspx?scid=kb;en-us;300202 for more
info.
 
In Lanwench [MVP - Exchange]
If you set up another DC w/DNS, you don't have a "backup" DNS server
per
se - it's a copy of the main AD DNS.

All servers and workstations should specify *only* the internal
AD-integrated DNS server's IP address in their network settings. The
AD-integrated DNS server should be set up with forwarders to several
of your ISP's DNS servers for external resolution.

See http://support.microsoft.com/default.aspx?scid=kb;en-us;300202
for more info.
Click to expand...

To add...maybe the root zone (a dot "." zone) exists on that new server or
recursion is disabled.

--
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
 
Hi

All workstation and Server have both AD-integraed DNS
Server IP address. not sure why all workstaion can only
use the other AD integrated DNS but not the other ?

thank you
 
In
Mr555 said:
Hi

All workstation and Server have both AD-integraed DNS
Server IP address. not sure why all workstaion can only
use the other AD integrated DNS but not the other ?

thank you
Click to expand...
Hi Mr555

Not sure what you mean by not all workstations can only use the "other" AD
integrated DNS. Do you have them listed in the machines' IP properties or
the DHCP scope?

Have you manually tested a client with ONLY putting in that one server, test
it out with Internet connectivity, then remove that and try it with the
other one...

Also, I'm still not sure if you have your ISP's DNS in those properties. If
you do, multiple issues WILL occur.



--
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
 
Hi there

(a dot "." zone) exists is on that new server and
recursion is not disable.

This morning we modify our proxy server and make server B
is the primary DNS and the SERVER A(primary integraed DNS)
to be the alternative DNS. then we disable the DNS service
on our Server A still no luck. I can ping any workstaion
on our network using Server B , nslookup on any site. send
and receive E-mail, but not browsing the internet.

Thanks



-----Original Message-----
In Lanwench [MVP - Exchange]
<[email protected]
posted their
thoughts, then I offered mine
If you set up another DC w/DNS, you don't have a "backup" DNS server
per
se - it's a copy of the main AD DNS.

All servers and workstations should specify *only* the internal
AD-integrated DNS server's IP address in their network settings. The
AD-integrated DNS server should be set up with forwarders to several
of your ISP's DNS servers for external resolution.

See http://support.microsoft.com/default.aspx? scid=kb;en-us;300202
for more info.
Click to expand...

To add...maybe the root zone (a dot "." zone) exists on that new server or
recursion is disabled.

--
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
--
=================================


.
Click to expand...
 
In
If you need DNS to resolve names on the internet, you must either delete the
dot "." zone or make it a delegated root zone. It is much easier to simply
delete it.
 
In
Kevin D. Goodknecht said:
In
If you need DNS to resolve names on the internet, you must either
delete the dot "." zone or make it a delegated root zone. It is much
easier to simply delete it.

--
Best regards,
Kevin D4 Dad Goodknecht Sr. [MVP]
Hope This Helps
============================
Click to expand...

I agree. Thought that's what the prob is. That's why Server B is not
resolving...

--
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
 
Hi There

Thank you for your reply. my problem is that I have 2 AD
integrated DNS Server. Server1 and Server2. our proxy will
only works with Server1. If Server1 down, Server2 will
take over for all the DNS lookup except for browsing
internet. I have listed Server2 IP address on DHCP Scope.
and I have enter our ISP DNS Sever address IP address on
Server2 forwarder. I have investigated this promblem have
gone futher. I disable Server1 , Server2 took over all the
DNS services. I can browse the internet site only if
server2 have the cache information on its DNS, otherwise
won't work. If there something I have miss during the DNS
configuration on Server2?

Please help.

Thanks

MR555
 
Sorry forgot to mention

I did tested with a clients with only Server2 IP address,
that works.

Is this a DNS problem or Proxy ???

Thanks
 
In
Mr555 said:
Sorry forgot to mention

I did tested with a clients with only Server2 IP address,
that works.

Is this a DNS problem or Proxy ???

Thanks
Click to expand...
It's starting to appear to be a Proxy issue. Do you have rules allowing DNS
communication outbound/inbound for Server2?

--
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
 
Back
Top