You might want to set your serial to a date format like:

2006032600

When you do an update on the same day you just increment the last digit(s).

2006032601

You are more likely to remember when you have done updates with a date.

On Sun, 26 Mar 2006, Hiren Dave wrote:

Hi Uwe,

The main problem in my configuration was this:
search server1.guru.com server2.guru.com
search guru.com
zone "server1.guru.com" IN {
make this: zone "guru.com" IN {

After changing this, my dns server is working fine. Thanks a lot dude.

Hiren

On 3/26/06, Uwe Thiem <[EMAIL PROTECTED]> wrote:

On 26 March 2006 10:01, Hiren Dave wrote:

Alright, I'll bite. ;-)

Some small errors.

server1.guru.com (192.168.0.2)  Primary DNS Server
server2.guru.com (192.168.0.3)  Secondary DNS Server

=> Here is my configuration file for server1.guru.com machine.

#######################/etc/resolve.conf##############################
domain guru.com
search server1.guru.com server2.guru.com

search guru.com

(the search string gets appended to non-qualified names)

nameserver 192.168.0.2
nameserver 192.168.0.3
######################################################################
####################/var/named/chroot/etc/named.conf##################
options {
 directory "/var/named";
 dump-file "/var/named/data/cache_dump.db";
 statistics-file "/var/named/data/named_stats.txt";
 allow-transfer { 192.168.0.3; 192.168.0.1; };
 allow-query { 192.168.0.0/24; localhost; };
 allow-recursion { 192.168.0.0/24; localhost; };
};

allow-tansfer: take out 192.168.0.1; it's unnecessary.

[ snip ]

zone "server1.guru.com" IN {

make this: zone "guru.com" IN {

 type master;
 file "server1.guru.com.zone";

make this: file "guru.com";   (not strictly necessary)

 allow-query { any; };

In the general options, you restrict queries to your local network. Why do
you
now allow queries from anywhere?

 allow-update { key rndckey; };
};



#include "/etc/rndc.key";
######################################################################
#######/var/named/chroot/var/named/server1.guru.com.zone##############

make the file "guru.co"

$TTL 86400
@ IN SOA server1.guru.com. root.server1.guru.com. (

BTW, *not* a good idea to make "root" the technical contact for your
domain.

Now most stuff below can be much easier.
    1          ; serial
    300    ; refresh (5 minutes)
    10         ; retry (10 seconds)
    86400      ; expire (1 day)
    600        ; minimum (10 minutes)
    )

@ IN NS server1.guru.com.
@ IN MX 10 server1.guru.com.

server1.guru.com. IN A 192.168.0.2
server2.guru.com. IN A 192.168.0.3
win2k.guru.com.  IN A 192.168.0.1

www1   CNAME server1.guru.com.
www2   CNAME server2.guru.com.
www3   CNAME win2k.guru.com.

server2 IN MX 0 server1.guru.com.
win2k IN MX 0 server1.guru.com.

The lines above can now look this way:

       IN      NS      server1.guru.com.
       IN      NS      server2.guru.com.

       IN      MX      10      server1.guru.co.
*.guru.com      IN      MX      10      server1.guru.com.

server1 IN      A       192.168.0.2
server2 IN      A       192.168.0.3
win2k   IN      A       192.168.0.1

www1    CNAME   server1
www2    CNAME   server2
www3    CNAME   win2k

(Note where I put a fullstop at the end of a name and where not. It's
important. Your MX statements above are contradictory. So I don't know
exactly which box your email server is and if you really have more than
one.
If so you have to adjust my two MX entries above.)

Adjust server2 accordingly.

I cannot guarantee that I caught all mistakes. Just try it out.

Uwe

--
Why do consumers keep buying products they will live to curse?
--
gentoo-user@gentoo.org mailing list




--
Bryan Whitehead
Email:[EMAIL PROTECTED]
--
gentoo-user@gentoo.org mailing list

Reply via email to