Cannot find server name though DNS works

davidmuraya · 09-09-2008, 04:24 AM

Hi,
I have configured a small zone in Bind 9 for a small intranet.
When I use the nslookup command on a Windows box, it shows
Default server: cannot find server name though it the remote DNS (The Fedora 9 Machine running the bind) resolves the name to IP.
How can I configure it to show
Default Server: server1.example.com
Address: 192.168.XXXXX.XXX

Woodypecker · 09-09-2008, 04:51 AM

How is the windows box receiving the default server?
Most of the time dhcp will do that, so you should configure dhcpd.conf properly.
Otherwise you have to go to (windows box) network-tcpip-properties-advanced-dns tab
and enter your dns server manually.

odcheck · 09-09-2008, 04:57 AM

is the search path set in the /etc/resolv.conf ?

like on the server

/etc/resolv.conf
search blahfassel.local
nameservers 127.0.0.1

and at the clients
/etc/resolv.conf
search blahfassel.local
nameserver 172.100.1.1

???

chort · 09-09-2008, 10:19 AM

Windows nslookup will complain if the DNS server doesn't have a reverse-DNS entry for it's own IP. You need to properly setup the in-addr.arpa zone for your subnet.

davidmuraya · 09-10-2008, 04:20 AM

Quote:

Originally Posted by chort

Windows nslookup will complain if the DNS server doesn't have a reverse-DNS entry for it's own IP. You need to properly setup the in-addr.arpa zone for your subnet.

Thanks.

I probably think this is the problem.
I tried inserting reverse dns entries but it kept showing errors ie. NS record not found etc.
Could u post a in-addr.arpa zone

chort · 09-10-2008, 10:00 AM

PHP Code:


			
$ORIGIN .
$TTL 3600       ; 1 hour
2.22.172.in-addr.arpa   IN SOA  ns1.smtps.net. hostmaster.smtps.net. (
                                2008081401 ; serial
                                28800      ; refresh (8 hours)
                                300        ; retry (5 minutes)
                                2419200    ; expire (4 weeks)
                                3600       ; minimum (1 hour)
                                )
                        NS      172.22.2.16.
                        NS      172.22.2.26.
$ORIGIN 2.22.172.in-addr.arpa.
1                       PTR     dmz-gw.smtps.net.
106                     PTR     gibraltar.smtps.net.
129                     PTR     wifi-gw.smtps.net.
144                     PTR     mle.smtps.net.
149                     PTR     horus2.smtps.net.
16                      PTR     ns1.smtps.net.
213                     PTR     anubis.smtps.net.
26                      PTR     suez.smtps.net.
33                      PTR     giza.smtps.net.
41                      PTR     stlinux.smtps.net.
50                      PTR     am-heh.smtps.net.
6                       PTR     ns2.smtps.net.
70                      PTR     vm-svr-01.smtps.net.
71                      PTR     pps-01.smtps.net.
80                      PTR     tmdemos.smtps.net.
84                      PTR     stdemo.smtps.net.
85                      PTR     mgdemo.smtps.net.
86                      PTR     w2k3-test1.demos.smtps.net.
88                      PTR     pdc-ad.demos.smtps.net.
89                      PTR     vm-obsd.smtps.net.
94                      PTR     dragonflay.smtps.net.
98                      PTR     unbreakable.smtps.net.

I just noticed the I'm using IPs for the NS records, and that I have a trailing period. I'm honestly not sure why I did that, normal fully-qualified hostname (with period) should work fine. My reverse zone is working correctly with bind 9.4.x though.

odcheck · 09-10-2008, 11:27 AM

ok, wonderful, as I see but 1st I guess that you know already that there is a correct reverse zone need.
So did you try what I've told you?
In the DHCP config
the option is domain-name "blahfassel";

I had once exactly this case, and there was a well configured reverse zone as well as a forward zone.
But "nslookups" from the clients failed. So after I've adjusted the dhcp to the above mentioned option it worked.

davidmuraya · 09-12-2008, 05:12 AM

Quote:

Originally Posted by chort

PHP Code:


			
$ORIGIN .
$TTL 3600       ; 1 hour
2.22.172.in-addr.arpa   IN SOA  ns1.smtps.net. hostmaster.smtps.net. (
                                2008081401 ; serial
                                28800      ; refresh (8 hours)
                                300        ; retry (5 minutes)
                                2419200    ; expire (4 weeks)
                                3600       ; minimum (1 hour)
                                )
                        NS      172.22.2.16.
                        NS      172.22.2.26.
$ORIGIN 2.22.172.in-addr.arpa.
1                       PTR     dmz-gw.smtps.net.
106                     PTR     gibraltar.smtps.net.
129                     PTR     wifi-gw.smtps.net.
144                     PTR     mle.smtps.net.
149                     PTR     horus2.smtps.net.
16                      PTR     ns1.smtps.net.
213                     PTR     anubis.smtps.net.
26                      PTR     suez.smtps.net.
33                      PTR     giza.smtps.net.
41                      PTR     stlinux.smtps.net.
50                      PTR     am-heh.smtps.net.
6                       PTR     ns2.smtps.net.
70                      PTR     vm-svr-01.smtps.net.
71                      PTR     pps-01.smtps.net.
80                      PTR     tmdemos.smtps.net.
84                      PTR     stdemo.smtps.net.
85                      PTR     mgdemo.smtps.net.
86                      PTR     w2k3-test1.demos.smtps.net.
88                      PTR     pdc-ad.demos.smtps.net.
89                      PTR     vm-obsd.smtps.net.
94                      PTR     dragonflay.smtps.net.
98                      PTR     unbreakable.smtps.net.

I just noticed the I'm using IPs for the NS records, and that I have a trailing period. I'm honestly not sure why I did that, normal fully-qualified hostname (with period) should work fine. My reverse zone is working correctly with bind 9.4.x though.

thanks a bunch!
That was definately the problem!
It is now working perfectly!!!!
Thanks again
It has even become faster in resolving.