| 1 |
On 26 March 2006 10:01, Hiren Dave wrote: |
| 2 |
|
| 3 |
Alright, I'll bite. ;-) |
| 4 |
|
| 5 |
Some small errors. |
| 6 |
|
| 7 |
> server1.guru.com (192.168.0.2) Primary DNS Server |
| 8 |
> server2.guru.com (192.168.0.3) Secondary DNS Server |
| 9 |
> |
| 10 |
> => Here is my configuration file for server1.guru.com machine. |
| 11 |
> |
| 12 |
> #######################/etc/resolve.conf############################## |
| 13 |
> domain guru.com |
| 14 |
> search server1.guru.com server2.guru.com |
| 15 |
|
| 16 |
search guru.com |
| 17 |
|
| 18 |
(the search string gets appended to non-qualified names) |
| 19 |
|
| 20 |
> nameserver 192.168.0.2 |
| 21 |
> nameserver 192.168.0.3 |
| 22 |
> ###################################################################### |
| 23 |
> ####################/var/named/chroot/etc/named.conf################## |
| 24 |
> options { |
| 25 |
> directory "/var/named"; |
| 26 |
> dump-file "/var/named/data/cache_dump.db"; |
| 27 |
> statistics-file "/var/named/data/named_stats.txt"; |
| 28 |
> allow-transfer { 192.168.0.3; 192.168.0.1; }; |
| 29 |
> allow-query { 192.168.0.0/24; localhost; }; |
| 30 |
> allow-recursion { 192.168.0.0/24; localhost; }; |
| 31 |
> }; |
| 32 |
|
| 33 |
allow-tansfer: take out 192.168.0.1; it's unnecessary. |
| 34 |
|
| 35 |
[ snip ] |
| 36 |
|
| 37 |
> zone "server1.guru.com" IN { |
| 38 |
|
| 39 |
make this: zone "guru.com" IN { |
| 40 |
|
| 41 |
> type master; |
| 42 |
> file "server1.guru.com.zone"; |
| 43 |
|
| 44 |
make this: file "guru.com"; (not strictly necessary) |
| 45 |
|
| 46 |
> allow-query { any; }; |
| 47 |
|
| 48 |
In the general options, you restrict queries to your local network. Why do you |
| 49 |
now allow queries from anywhere? |
| 50 |
|
| 51 |
> allow-update { key rndckey; }; |
| 52 |
> }; |
| 53 |
|
| 54 |
|
| 55 |
|
| 56 |
> #include "/etc/rndc.key"; |
| 57 |
> ###################################################################### |
| 58 |
> #######/var/named/chroot/var/named/server1.guru.com.zone############## |
| 59 |
|
| 60 |
make the file "guru.co" |
| 61 |
|
| 62 |
> $TTL 86400 |
| 63 |
> @ IN SOA server1.guru.com. root.server1.guru.com. ( |
| 64 |
|
| 65 |
BTW, *not* a good idea to make "root" the technical contact for your domain. |
| 66 |
|
| 67 |
Now most stuff below can be much easier. |
| 68 |
> 1 ; serial |
| 69 |
> 300 ; refresh (5 minutes) |
| 70 |
> 10 ; retry (10 seconds) |
| 71 |
> 86400 ; expire (1 day) |
| 72 |
> 600 ; minimum (10 minutes) |
| 73 |
> ) |
| 74 |
> |
| 75 |
> @ IN NS server1.guru.com. |
| 76 |
> @ IN MX 10 server1.guru.com. |
| 77 |
> |
| 78 |
> server1.guru.com. IN A 192.168.0.2 |
| 79 |
> server2.guru.com. IN A 192.168.0.3 |
| 80 |
> win2k.guru.com. IN A 192.168.0.1 |
| 81 |
> |
| 82 |
> www1 CNAME server1.guru.com. |
| 83 |
> www2 CNAME server2.guru.com. |
| 84 |
> www3 CNAME win2k.guru.com. |
| 85 |
> |
| 86 |
> server2 IN MX 0 server1.guru.com. |
| 87 |
> win2k IN MX 0 server1.guru.com. |
| 88 |
|
| 89 |
The lines above can now look this way: |
| 90 |
|
| 91 |
IN NS server1.guru.com. |
| 92 |
IN NS server2.guru.com. |
| 93 |
|
| 94 |
IN MX 10 server1.guru.co. |
| 95 |
*.guru.com IN MX 10 server1.guru.com. |
| 96 |
|
| 97 |
server1 IN A 192.168.0.2 |
| 98 |
server2 IN A 192.168.0.3 |
| 99 |
win2k IN A 192.168.0.1 |
| 100 |
|
| 101 |
www1 CNAME server1 |
| 102 |
www2 CNAME server2 |
| 103 |
www3 CNAME win2k |
| 104 |
|
| 105 |
(Note where I put a fullstop at the end of a name and where not. It's |
| 106 |
important. Your MX statements above are contradictory. So I don't know |
| 107 |
exactly which box your email server is and if you really have more than one. |
| 108 |
If so you have to adjust my two MX entries above.) |
| 109 |
|
| 110 |
Adjust server2 accordingly. |
| 111 |
|
| 112 |
I cannot guarantee that I caught all mistakes. Just try it out. |
| 113 |
|
| 114 |
Uwe |
| 115 |
|
| 116 |
-- |
| 117 |
Why do consumers keep buying products they will live to curse? |
| 118 |
-- |
| 119 |
gentoo-user@g.o mailing list |
Archives