Re: ping from a Windows client desktop doesn't resolve

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

please check below!

On Tue, 2 Feb 2010 16:57:33 -0500
cr lankis <[email protected]> wrote:

> Hi,
> 
> I'm migrating and old MS-DNS to dnscache+tinydns.
> 
> I'm having a weird problem and I don't know where it could be coming from.
> 
> I have the Windows desktop with the MS-DNS IPs as DNS servers, I ping
> any domain and it resolves it.
> 
> I have the Windows desktop with the dnscache IPs as DNS servers, I
> ping and it does not resolve the domain, but if I run nslookup, it
> does resolve.
> 

- - ---- cut --

There are a number of reasons why your DNS lookup may not be working.

1) DNSCACHE configuration
   as already mentioned in /service/dnscache/root/ip/ you have one or more files
   determining which IP addresses are allowed to use the dnscache 
   e.g. file name "192" means all servers with an IP address starting with 192.

   The file /service/dnscache/env/IP contains one line with the IP running running dnscache.
   This should be the IP number of the interface your LAN clients are connected to

   The same IP address has to be in /etc/resolv.conf
   -> e.g. nameserver 192.168.0.1

   The file /etc/nsswitch.conf contains configuration data.
   There should be a "hosts" line and it should look like this:
  	hosts:          files wins dns
   This determines different methods to resolve hosts names and their order! 
    -> if you have no "dns" your dnscache will never be used!!

2) DHCP3 configuration
   the problem here is that some nasty logic was implemented which will check the servers IP address 
   and automatically update /etc/resolv.conf!
   This will always cause problems if you have 2 network adapters e.g. one WAN side and one LAN side.
   There are 2 ways to solve this
   1) add a file called "nodnsupdate" to /etc/dhcp3/dhclient-enter-hooks.d with the following content:
	---
       #!/bin/sh
	make_resolv_conf(){
        	:
	}
	---
    2) deinstall the whole mDNS, avahi crap from the server


   In addition you need to tell your Windows PC's which DNS server they should be using.
   You do this by adding a line with the DNS server to your /etc/dhcp3/dhcpd.conf file
   -> e.g.    option netbios-name-servers 192.168.0.1


3) Windows PC
   Adjust your network configuration to use DHCP and automatic DNS servers.
   Restart the PC and check the network configuration by running the command 
	ifconfig /all 
   in a Command Prompt window!
   This should show not only your IP number but additional data including the DNS server being used.
   Obviously this should be your dnscache server.

Hope this helps!

Bernd
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkto944ACgkQpYU8M8PbPV7kBgCeIVgWLewX1B/PmN9xj17lksJh
zSIAoJIAxhVB9+x+N04CCTJCRdtqbsFY
=mY8Z
-----END PGP SIGNATURE-----