intermittant NS failure on external addresses

[Guest]

Would appreciate some feedback Internal DNS deployment which has
internmittant name resolution failures, especially for external IP Addresses.

FISMO Holder, Primary Domain DNS Own IP As primary, another DC as secondary,
telstra ns as tertiary

DC's - All have own IP Primary, FISMO as secondary

Clients - DHCP assigned DC's IP as primary and seconday

Caching enabled all DC's, forwarders enable on AD integrated zone.


I want external NS to work as well as internal, Do i need to update root
hints? or modify LAN settings to get this working
Any ideas much appreciated

 

[Guest]

You should use only forwarders to forward query to your external DNS server,
and not to put external DNS in any of your servers/clients.

BR,
Denis

 

[Ace Fekay [MVP]]

In

Would appreciate some feedback Internal DNS deployment which has
internmittant name resolution failures, especially for external IP
Addresses.

FISMO Holder, Primary Domain DNS Own IP As primary, another DC as
secondary, telstra ns as tertiary

DC's - All have own IP Primary, FISMO as secondary

Clients - DHCP assigned DC's IP as primary and seconday

Caching enabled all DC's, forwarders enable on AD integrated zone.


I want external NS to work as well as internal, Do i need to update
root hints? or modify LAN settings to get this working
Any ideas much appreciated

What exactly is not resolving?
Are they certain websites?
Is this Windows 2000 or 2003 DNS?
Are you asking if you want your internal servers to host a domain name on
the Internet?


--
Regards,
Ace

Please direct all replies ONLY to the Microsoft public newsgroups
so all can benefit.

This posting is provided "AS-IS" with no warranties or guarantees
and confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft Windows MVP - Windows Server - Directory Services

Security Is Like An Onion, It Has Layers
HAM AND EGGS: A day's work for a chicken;
A lifetime commitment for a pig.