bind 9.1.2 zonefile trouble

bind 9.1.2 zonefile trouble

Post by SBiel » Sat, 16 Mar 2002 01:30:16



hi all,
I have a master nameserver running bind 8, I need to switch to a new
server running bind 9.1.2, I have copied the named.conf and the zone
files from the old to the new server. The new server starts and works
fine with the cache and the root zone, but It doesn't resolve any
address from the master zone files.

I can not find where is the error... any help? :-)

This is a master zone file:

                        2002031313      ; serial, todays date + todays
serial n
                        300             ; Refresh - 5 Minutes
                        60              ; Retry - 1 minute
                        1209600         ; Expire - 2 Weeks
                        43200)          ; Minimum - 12 Hours
;
                TXT     "Cobest srl"
                NS      mz01.vnet.it.        ; Inet Address of name
server
                NS      mz02.vnet.it.
                MX      10 mail.vnet.it.    ; Primary Mail Exchanger
                MX      20 mail.hal9001.net.      ; Secondary Mail
Exchanger
;
cobest.com.     A       195.191.47.238
;
www               CNAME   cobest.com.
and this is the named.conf file:

options {
        directory "/var/named";
        query-source address * port 53;
        allow-transfer {
            80.16.61.155;
            80.16.61.156;
            80.16.61.147;
            151.99.125.3;
        };
        listen-on port 53 {
            80.16.61.146;
        };

Quote:};

logging {
        category lame-servers { null; };
        category cname { null; };

Quote:};

zone "." {
        type hint;
        file "root.hints";

Quote:};

zone "0.0.127.in-addr.arpa" {
        type master;
        file "pz2/0.0.127.in-addr.arpa";

Quote:};

zone "cobest.com" {
          type master;
          file "pz2/cobest.com";
Quote:};

 
 
 

bind 9.1.2 zonefile trouble

Post by Barry Margoli » Sat, 16 Mar 2002 04:05:29



>I have a master nameserver running bind 8, I need to switch to a new
>server running bind 9.1.2, I have copied the named.conf and the zone
>files from the old to the new server. The new server starts and works
>fine with the cache and the root zone, but It doesn't resolve any
>address from the master zone files.

>I can not find where is the error... any help? :-)

Have you tried checking your log file to see named's error messages?

I notice you don't have a $TTL directive in the zone file.  BIND 8 was
permissive about this (it would revert to the old behavior of using the SOA
Minimum field as the default TTL), but I think BIND 9 requires it if you
don't have explicit TTLs on every record.

>This is a master zone file:


>                        2002031313      ; serial, todays date + todays
>serial n
>                        300             ; Refresh - 5 Minutes
>                        60              ; Retry - 1 minute
>                        1209600         ; Expire - 2 Weeks
>                        43200)          ; Minimum - 12 Hours
>;
>                TXT     "Cobest srl"
>                NS      mz01.vnet.it.        ; Inet Address of name
>server
>                NS      mz02.vnet.it.
>                MX      10 mail.vnet.it.    ; Primary Mail Exchanger
>                MX      20 mail.hal9001.net.      ; Secondary Mail
>Exchanger
>;
>cobest.com.     A       195.191.47.238
>;
>www               CNAME   cobest.com.
>and this is the named.conf file:

>options {
>        directory "/var/named";
>        query-source address * port 53;
>        allow-transfer {
>            80.16.61.155;
>            80.16.61.156;
>            80.16.61.147;
>            151.99.125.3;
>        };
>        listen-on port 53 {
>            80.16.61.146;
>        };
>};

>logging {
>        category lame-servers { null; };
>        category cname { null; };
>};

>zone "." {
>        type hint;
>        file "root.hints";
>};

>zone "0.0.127.in-addr.arpa" {
>        type master;
>        file "pz2/0.0.127.in-addr.arpa";
>};

>zone "cobest.com" {
>          type master;
>          file "pz2/cobest.com";
>};

--

Genuity, Woburn, MA
*** DON'T SEND TECHNICAL QUESTIONS DIRECTLY TO ME, post them to newsgroups.
Please DON'T copy followups to me -- I'll assume it wasn't posted to the group.

 
 
 

bind 9.1.2 zonefile trouble

Post by p.. » Sat, 16 Mar 2002 04:53:11



