NAT Router Problem Nachtrag

Ich muß noch dazu sagen, daß ich den wwwoffle Proxy einsetze und
http_proxy, ftp_proxy, HTTP_PROXY und FTP_PROXY alle auf
"http://localhost:8080/"
gesetzt sind.

Außerdem erhalte ich vom routed folgende Meldung:
Jan 19 12:47:03 sun routed[268]: setsockopt(IP_ADD_MEMBERSHIP RIP):
Can't assign requested address
Jan 19 12:47:03 sun routed[268]: ignore RTM_CHANGE without mask
Jan 19 12:47:03 sun routed[268]: ignore RTM_CHANGE without mask

Übrigens funkte es auch nicht, als ich noch alle Rechner statisch in der
"/etc/hosts" eingetragen hatte (Ohne DHCP).

FRAGE: Brauche ich beim DNS überhaupt eine eigene ZONE, reicht es nicht
       in der named.conf "forward only" zu setzen und die DNS des Providers
       als forwarders einzutragen ???

Ich ersetzte den BIND auch schon mit "dnsmasq", bekam aber immer
Meldungen von
schon benutzten SOCKETS. (Socket alredy in use) Der BIND war hier
natürlich aus.

/etc/resolv.conf (ROUTER)
domain solar-system.xxx
nameserver 127.0.0.1
nameserver 192.168.0.1

/etc/resolv.conf (CLIENT)
search solar-system.xxx
nameserver 127.0.0.1
nameserver 192.168.0.1

In der rc.conf des CLIENT ist noch
defaultrouter="192.168.0.1" (IP des Routers) eingetragen.

Zum Abschluß hier noch meine named.conf, hatte ich vorher vergessen:

// $FreeBSD: src/etc/namedb/named.conf,v 1.14 2003/02/07 20:58:38
keramida Exp $
//
// Refer to the named.conf(5) and named(8) man pages for details. If
// you are ever going to set up a primary server, make sure you
// understand the hairy details of how DNS works. Even with
// simple mistakes, you can break connectivity for affected parties,
// or cause huge amounts of useless Internet traffic.

options {
    directory "/etc/namedb";
    pid-file "/var/run/named.pid";

// In addition to the "forwarders" clause, you can force your name
// server to never initiate queries of its own, but always ask its
// forwarders only, by enabling the following line:
//
    forward only;
    forward first;

// If you've got a DNS server around at your upstream provider, enter
// its IP address here, and enable the line below. This will make you
// benefit from its cache, thus reduce overall DNS traffic in the Internet.

    forwarders {
        194.97.3.83;
        194.97.173.125;
    };

    notify no;

    listen-on {
        127.0.0.1;
        192.168.0.1;
    };

    /*
     * 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;

    /*
     * If running in a sandbox, you may have to specify a different
     * location for the dumpfile.
     */
    // dump-file "s/named_dump.db";
};

// Note: the following will be supported in a future release.
/*
host { any; } {
    topology {
        127.0.0.0/8;
    };
};
*/

// Setting up secondaries is way easier and a rough example for this
// is provided below.
//
// If you enable a local name server, don't forget to enter 127.0.0.1
// first in your /etc/resolv.conf so this server will be queried.
// Also, make sure to enable it in /etc/rc.conf.

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

zone "0.0.127.IN-ADDR.ARPA" {
    type master;
    file "localhost.rev";
};

// RFC 3152
zone
"1.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" {
    type master;
    file "localhost-v6.rev";
};

// RFC 1886 -- deprecated
zone
"1.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.INT" {
    type master;
    file "localhost-v6.rev";

};

zone "solar-system.xxx" {
    notify no;
    type master;
    file "solar-system.xxx_192.168.0.0";
};

zone "0.168.192.IN-ADDR.ARPA" {
    notify no;
    type master;
    file "192.168.0.0_solar-system.xxx";
};

// NB: Do not use the IP addresses below, they are faked, and only
// serve demonstration/documentation purposes!
//
// Example secondary config entries. It can be convenient to become
// a secondary at least for the zone your own domain is in. Ask
// your network administrator for the IP address of the responsible
// primary.
//
// Never forget to include the reverse lookup (IN-ADDR.ARPA) zone!
// (This is named after the first bytes of the IP address, in reverse
// order, with ".IN-ADDR.ARPA" appended.)
//
// Before starting to set up a primary zone, make sure you fully
// understand how DNS and BIND works. There are sometimes
// non-obvious pitfalls. Setting up a secondary is simpler.
//
// NB: Don't blindly enable the examples below. :-) Use actual names
// and addresses instead.
//
// NOTE!!! FreeBSD can run bind in a sandbox (see named_flags in rc.conf).
// The directory containing the secondary zones must be write accessible
// to bind. The following sequence is suggested:
//
// mkdir /etc/namedb/s
// chown bind:bind /etc/namedb/s
// chmod 750 /etc/namedb/s

/*
zone "solar-system.xxx" {
    type slave;
    file "s/solar-system.xxx.bak";
    masters {
        192.168.0.1;
    };
};

zone "0.168.192.in-addr.arpa" {
    type slave;
    file "s/0.168.192.in-addr.arpa.bak";
    masters {
        192.168.0.1;
    };
};
*/

Gruß Seppy

To Unsubscribe: send mail to majordomo.FreeBSD.org
with "unsubscribe de-bsd-questions" in the body of the message
Received on Mon 19 Jan 2004 - 13:44:33 CET