Nie jesteś zalogowany.
Jeśli nie posiadasz konta, zarejestruj je już teraz! Pozwoli Ci ono w pełni korzystać z naszego serwisu. Spamerom dziękujemy!

Ogłoszenie

Prosimy o pomoc dla małej Julki — przekaż 1% podatku na Fundacji Dzieciom zdazyć z Pomocą.
Więcej informacji na dug.net.pl/pomagamy/.

#1  2009-01-07 11:28:05

  Lewiatan - Użytkownik

Lewiatan
Użytkownik
Skąd: Łódź
Zarejestrowany: 2008-04-08
Serwis

Probilem z bindem. DNS na kliencie nie dziala

Witam

Problem przedstawia się następująco: na jednym kompie (serwer) postawione jest  DHCP i DNS (BIND). Do serweras podłaczony jest jeden komputer który bezproblemowo otrzymuje cala konfiguracje sieci od serwera. Internet generalnie chodzi ale DNS jedynie na serwerze - na kliencie strony wczytuja sie po adresie IP.

konfiguracja serwera:

resolv.conf

Kod:

nameserver 127.0.0.1

named.conf:

Kod:

# Copyright (c) 2001-2004 SuSE Linux AG, Nuernberg, Germany.
# All rights reserved.
#
# Author: Frank Bodammer, Lars Mueller <lmuelle@suse.de>
#
# /etc/named.conf
#
# This is a sample configuration file for the name server BIND 9.  It works as
# a caching only name server without modification.
#
# A sample configuration for setting up your own domain can be found in
# /usr/share/doc/packages/bind/sample-config.
#
# A description of all available options can be found in
# /usr/share/doc/packages/bind/misc/options.

options {

        # The directory statement defines the name server's working directory

        directory "/var/lib/named";

        # Write dump and statistics file to the log subdirectory.  The
        # pathenames are relative to the chroot jail.

        dump-file "/var/log/named_dump.db";
        statistics-file "/var/log/named.stats";

        # The forwarders record contains a list of servers to which queries
        # should be forwarded.  Enable this line and modify the IP address to
        # your provider's name server.  Up to three servers may be listed.

        forwarders { 192.168.0.7; 192.168.0.2; };

        # Enable the next entry to prefer usage of the name server declared in
        # the forwarders section.

        forward first;

        # The listen-on record contains a list of local network interfaces to
        # listen on.  Optionally the port can be specified.  Default is to
        # listen on all interfaces found on your system.  The default port is
        # 53.

        listen-on port 53 { 127.0.0.1; };

        # The listen-on-v6 record enables or disables listening on IPv6
        # interfaces.  Allowed values are 'any' and 'none' or a list of
        # addresses.

        listen-on-v6 { any; };

        # The next three statements may be needed if a firewall stands between
        # the local server and the internet.

        #query-source address * port 67;
        #transfer-source * port 67;
        #notify-source * port 67;

        # The allow-query record contains a list of networks or IP addresses
        # to accept and deny queries from. The default is to allow queries
        # from all hosts.

        allow-query { 127.0.0.1; };

        # If notify is set to yes (default), notify messages are sent to other
        # name servers when the the zone data is changed.  Instead of setting
        # a global 'notify' statement in the 'options' section, a separate
        # 'notify' can be added to each zone definition.

        notify no;
};

# To configure named's logging remove the leading '#' characters of the
# following examples.
logging {
        #Log queries to a file limited to a size of 100 MB.
        channel query_logging {
                file "/var/log/named_querylog"
                        versions 3 size 100M;
                print-time yes;                 // timestamp log entries
        };
        category queries {
                query_logging;
        };

        # Or log this kind alternatively to syslog.
        channel syslog_queries {
                syslog user;
                severity info;
        };
        category queries { syslog_queries; };

        # Log general name server errors to syslog.
        channel syslog_errors {
                syslog user;
                severity error;
        };
        category default { syslog_errors;  };

        # Don't log lame server messages.
        category lame-servers { null; };
};

# The following zone definitions don't need any modification.  The first one
# is the definition of the root name servers.  The second one defines
# localhost while the third defines the reverse lookup for localhost.

zone "." in {
        type hint;
        file "root.hint";
};

zone "localhost" in {
        type master;
        file "localhost.zone";
};

zone "0.0.127.in-addr.arpa" in {
        type master;
        file "127.0.0.zone";
};

# Include the meta include file generated by createNamedConfInclude.  This
# includes all files as configured in NAMED_CONF_INCLUDE_FILES from
# /etc/sysconfig/named

include "/etc/named.conf.include";

# You can insert further zone records for your own domains below or create
# single files in /etc/named.d/ and add the file names to
# NAMED_CONF_INCLUDE_FILES.
# See /usr/share/doc/packages/bind/README.SUSE for more details.

dhcpd.conf

Kod:

default-lease-time 600;
max-lease-time 7200;
option domain-name "site";
option domain-name-servers 192.168.250.249;
option broadcast-address 192.168.250.255;
option routers 192.168.250.1;
option subnet-mask 255.255.255.0;
ddns-update-style none;



subnet 192.168.250.0 netmask 255.255.255.0 {
default-lease-time 600;
max-lease-time 7200;
range 192.168.250.230 192.168.250.240;
option domain-name-servers 192.168.250.249;

Dodam, ze na obu komputerach zapory sa wylaczone.

Offline

 

#2  2009-01-07 12:08:52

  kayo - Członek DUG

kayo
Członek DUG
Zarejestrowany: 2007-05-20

Re: Probilem z bindem. DNS na kliencie nie dziala

w named.conf masz

Kod:

allow-query { 127.0.0.1; };

czyli dopuszczasz zapytania tylko z serwera, zmień to na:

Kod:

allow-query { 127.0.0.1; 192.168.250.0/32;};

Ostatnio edytowany przez kayo (2009-01-07 12:10:55)


Having a Windows 95 box hooked to the internet is akin to walking naked into a prison carrying a carton of cigarettes.
-----------------
jid: kayo77//gmail.com  gg #1046710

Offline

 

#3  2009-01-07 12:33:08

  Lewiatan - Użytkownik

Lewiatan
Użytkownik
Skąd: Łódź
Zarejestrowany: 2008-04-08
Serwis

Re: Probilem z bindem. DNS na kliencie nie dziala

Nic :/

Btw. wystarczy, ze w kliencie wydam komende "dhclient" zeby mu sie to wsio odswiezylo, czy generalnie po restarcie binda nie musze nic w kliencie robic?

EDIT

sprawa zalatwiona, wystarczylo zmienic

Kod:

listen-on port 53 { 127.0.0.1; };

na

Kod:

listen-on port 53 { any; };

Pozdrawiam ;)

Ostatnio edytowany przez Lewiatan (2009-01-07 13:05:30)

Offline

 

Stopka forum

Powered by PunBB
© Copyright 2002–2005 Rickard Andersson
To nie jest tylko forum, to nasza mała ojczyzna ;-)