How to set SOA records?

L

lowbasic

New member
Joined
May 11, 2009
Messages
4
I set up this server a few months ago and now and then the nameserver doesn't resolve.
I ran a little test and it said there were no valid SOA records found.

Any help on this one?
 
Guess your zone file is messed. Login to the shell and look at the zone file manually.
 
can't directly find anything wrong :s

named.conf:
Code: 
// 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;

        allow-transfer { none; };
};

//
// a caching only nameserver config
//
controls {
        inet 127.0.0.1 allow { localhost; } keys { rndckey; };
};
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; };
};

include "/etc/rndc.key";

zone "publimediasvr.be" { type master; file "/var/named/publimediasvr.be.db"; };

the zone file:
Code: 
$TTL 14400
@       IN      SOA     ns1.publimediasvr.be.      hostmaster.publimediasvr.be. (
                                                2009032301
                                                14400
                                                3600
                                                1209600
                                                86400 )

publimediasvr.be.       14400   IN      NS      ns1.publimediasvr.be.
publimediasvr.be.       14400   IN      NS      ns2.publimediasvr.be.

ftp     14400   IN      A       86.39.132.41
localhost       14400   IN      A       127.0.0.1
mail    14400   IN      A       86.39.132.41
pop     14400   IN      A       86.39.132.41
publimediasvr.be.       14400   IN      A       86.39.132.41
smtp    14400   IN      A       86.39.132.41
stream  14400   IN      A       86.39.132.38
www     14400   IN      A       86.39.132.41

publimediasvr.be.       14400   IN      MX      10 mail

publimediasvr.be.       14400   IN      TXT     "v=spf1 a mx ip4:86.39.132.41 ?all"
 
Not required if you register the nameservers at your registrar.
 
Having a top level domain nameserver sending a glue record of the domain nameserver IP address doesn't mean that you can just leave out its record, even if they are redundant in some cases.
 
tillo said:
Having a top level domain nameserver sending a glue record of the domain nameserver IP address doesn't mean that you can just leave out its record, even if they are redundant in some cases.
Click to expand...

Nice opinion.
 
scsi,

While you usually don't need an A record at your nameserver if you've got a glue record, sometimes you do.

And here's why:

Because if you're looking for an NS record and your immediate upstream nameserver (the one you set in your /etc/resolv.conf file) already has any record for the domain in which you're looking, it won't query the root.

And even though you can argue that it should know the IP# of the nameserver, that's not the way it works. It'll ask the nameserver for the IP# of the nameserver. And it won't get it.

Sorry, but in real life, that's the way it works.

Jeff
 
You must log in or register to reply here.
Back
Top