Hallo Linux freak! Ik gebruik LInux Ubuntu 7.10 sinds kort en ik heb amper LInux ervaring. Ik krijg een error bij het starten van de service voor PROFTPD:
root@linux-computer:/etc# /etc/init.d/proftpd restart
* Stopping ftp server proftpd [ OK ]
* Starting ftp server proftpd
- IPv6 getaddrinfo 'linux-computer' error: No address associated with hostname
[ OK ]
Ik ergens gelezen dat ik de /etc/hosts file en de dns record moet aanpassen. IK heb dus ook een DNS server gemaakt via bind. Ik neem aan dat ik in mijn configuratie file van bind moet zijn, /etc/bind/named.conf. Maar mocht ik in de verkeerde hoek zitten laat mij weten. In iedergeval heb ik mijn /etc/hosts file al aangepast en dit heeft het probleem nog niet verholpen. Tevens weet ik niet hoe ik mijn hostname in de DNS record moet zetten.
GNU nano 2.0.6 File: /etc/hosts
127.0.0.1 localhost
192.168.1.12 linux-computer
# The following lines are desirable for IPv6 capable hosts
::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts
192.168.1.11 black
DNS record:
// This is the primary configuration file for the BIND DNS server named.
//
// Please read /usr/share/doc/bind9/README.Debian.gz for information on the
// structure of BIND configuration files in Debian, *BEFORE* you customize
// this configuration file.
//
// If you are just adding zones, please do that in /etc/bind/named.conf.local
include "/etc/bind/named.conf.options";
// prime the server with knowledge of the root servers
zone "." {
type hint;
file "/etc/bind/db.root";
};
// be authoritative for the localhost forward and reverse zones, and for
// broadcast zones as per RFC 1912
zone "localhost" {
type master;
file "/etc/bind/db.local";
};
zone "127.in-addr.arpa" {
type master;
file "/etc/bind/db.127";
};
zone "0.in-addr.arpa" {
type master;
file "/etc/bind/db.0";
};
zone "255.in-addr.arpa" {
type master;
file "/etc/bind/db.255";
};
// zone "com" { type delegation-only; };
// zone "net" { type delegation-only; };
// From the release notes:
// Because many of our users are uncomfortable receiving undelegated answers
// from root or top level domains, other than a few for whom that behaviour
// has been trusted and expected for quite some length of time, we have now
// introduced the "root-delegations-only" feature which applies delegation-only
// logic to all top level domains, and to the root domain. An exception list
// should be specified, including "MUSEUM" and "DE", and any other top level
// domains from whom undelegated responses are expected and trusted.
