DNS problem

[Brian Salomaki]

When setting up your clients, your primary and secondary DNS servers should 
be two servers that return the same data for all zones (usually your own 
master/slave, or two of your own dedicated caching machines).  Windows will 
query a nameserver, and if that one works, it will keep using that one until 
it fails.  If your primary failed at one point, then Windows switched to your 
secondary DNS (your ISP's), and is now using that for DNS resolution. (This 
does not apply to nslookup, as it is probably querying the first server on 
its own, without going through Win2K's resolver.)

You should probably set up a slave server for your BIND box, and use that as 
a secondary, or set up a caching server that points at your BIND box, so you 
don't deal with different DNS environments.

On Monday 03 September 2001 11:27 pm, Yuen_121 wrote:
> I have set up an internal DNS server (solaris 7) using bind 9.1.2.
> with IP (192.168.0.2)and a zone file for company.com domain with the
> following entry :
>
> www  86400   A  192.168.0.5   ; Web server
>
> One Win2K prof. client use 192.168.0.5 as primary DNS server and ISP's
> DNS server as the secondary.
> When execute nslookup www.company.com in the client side, everything
> works no problem. (The address is  192.168.0.5)
>
> However, when execute ping www.company.com in the client side, the
> address is pointing to the external address, it use secondary DNS
> server's entry. (The address is differ. from the 192.168.0.5).
>
> Can anyone help me?
>
> Thanks.
>
> Yuen_121

-- 
Brian Salomaki
Gambit Design Internet Services
110 E. State St., Suite 18, Kennett Square, PA 19348