Ik heb wat probleempjes met mijn nameserver.
soms werken de domeinen wel maar meestal niet. dit is heel irritant aangezien er flink bezocht en gemailed wordt naar sommige domeinen.
Ik zal mijn zonefile ff posten want ik snap er geen fluit meer van.
mijn named.conf
soms werken de domeinen wel maar meestal niet. dit is heel irritant aangezien er flink bezocht en gemailed wordt naar sommige domeinen.
Ik zal mijn zonefile ff posten want ik snap er geen fluit meer van.
code:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
| $ttl 86400
@ IN SOA ns.taononstop.com. webmaster.taononstop.com. (
2001090603 ; Serial
; 21600 ; Refresh 6 hours
14400 ; Refresh 4 hours
; 10800 ; Refresh 3 hours
3600 ; Retry 1 hour
604800 ; Expire 7 days
86400 ) ; Minimum 24 hours
taononstop.com. IN NS ns.taononstop.com.
IN NS ns.enigmavoice.com.
IN MX 50 smtp.gambitsplace.com.
IN A xxx.xxx.xxx.xxx
IN A xxx.xxx.xxx.xxx
localhost IN A 127.0.0.1
www IN A xxx.xxx.xxx.xxx
ftp IN A xxx.xxx.xxx.xxx
mail IN A xxx.xxx.xxx.xxx
IN MX 50 smtp.gambitsplace.com.
smtp IN A xxx.xxx.xxx.xxx
pop3 IN A xxx.xxx.xxx.xxx
IN MX 50 mail.gambitsplace.com.
ns IN A xxx.xxx.xxx.xxx
dolly IN A xxx.xxx.xxx.xxx |
mijn named.conf
code:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
| // generated by named-bootconf.pl
options {
directory "/var/named";
/*
* 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;
};
//
// a caching only nameserver config
//
zone "." IN {
type hint;
file "named.ca";
};
zone "localhost" IN {
type master;
file "localhost.zone";
allow-update { none; };
};
zone "0.0.127.in-addr.arpa" IN {
type master;
file "named.local";
allow-update { none; };
};
zone "0.0.10.IN-ADDR.ARPA"{
type master;
file "0.0.10.rev";
notify yes;
};
#key "key" {
# algorithm hmac-md5;
# secret "AvMoDXpiYXwQjnLYlFsWhJanowwztFfrf0IkxRVZNwsEZBGiWWMeyhUGINDa";
#};
zone "babeforce.com" in { type master; file "babeforce.com"; };
zone "gambitsplace.com" in { type master; file "gambitsplace.com"; };
zone "taononstop.com" in { type master; file "taononstop.com"; };
zone "nirvanadiscography.com" in { type master; file "nirvanadiscography.com"; };
zone "tattooshop-hilversum.nl" in { type master; file "tattooshop-hilversum.nl"; };
zone "saiyan-power.com" in { type master; file "saiyan-power.com"; };
zone "hiele-online.com" in { type master; file "hiele-online.com"; };
zone "bonesplace.com" in { type master; file "bonesplace.com"; };
zone "bikez-n-stuff.com" in { type master; file "bikez-n-stuff.com"; };
zone "rasputinfo.com" in { type master; file "rasputinfo.com"; };
zone "borismoose.com" in { type master; file "borismoose.com"; }; |
It's not DNS. There's no way it's DNS. It was DNS. --The Sysadmin haiku