First nslookup/query from Windows clients always fails (Bind9)

Bryan Irvine sparctacus at gmail.com
Tue Mar 7 19:08:11 UTC 2006


what version of BIND?

On 7 Mar 2006 09:19:28 -0800, aweaver at ee.net <aweaver at ee.net> wrote:
> I've setup two identical machines for the purpose of simple resolution
> for hosts on my network. For whatever reason Windows clients always
> fail to resolve domains on the first try every attempt, here is an
> example of this behaviour:
>
> C:\Documents and Settings\aweaver.THENAP.000>nslookup
> www.cartoonnetwork.com
> Server:  resolver2.services.domain.com
> Address:  192.168.123.3
>
> DNS request timed out.
>     timeout was 2 seconds.
> *** Request to resolver2.services.domain.com timed-out
>
> C:\Documents and Settings\aweaver.THENAP.000>nslookup
> www.cartoonnetwork.com
> Server:  resolver2.services.domain.com
> Address:  192.168.123.3
>
> Non-authoritative answer:
> Name:    cartoonnetwork.com
> Addresses:  64.236.29.72, 64.236.22.72
> Aliases:  www.cartoonnetwork.com
>
> On linux:
>
> [root at linuxweb ~]# nslookup cartoonnetwork.com
> Server:         192.168.123.3
> Address:        192.168.123.3#53
>
> Non-authoritative answer:
> Name:   cartoonnetwork.com
> Address: 64.236.22.72
> Name:   cartoonnetwork.com
> Address: 64.236.29.72
>
> Here is my configuration file that I am using on 192.168.123.2 and
> 192.168.123.3:
>
> options {
>         directory "/var/named";
>         dump-file "/var/named/data/cache_dump.db";
>         statistics-file "/var/named/data/named_stats.txt";
>         /*
>          * If there is a firewall between you and nameservers you want
>          * to talk to, you might need to uncomment the query-source
>          * directive below.  Previous versions of BIND always asked
>          * questions using port 53, but BIND 8.1 uses an unprivileged
>          * port by default.
>          */
>          // query-source address * port 53;
> };
>
> //
> // a caching only nameserver config
> //
> controls {
>         inet 127.0.0.1 allow {
>                 10.1.1.0/24;
>                 192.168.123.0/24;
>                 172.0.1.0/24;
>                 localhost;
>                         }
> keys { rndckey; };
>
> };
> zone "." IN {
>         type hint;
>         file "named.ca";
> };
>
> zone "localdomain" IN {
>         type master;
>         file "localdomain.zone";
>         allow-update { none; };
> };
>
> zone "localhost" IN {
>         type master;
>         file "localhost.zone";
>         allow-update { none; };
> };
>
> zone "0.0.127.in-addr.arpa" IN {
>         type master;
>         file "named.local";
>         allow-update { none; };
> };
>
> zone
> "0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa"
> IN
>  {
>         type master;
>         file "named.ip6.local";
>         allow-update { none; };
> };
>
> zone "255.in-addr.arpa" IN {
>         type master;
>         file "named.broadcast";
>         allow-update { none; };
> };
>
> zone "0.in-addr.arpa" IN {
>         type master;
>         file "named.zero";
>         allow-update { none; };
> };
>
> include "/etc/rndc.key";
>
> If anyone has a moment to try and tell me what I am doing wrong I would
> appreciate it so much; I am more used to bind 8 as we have been using
> it for years.
>
> There are no relevant lines in the log file either.
>
> Thanks,
> -Drew
>
>
>



More information about the bind-users mailing list