1 |
You might want to set your serial to a date format like: |
2 |
|
3 |
2006032600 |
4 |
|
5 |
When you do an update on the same day you just increment the last |
6 |
digit(s). |
7 |
|
8 |
2006032601 |
9 |
|
10 |
You are more likely to remember when you have done updates with a date. |
11 |
|
12 |
On Sun, 26 Mar 2006, Hiren Dave wrote: |
13 |
|
14 |
> Hi Uwe, |
15 |
> |
16 |
> The main problem in my configuration was this: |
17 |
>> search server1.guru.com server2.guru.com |
18 |
> search guru.com |
19 |
>> zone "server1.guru.com" IN { |
20 |
> make this: zone "guru.com" IN { |
21 |
> |
22 |
> After changing this, my dns server is working fine. Thanks a lot dude. |
23 |
> |
24 |
> Hiren |
25 |
> |
26 |
> On 3/26/06, Uwe Thiem <uwix@××××.na> wrote: |
27 |
> |
28 |
>> On 26 March 2006 10:01, Hiren Dave wrote: |
29 |
>> |
30 |
>> Alright, I'll bite. ;-) |
31 |
>> |
32 |
>> Some small errors. |
33 |
>> |
34 |
>>> server1.guru.com (192.168.0.2) Primary DNS Server |
35 |
>>> server2.guru.com (192.168.0.3) Secondary DNS Server |
36 |
>>> |
37 |
>>> => Here is my configuration file for server1.guru.com machine. |
38 |
>>> |
39 |
>>> #######################/etc/resolve.conf############################## |
40 |
>>> domain guru.com |
41 |
>>> search server1.guru.com server2.guru.com |
42 |
>> |
43 |
>> search guru.com |
44 |
>> |
45 |
>> (the search string gets appended to non-qualified names) |
46 |
>> |
47 |
>>> nameserver 192.168.0.2 |
48 |
>>> nameserver 192.168.0.3 |
49 |
>>> ###################################################################### |
50 |
>>> ####################/var/named/chroot/etc/named.conf################## |
51 |
>>> options { |
52 |
>>> directory "/var/named"; |
53 |
>>> dump-file "/var/named/data/cache_dump.db"; |
54 |
>>> statistics-file "/var/named/data/named_stats.txt"; |
55 |
>>> allow-transfer { 192.168.0.3; 192.168.0.1; }; |
56 |
>>> allow-query { 192.168.0.0/24; localhost; }; |
57 |
>>> allow-recursion { 192.168.0.0/24; localhost; }; |
58 |
>>> }; |
59 |
>> |
60 |
>> allow-tansfer: take out 192.168.0.1; it's unnecessary. |
61 |
>> |
62 |
>> [ snip ] |
63 |
>> |
64 |
>>> zone "server1.guru.com" IN { |
65 |
>> |
66 |
>> make this: zone "guru.com" IN { |
67 |
>> |
68 |
>>> type master; |
69 |
>>> file "server1.guru.com.zone"; |
70 |
>> |
71 |
>> make this: file "guru.com"; (not strictly necessary) |
72 |
>> |
73 |
>>> allow-query { any; }; |
74 |
>> |
75 |
>> In the general options, you restrict queries to your local network. Why do |
76 |
>> you |
77 |
>> now allow queries from anywhere? |
78 |
>> |
79 |
>>> allow-update { key rndckey; }; |
80 |
>>> }; |
81 |
>> |
82 |
>> |
83 |
>> |
84 |
>>> #include "/etc/rndc.key"; |
85 |
>>> ###################################################################### |
86 |
>>> #######/var/named/chroot/var/named/server1.guru.com.zone############## |
87 |
>> |
88 |
>> make the file "guru.co" |
89 |
>> |
90 |
>>> $TTL 86400 |
91 |
>>> @ IN SOA server1.guru.com. root.server1.guru.com. ( |
92 |
>> |
93 |
>> BTW, *not* a good idea to make "root" the technical contact for your |
94 |
>> domain. |
95 |
>> |
96 |
>> Now most stuff below can be much easier. |
97 |
>>> 1 ; serial |
98 |
>>> 300 ; refresh (5 minutes) |
99 |
>>> 10 ; retry (10 seconds) |
100 |
>>> 86400 ; expire (1 day) |
101 |
>>> 600 ; minimum (10 minutes) |
102 |
>>> ) |
103 |
>>> |
104 |
>>> @ IN NS server1.guru.com. |
105 |
>>> @ IN MX 10 server1.guru.com. |
106 |
>>> |
107 |
>>> server1.guru.com. IN A 192.168.0.2 |
108 |
>>> server2.guru.com. IN A 192.168.0.3 |
109 |
>>> win2k.guru.com. IN A 192.168.0.1 |
110 |
>>> |
111 |
>>> www1 CNAME server1.guru.com. |
112 |
>>> www2 CNAME server2.guru.com. |
113 |
>>> www3 CNAME win2k.guru.com. |
114 |
>>> |
115 |
>>> server2 IN MX 0 server1.guru.com. |
116 |
>>> win2k IN MX 0 server1.guru.com. |
117 |
>> |
118 |
>> The lines above can now look this way: |
119 |
>> |
120 |
>> IN NS server1.guru.com. |
121 |
>> IN NS server2.guru.com. |
122 |
>> |
123 |
>> IN MX 10 server1.guru.co. |
124 |
>> *.guru.com IN MX 10 server1.guru.com. |
125 |
>> |
126 |
>> server1 IN A 192.168.0.2 |
127 |
>> server2 IN A 192.168.0.3 |
128 |
>> win2k IN A 192.168.0.1 |
129 |
>> |
130 |
>> www1 CNAME server1 |
131 |
>> www2 CNAME server2 |
132 |
>> www3 CNAME win2k |
133 |
>> |
134 |
>> (Note where I put a fullstop at the end of a name and where not. It's |
135 |
>> important. Your MX statements above are contradictory. So I don't know |
136 |
>> exactly which box your email server is and if you really have more than |
137 |
>> one. |
138 |
>> If so you have to adjust my two MX entries above.) |
139 |
>> |
140 |
>> Adjust server2 accordingly. |
141 |
>> |
142 |
>> I cannot guarantee that I caught all mistakes. Just try it out. |
143 |
>> |
144 |
>> Uwe |
145 |
>> |
146 |
>> -- |
147 |
>> Why do consumers keep buying products they will live to curse? |
148 |
>> -- |
149 |
>> gentoo-user@g.o mailing list |
150 |
>> |
151 |
>> |
152 |
> |
153 |
|
154 |
-- |
155 |
Bryan Whitehead |
156 |
Email:driver@×××××××××.net |
157 |
-- |
158 |
gentoo-user@g.o mailing list |