Ja, vielen Dank !
zulu.reversed:
Code:
$ORIGIN 0.168.192.in-addr.arpa.
$TTL 86400 ; 1 day
@ IN SOA zulu.zulu.de. root.zulu.de. (
2004021003 ; serial
28800 ; refresh (8 hours)
7200 ; retry (4 hours)
604800 ; expire (5 weeks 6 days 16 hours)
86400 ; minimum (1 day)
)
NS zulu.zulu.de.
$TTL 3600 ; 1 hour
111 PTR pop.zulu.de.
111 PTR smtp.zulu.de.
;
; Workstations
;
111 PTR zulu.
zulu.zone:
Code:
$ORIGIN zulu.de.
$TTL 86400 ; 1 day
@ IN SOA zulu.zulu.de. root.zulu.de. (
2004022406 ; serial
600 ; refresh (1 day)
2H ; retry (6 hours)
1W ; expire (5 weeks 6 days 16 hours)
1D ; minimum (1 hour)
)
IN NS 192.168.0.111.
IN MX 10 zulu.zulu.de. ; Primary Mail Exchanger
localhost.zulu.de IN A 127.0.0.1
; Aliase
pop.zulu.de IN CNAME zulu.zulu.de
smtp.zulu.de IN CNAME zulu.zulu.de
;
; Workstations
;
zulu.zulu.de. A 192.168.0.111
/var/log/messages:
Code:
Feb 24 16:48:04 zulu named[4554]: starting BIND 9.2.2 -u named -d 15
Feb 24 16:48:04 zulu named[4554]: using 1 CPU
Feb 24 16:48:04 zulu named[4556]: loading configuration from '/etc/named.conf'
Feb 24 16:48:04 zulu named[4556]: no IPv6 interfaces found
Feb 24 16:48:04 zulu named[4556]: listening on IPv4 interface lo, 127.0.0.1#53
Feb 24 16:48:04 zulu named[4556]: listening on IPv4 interface eth0, 192.168.0.111#53
Feb 24 16:48:04 zulu named[4556]: command channel listening on 127.0.0.1#953
Feb 24 16:48:04 zulu named[4556]: zone 0.0.127.in-addr.arpa/IN: loaded serial 1997022700
Feb 24 16:48:04 zulu named[4556]: zone 0.168.192.in-addr.arpa/IN: loaded serial 2004021003
Feb 24 16:48:04 zulu named[4556]: zone zulu.de/IN: loaded serial 2004022406
Feb 24 16:48:04 zulu named[4556]: running
Feb 24 16:48:04 zulu named[4556]: zone zulu.de/IN: sending notifies (serial 2004022406)
Feb 24 16:48:04 zulu named[4556]: zone 0.168.192.in-addr.arpa/IN: sending notifies (serial 2004021003)
Allerdings:
http://zulu.zulu.de/ ergibt den lokalen Webserver und nicht wie gewollt:
http://zulu.de/