Nslookup of the sites turn up the OpenDNS error page IP address.  
(67.215.65.132)

Reverting to hosts file for now.

 

Didn’t think about conditional forwarders… thanks!

 

From: [email protected] [mailto:[email protected]] On 
Behalf Of Richard Stovall
Sent: Friday, July 26, 2013 10:58 AM
To: [email protected]
Subject: Re: [NTSysADM] Propagating new DNS Forwarders?

 

Do nslookups from the clients show the incorrect addresses?

 

As an aside, if you want to keep using OpenDNS, you can always set up 
conditional forwarders for the problematic sites.

 

On Fri, Jul 26, 2013 at 11:51 AM, Sam Cayze <[email protected]> wrote:

Changing my DNS for our network away from OpenDNS to the DNS of our ISP.  
(Can’t access a few sites all of a sudden with OpenDNS).

 

I changed it on our 2 DNS servers, how do I quickly propagate those settings to 
the clients?  (DHCP hands out the internal DNS servers).

 

I’ve tried restarting DNS on the DCs, clearing the cache, and ipconfig renew 
and flushdns on the clients.  Still getting OpenDNS errors on these sites… so 
the clients are still using OpenDNS…

 

Drawing blanks…

 

Thanks,
Sam

 


Reply via email to