Starto Server und Eigenen namensserver
Posted: 2005-05-18 10:31
hallo ich bins wieder mit einem Problem habe nun einen neuen Strato server mit confix 3 ect .pp alles standart von strao installiert und funzt
daten
Domain war beim server dabei
wsn
der Namensserver eintrag für bestellte domains soll ns.ws.de sein
nun möchte ich aber einen eigenen namensserver dort laufen lassen um die bei schlundtechnologie regestrierten domains aud meinem eigenen Namensserver (primary) laufen zu lassen
ich habe alles wie in den vorigen beiträgen gemacht aber wenn ich dann in der console dig @ip domain any eingebe sagt er mir
<<>> DiG 9.2.2 <<>> @85.214.xxx.xxx maty.de any
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6504
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 5, AUTHORITY: 0, ADDITIONAL: 1
;; QUESTION SECTION:
;maty.de. IN ANY
;; ANSWER SECTION:
maty.de. 86400 IN MX 10 mail.maty.de.
maty.de. 86400 IN NS ns.
maty.de. 86400 IN NS ns2. (wie bekomme ich da e hin)
maty.de. 86400 IN SOA ns.server.de. hostmaster.server.de. 2005051501 10800 3600 604800 86400
maty.de. 86400 IN A 85.214.xxx.xxx
;; ADDITIONAL SECTION:
mail.maty.de. 86400 IN A 85.214.xxx.xxx
;; Query time: 2 msec
;; SERVER: 85.214.xx.xxx#53(85.214.17.166)
;; WHEN: Wed May 18 10:18:32 2005
;; MSG SIZE rcvd: 179
hier mal die datein zur kontrolle
ect/named.conf
# Copyright (c) 2001-2003 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/bind9/sample-config.
#
# A description of all available options can be found in
# /usr/share/doc/packages/bind9/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 { 10.11.12.13; 10.11.12.14; };
# 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 53;
#transfer-source * port 53;
#notify-source * port 53;
# 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;
allow-transfer { 195.20.224.97; 195.20.225.34; };
allow-query {any; };
};
# 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 "localhost" in {
type master;
file "localhost.zone";
};
zone "0.0.127.in-addr.arpa" in {
type master;
file "127.0.0.zone";
};
zone "xxx.xxx.85.in-addr.arpa" in {
type master;
file "85.xxx.xx.zone";
};
zone "wn.de.in-addr.arpa" in {
type master;
file "wn.de.zone";
};
zone "maty.de.in-addr.arpa" in {
type master;
file "maty.zone";
zone "." in {
type hint;
file "root.hint";
};
# Include the meta include file generated by SuSEconfig.named. 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.
## CONFIXX
Include "/etc/named.confixx";
## /CONFIXX
[/code]
___________________________________________________________
/var/named/85.xxx.xxx.zone
_________________________________________________________
/var/named/maty.de.zone
_________________________________________________________
in der var/log/massage steht beim restarten des servers
____________________________________________________________l
dig @81.xxx.xxx.xxx maty.de any
gleich vorweg sicher habe ich mitbekommen
das er die file nicht findet aber warum nicht ?? wo liegt da der fehler
[/code]
daten
Domain war beim server dabei
wsn
der Namensserver eintrag für bestellte domains soll ns.ws.de sein
nun möchte ich aber einen eigenen namensserver dort laufen lassen um die bei schlundtechnologie regestrierten domains aud meinem eigenen Namensserver (primary) laufen zu lassen
ich habe alles wie in den vorigen beiträgen gemacht aber wenn ich dann in der console dig @ip domain any eingebe sagt er mir
<<>> DiG 9.2.2 <<>> @85.214.xxx.xxx maty.de any
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6504
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 5, AUTHORITY: 0, ADDITIONAL: 1
;; QUESTION SECTION:
;maty.de. IN ANY
;; ANSWER SECTION:
maty.de. 86400 IN MX 10 mail.maty.de.
maty.de. 86400 IN NS ns.
maty.de. 86400 IN NS ns2. (wie bekomme ich da e hin)
maty.de. 86400 IN SOA ns.server.de. hostmaster.server.de. 2005051501 10800 3600 604800 86400
maty.de. 86400 IN A 85.214.xxx.xxx
;; ADDITIONAL SECTION:
mail.maty.de. 86400 IN A 85.214.xxx.xxx
;; Query time: 2 msec
;; SERVER: 85.214.xx.xxx#53(85.214.17.166)
;; WHEN: Wed May 18 10:18:32 2005
;; MSG SIZE rcvd: 179
hier mal die datein zur kontrolle
ect/named.conf
# Copyright (c) 2001-2003 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/bind9/sample-config.
#
# A description of all available options can be found in
# /usr/share/doc/packages/bind9/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 { 10.11.12.13; 10.11.12.14; };
# 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 53;
#transfer-source * port 53;
#notify-source * port 53;
# 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;
allow-transfer { 195.20.224.97; 195.20.225.34; };
allow-query {any; };
};
# 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 "localhost" in {
type master;
file "localhost.zone";
};
zone "0.0.127.in-addr.arpa" in {
type master;
file "127.0.0.zone";
};
zone "xxx.xxx.85.in-addr.arpa" in {
type master;
file "85.xxx.xx.zone";
};
zone "wn.de.in-addr.arpa" in {
type master;
file "wn.de.zone";
};
zone "maty.de.in-addr.arpa" in {
type master;
file "maty.zone";
zone "." in {
type hint;
file "root.hint";
};
# Include the meta include file generated by SuSEconfig.named. 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.
## CONFIXX
Include "/etc/named.confixx";
## /CONFIXX
[/code]
___________________________________________________________
/var/named/85.xxx.xxx.zone
Code: Select all
$TTL 1W
@ IN SOA ns.ws.de. hostmaster.ws.de (
2005051701 ; serial
8H ; refresh
2H ; retry
1W ; expiry
12h) ; minimum
IN NS ns.
IN NS ns.schlund.de.
166 IN PTR ws.de.
/var/named/maty.de.zone
Code: Select all
$TTL 1W
@ IN SOA ns.ws.de. hostmaster.ws.de. (
2005051703 ; serial
8H ; refresh
2H ; retry
1W ; expiry
12h) ; minimum
IN NS ns.ws.de.
IN NS ns.schlund.de.
IN A 85.xxx.xx.xxx
* IN A 85.21x.xxx.xxx
www IN A 85.xxx.xxx.xxxin der var/log/massage steht beim restarten des servers
Code: Select all
May 18 10:01:12 hxxxxxx saslauthd[684]: detach_tty : master pid is: 684
May 18 10:01:12 hxxxxxx saslauthd[684]: ipc_init : listening on socket: /var/run/sasl2//mux
May 18 10:01:12 hxxxxxx named[688]: starting BIND 9.2.2 -t /var/lib/named -u named
May 18 10:01:12 hxxxxxx named[688]: using 1 CPU
May 18 10:01:12 hxxxxxx xinetd[683]: Reading included configuration file: /etc/xinetd.d/chargen-udp [file=/etc/xinetd.d/chargen-udp] [line=13]
May 18 10:01:12 hxxxxxx xinetd[683]: Reading included configuration file: /etc/xinetd.d/daytime [file=/etc/xinetd.d/daytime] [line=14]
May 18 10:01:12 hxxxxxx xinetd[683]: Reading included configuration file: /etc/xinetd.d/daytime-udp [file=/etc/xinetd.d/daytime-udp] [line=13]
May 18 10:01:12 hxxxxxx xinetd[683]: Reading included configuration file: /etc/xinetd.d/echo [file=/etc/xinetd.d/echo] [line=14]
May 18 10:01:13 hxxxxxx xinetd[683]: Reading included configuration file: /etc/xinetd.d/echo-udp [file=/etc/xinetd.d/echo-udp] [line=13]
May 18 10:01:13 hxxxxxx xinetd[683]: Reading included configuration file: /etc/xinetd.d/netstat [file=/etc/xinetd.d/netstat] [line=14]
May 18 10:01:13 hxxxxxx xinetd[683]: Reading included configuration file: /etc/xinetd.d/qpopper [file=/etc/xinetd.d/qpopper] [line=16]
May 18 10:01:13 hxxxxxx xinetd[683]: Reading included configuration file: /etc/xinetd.d/rsync [file=/etc/xinetd.d/rsync] [line=14]
May 18 10:01:13 hxxxxxx xinetd[683]: Reading included configuration file: /etc/xinetd.d/servers [file=/etc/xinetd.d/servers] [line=12]
May 18 10:01:13 hxxxxxx xinetd[683]: Reading included configuration file: /etc/xinetd.d/services [file=/etc/xinetd.d/services] [line=13]
May 18 10:01:13 hxxxxxx xinetd[683]: Reading included configuration file: /etc/xinetd.d/systat [file=/etc/xinetd.d/systat] [line=13]
May 18 10:01:13 hxxxxxx xinetd[683]: Reading included configuration file: /etc/xinetd.d/time [file=/etc/xinetd.d/time] [line=17]
May 18 10:01:13 hxxxxxx xinetd[683]: Reading included configuration file: /etc/xinetd.d/time-udp [file=/etc/xinetd.d/time-udp] [line=14]
May 18 10:01:13 hxxxxxx xinetd[683]: Reading included configuration file: /etc/xinetd.d/vsftpd [file=/etc/xinetd.d/vsftpd] [line=14]
May 18 10:01:13 hxxxxxx named[690]: loading configuration from '/etc/named.conf'
May 18 10:01:13 hxxxxxx xinetd[683]: removing chargen
May 18 10:01:13 hxxxxxx xinetd[683]: removing chargen
May 18 10:01:13 hxxxxxx xinetd[683]: removing daytime
May 18 10:01:13 hxxxxxx xinetd[683]: removing daytime
May 18 10:01:13 hxxxxxx xinetd[683]: removing echo
May 18 10:01:13 hxxxxxx xinetd[683]: removing echo
May 18 10:01:13 hxxxxxx xinetd[683]: removing netstat
May 18 10:01:13 hxxxxxx xinetd[683]: removing rsync
May 18 10:01:13 hxxxxxx xinetd[683]: removing servers
May 18 10:01:13 hxxxxxx xinetd[683]: removing services
May 18 10:01:13 hxxxxxx xinetd[683]: removing systat
May 18 10:01:13 hxxxxxx xinetd[683]: removing time
May 18 10:01:13 hxxxxxx xinetd[683]: removing time
May 18 10:01:13 hxxxxxx xinetd[683]: xinetd Version 2.3.12 started with libwrap loadavg options compiled in.
May 18 10:01:13 hxxxxxx xinetd[683]: Started working: 2 available services
May 18 10:01:13 hxxxxxx named[690]: listening on IPv6 interfaces, port 53
May 18 10:01:14 hxxxxxx named[690]: listening on IPv4 interface lo, 127.0.0.1#53
May 18 10:01:14 hxxxxxx named[690]: binding TCP socket: address in use
May 18 10:01:14 hxxxxxx named[690]: listening on IPv4 interface eth0, 85.214.17.166#53
May 18 10:01:14 hxxxxxx named[690]: binding TCP socket: address in use
May 18 10:01:14 hxxxxxx sshd[737]: Server listening on :: port 22.
May 18 10:01:14 hxxxxxx named[690]: zone 0.0.127.in-addr.arpa/IN: loaded serial 42
May 18 10:01:14 hxxxxxx named[690]: zone xxx.xxx.85.in-addr.arpa/IN: loading master file 85.xxx.xxx.zone: file not found
May 18 10:01:14 hxxxxxx named[690]: zone maty.de.in-addr.arpa/IN: loading master file maty.zone: file not found
May 18 10:01:14 hxxxxxx named[690]: zone ws.de.in-addr.arpa/IN: loading master file ws.de.zone: file not found
May 18 10:01:14 hxxxxxx named[690]: zone maty.de/IN: loaded serial 2005051501
May 18 10:01:14 hxxxxxx named[690]: zone ma.de/IN: loaded serial 2005051501
May 18 10:01:14 hxxxxxx named[690]: zone ws.de/IN: loaded serial 2005051501
May 18 10:01:14 hxxxxxx named[690]: zone localhost/IN: loaded serial 42
May 18 10:01:14 hxxxxxx named[690]: running
May 18 10:01:15 hxxxxxx kernel: klogd 1.4.1, log source = /proc/kmsg started.
May 18 10:01:15 hxxxxxx kernel: Inspecting /boot/System.map
May 18 10:01:16 hxxxxxx kernel: Loaded 21621 symbols from /boot/System.map.
May 18 10:01:16 hxxxxxx kernel: Symbols match kernel version 2.4.25.
May 18 10:01:16 hxxxxxx kernel: Loaded 28 symbols from 1 module.
May 18 10:01:20 hxxxxxx kernel: eth0: no IPv6 routers present
May 18 10:01:20 hxxxxxx kernel: keyboard: Timeout - AT keyboard not present?(f4)
May 18 10:01:28 hxxxxxx last message repeated 6 times
May 18 10:01:34 hxxxxxx /usr/sbin/cron[993]: (CRON) STARTUP (fork ok)
May 18 10:02:08 hxxxxxx sshd[1015]: Accepted keyboard-interactive/pam for root from ::ffff:82.83.143.87 port 2746 ssh2
May 18 10:02:08 hxxxxxx sshd[1015]: subsystem request for sftpdig @81.xxx.xxx.xxx maty.de any
Code: Select all
; <<>> DiG 9.2.2 <<>> @85.xxx.xxx.xxx maty.de any
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6504
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 5, AUTHORITY: 0, ADDITIONAL: 1
;; QUESTION SECTION:
;maty.de. IN ANY
;; ANSWER SECTION:
maty.de. 86400 IN MX 10 mail.maty.de.
maty.de. 86400 IN NS ns.server.de.
maty.de. 86400 IN NS ns2.server.de.
maty.de. 86400 IN SOA ns.server.de. hostmaster.server.de. 2005051501 10800 3600 604800 86400
mavty.de. 86400 IN A 85.xxx.xxx.xxx
;; ADDITIONAL SECTION:
mail.mavty.de. 86400 IN A 85.xxx.xxx.xxx
;; Query time: 2 msec
;; SERVER: 85.xxx.xxx.xxx#53(xx.xxx.xxx.xxx)
;; WHEN: Wed May 18 10:18:32 2005
;; MSG SIZE rcvd: 179
hxxxxxx:~ #das er die file nicht findet aber warum nicht ?? wo liegt da der fehler
Code: Select all
May 18 10:01:14 xxxxxx named[690]: zone maty.de.in-addr.arpa/IN: loading master file maty.zone: file not found