Very Computer

by **J. T** » Fri, 13 Jul 2001 21:17:29

I was wondering what needs to be converted below for it to work with linux
named... this is from a Solaris 2.5.1 machine.

------ From Solaris machine --------

#From file rutherford.k12.nc.us

1997040810 ; Serial
21600 ; Refresh - 6 hours
3600 ; Retry - 1 hour
3600000 ; Expire - 41 days 16 hrs
86400 ) ; Minimum - 1 day
;
; Name Server(s)
;
IN NS eclipse.rutherford.k12.nc.us.
;
; Top-level MX record(s)
;
IN MX 10 eclipse.rutherford.k12.nc.us.
;
; CNAMES
;
www IN CNAME eclipse.rutherford.k12.nc.us.
pop IN CNAME eclipse.rutherford.k12.nc.us.
irc IN CNAME eclipse.rutherford.k12.nc.us.
loghost IN CNAME eclipse.rutherford.k12.nc.us.
ns IN CNAME eclipse.rutherford.k12.nc.us.
;
; Hosts
; Unrouted Network 207.203.141, Netmask 255.255.255.0
;
c001 IN A 207.203.141.1
c003 IN A 207.203.141.3
# this goes up to 255

------ For intranet users -------
# from file 168.192.in-addr.arpa

;
; Authoritative data for rutherford.k12.nc.us.
; This is a network of fake addresses.

1997040810 ; Serial
21600 ; Refresh - 6 hours
3600 ; Retry - 1 hour
3600000 ; Expire - 41 days 16 hrs
86400 ) ; Minimum - 1 day

;
; Name Servers
;
IN NS eclipse.rutherford.k12.nc.us.

----- from 1.168.192.in-addr.arpa ------

;
; Authoritative data for rutherford.k12.nc.us.
; This is a network of fake addresses.

2001013101 ; Serial
21600 ; Refresh - 6 hours
3600 ; Retry - 1 hour
3600000 ; Expire - 41 days 16 hrs
86400 ) ; Minimum - 1 day

;
; Name Servers
;
IN NS eclipse.rutherford.k12.nc.us.
;
; Hosts
;
2 IN PTR eclipse.rutherford.k12.nc.us.

# End of paste.

Copying them over and editing the boot.conf to include these files, loads
these with errors. I have tried looking at other examples listed for linux
on
the net and modifying these without any luck, my lack of non-experience with
setting up named is killing me here... Also... do I need both the 192.168.1
and 192.168 when I define the 192.168? That's the way the solaris machine
was
setup. These file pasted above are running on the solaris machine currently
and haven't been modified. The other required named files are working (ones
that defaultly came setup with linux).

Thanks for any help,
JT

by **Dean Thompso** » Sat, 14 Jul 2001 14:34:04

Hi!,

Quote:> Copying them over and editing the boot.conf to include these files, loads
> these with errors. I have tried looking at other examples listed for linux
> on the net and modifying these without any luck, my lack of non-experience
> with setting up named is killing me here... Also... do I need both the
> 192.168.1 and 192.168 when I define the 192.168? That's the way the solaris
> machine was setup. These file pasted above are running on the solaris
> machine currently and haven't been modified. The other required named files
> are working (ones that defaultly came setup with linux).

Thanks for the zone files, but perhaps a quicker way of finding the faults,
would be to see the output of the bind errors. Additionally, it would also be
helpful to see which version of BIND you are using. If you are using 9, you
will need to add the TTL directive. You will need this even though it is
specified in the SOA.

See ya

Dean Thompson

Very Computer

Named reverse lookup files problem (converting from Solaris to Linux)

Named reverse lookup files problem (converting from Solaris to Linux)

Named reverse lookup files problem (converting from Solaris to Linux)