not able to access bind from windows client machine

This is a discussion on not able to access bind from windows client machine within the Linux Networking forums, part of the Linux Forums category; Hi, Im using Fedora4 and a VMware on it which runs Fedora5. Im running bind-9.3.1-4 on ...


Go Back   Usenet Forums > Linux Forums > Linux Networking

FAQ Members List Calendar Search Today's Posts Mark Forums Read
  #1 (permalink)  
Old 10-10-2006
Danish
 
Posts: n/a
Default not able to access bind from windows client machine

Hi,
Im using Fedora4 and a VMware on it which runs Fedora5. Im running
bind-9.3.1-4 on Fedora4. Im not able to access my the index.html under
/var/ww/html on the Fedora4 machine from a Windows machine, but the
same is accessible under the VMmachine.

Under the Window system: a static ip is configured with the dns server
ip as default gateway and also as the dns server.

Following are my named.conf and est-it-03.zone file

//
// named.conf for Red Hat caching-nameserver
//

options {
directory "/var/named";
};

controls {
inet 127.0.0.1 allow{ localhost; } keys { rndc_key; };
};

zone "."{
type hint;
file "named.ca";
};

zone "est-it-03.lab" {
type master;
notify yes;
file "est-it-03.zone";
};

zone "0.0.127.in-addr.arpa"{
type master;
file "named.local";
allow-update { none; };
};


est-it-03.zone file:

$TTL 86400
@ IN SOA @ root (
42 ; serial (d.
adams)
3H ; refresh
15M ; retry
1W ; expiry
1D ) ; minimum

IN NS 192.168.10.240
IN A 127.0.0.1
IN AAAA ::1



windows machine: 192.168.10.243
DNS server machine: 192.168.10.240

On doing nslookup on windows command prompt, I get the following error:
C:\ nslookup est-it-03.lab
Cant find server name for address 192.168.10.240: Non existant domain
Default servers are not available
Server: Unknown
Address 192.168.10.240


Thanks
Danish

Reply With Quote
  #2 (permalink)  
Old 10-15-2006
Jeroen Geilman
 
Posts: n/a
Default Re: not able to access bind from windows client machine

Danish wrote:

> est-it-03.zone file:
>
> $TTL 86400
> @ IN SOA @ root (
> 42 ; serial (d.
> adams)
> 3H ; refresh
> 15M ; retry
> 1W ; expiry
> 1D ) ; minimum
>
> IN NS 192.168.10.240
> IN A 127.0.0.1
> IN AAAA ::1


You have to define at least one glue record for the nameserver:

server IN A 192.168.10.240
@ IN NS server

And remove all the other records.

Without glue records, it won't know that it is, in fact, a nameserver.
Which is reflected in the error you get.


J.
Reply With Quote
Reply
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are Off
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On



All times are GMT +1. The time now is 02:17 AM.


Powered by vBulletin® Version 3.7.3
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO 3.0.0