> hi all,
> I have a master nameserver running bind 8, I need to switch to a new
> server running bind 9.1.2, I have copied the named.conf and the zone
> files from the old to the new server. The new server starts and works
> fine with the cache and the root zone, but It doesn't resolve any
> address from the master zone files.

One: there is no real sense in using bind-9.1.2 , several things
have been fixed that motivates using current (9.2.0 )

two: whats written in the logfile ? May i guess "missing 4TTL " ??

three : it does answer right now :


; (1 server found)
;; res options: init recurs defnam dnsrch
;; got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2
             ^
           Auth bit
;; ANSWER SECTION:
cobest.com.             1H IN A         195.191.47.238

peter h

> I can not find where is the error... any help? :-)
> This is a master zone file:

>                         2002031313      ; serial, todays date + todays
> serial n
>                         300             ; Refresh - 5 Minutes
>                         60              ; Retry - 1 minute
>                         1209600         ; Expire - 2 Weeks
>                         43200)          ; Minimum - 12 Hours
> ;
>                 TXT     "Cobest srl"
>                 NS      mz01.vnet.it.        ; Inet Address of name
> server
>                 NS      mz02.vnet.it.
>                 MX      10 mail.vnet.it.    ; Primary Mail Exchanger
>                 MX      20 mail.hal9001.net.      ; Secondary Mail
> Exchanger
> ;
> cobest.com.     A       195.191.47.238
> ;
> www               CNAME   cobest.com.
> and this is the named.conf file:
> options {
>         directory "/var/named";
>         query-source address * port 53;
>         allow-transfer {
>             80.16.61.155;
>             80.16.61.156;
>             80.16.61.147;
>             151.99.125.3;
>         };
>         listen-on port 53 {
>             80.16.61.146;
>         };
> };

> logging {
>         category lame-servers { null; };
>         category cname { null; };
> };

> zone "." {
>         type hint;
>         file "root.hints";
> };

> zone "0.0.127.in-addr.arpa" {
>         type master;
>         file "pz2/0.0.127.in-addr.arpa";
> };

> zone "cobest.com" {
>           type master;
>           file "pz2/cobest.com";
> };

--
Peter H?kanson        
        IPSec  Sverige      (At the Riverside of Gothenburg, home of Volvo)
           Sorry about my e-mail address, but i'm trying to keep spam out.
           Remove "icke-reklam" and it works.
 
 
 

1. new BIND user asking for zonefile proofreading

Hello, I recently setup a chrooted install of bind 9.2.1 as per the
HOWTOs on linuxdoc and would like to have somebody proofread my
zonefile.  I updated the whois information for the domain on
Wednesday, and the new dns servers were reflected on Thursday, and
it's Sunday and I still cannot resolve the domain.  I think I found &
fixed one problem (I had the SOA pointing to the wrong nameserver) but
I was wondering if somebody would be kind enough to check this over
for any other errors.


info, but dig +trace still does not resolve.  Before I fixed this, the
TTL was 3D and the host after SOA was ns.fileswapper.com... hopefully
it will now work.  Any fixes or suggestions welcome.

TIA.

Zone record follows .......................................................


hostmaster.fileswapper.com. (
                                2002081112       ; Serial
                                2H      ; Refresh
                                2H      ; Retry
                                1W      ; Expire
                                1D)     ; Minimum TTL
;
                        NS      ns1.fileswapper.com.
                        NS      ns2.fileswapper.com.

                        MX      10      mail    ;

localhost               A       127.0.0.1

ns1                     A       63.143.133.137
ns2                     A       63.143.133.138

fileswapper.com.        A               24.90.207.162
                        TXT             "The webserver"
*.fileswapper.com.      IN CNAME        fileswapper.com.

mail                    A               24.90.207.162

2. After E2K SP1 cannot use MMC for advance feature

3. Bind 9 zonefile-format

4. Palm wap browser tru wap phone with no isp

5. Bind/InterNic/ZoneFile

6. Pcmcia Network card

7. Is this zonefile legal or should it be changed?

8. 68000 Assembler/disassembler...

9. zonefile migration from 8.2.3 to 9.1.1rc4 -working example required

10. cnames in a zonefile?

11. Zonefile Updates :: Serial Not Accepted

12. zonefile record question

13. zonefile via DHCP