Forward zone files not working on Bind 9.3.6-P1 for Solaris and OpenSolaris??

[Kevin Darcy]

If you're loading a zone as "sgd.test", then an owner name of ns-m.test 
doesn't belong in it, and BIND is correct to reject it.

Either change that name to something under sgd.test, or set up a 
separate zone for ns-m.test or anything above that in the hierarchy 
(i.e. "test" or root).

I don't know why this would have worked in your old environment, but 
then again I don't know what version "BIND 9 from Blastwave" is, or what 
you mean by "skeleton of the files".

- Kevin

Kaya Saman wrote:
> Hi,
>
> I'm not sure if there is a syntax error or if I've missed to include 
> something but for some reason my forward zone files don't seem to be 
> working :-(
>
> I pulled the skeleton of the files straight off my working Solaris 9 
> boxes which use Bind 9 from Blastwave! I checked and double checked 
> the paths in named.conf as Blastwave has all it's files stored in 
> /opt/csw/.... and /etc/opt/csw... directories; while with native Sol10 
> and OpenSol Bind I can use /etc and /var/named respectively.
>
> The zone files 'domain' are just so that I can use the Sun Secure 
> Global Desktop software in a test platform which is why I have decided 
> to allocated the FQDN of sgd.test.
>
> These are the zone files:
>
> {Forward}
>
> ;
> ; BIND data file for example.com
> ;
> $TTL 1d
> @ IN SOA ns-m.test. mail.test. (
> 2009103007 ; Serial
> 7200 ; Refresh
> 120 ; Retry
> 2419200 ; Expire
> 86400) ; Default TTL
> ;
> IN NS ns-m.test.
> ns-m.test. IN A 192.168.2.24
> sgd.test. IN A 192.168.2.24
>
> {Reverse}
>
> $TTL 1d ;
> $ORIGIN 2.168.192.IN-ADDR.ARPA.
> @ IN SOA ns-m.test. mail.test. (
> 2009103002
> 7200
> 120
> 2419200
> 86400
> )
>
> IN NS ns-m.test.
> 24 IN PTR ns-m.test.
> 24 IN PTR sgd.test.
>
> This is the error I receive from OpenSol:
>
> Oct 30 13:24:11 sgd named[2025]: [ID 873579 daemon.notice] starting 
> BIND 9.3.6-P1
> Oct 30 13:24:11 sgd named[2025]: [ID 873579 daemon.notice] command 
> channel listening on 127.0.0.1#953
> Oct 30 13:24:11 sgd named[2025]: [ID 873579 daemon.warning] 
> /var/named/sgd.db:13: ignoring out-of-zone data (ns-m.test)
> Oct 30 13:24:11 sgd named[2025]: [ID 873579 daemon.notice] running
>
> Also the same error for Sol10:
>
> Oct 30 13:43:31 sgd named[1857]: [ID 873579 daemon.notice] starting 
> BIND 9.3.6-P1
> Oct 30 13:43:31 sgd named[1857]: [ID 873579 daemon.notice] command 
> channel listening on 127.0.0.1#953
> Oct 30 13:43:31 sgd named[1857]: [ID 873579 daemon.warning] 
> /var/named/sgd.db:13: ignoring out-of-zone data (ns-m.test)
> Oct 30 13:43:31 sgd named[1857]: [ID 873579 daemon.notice] running
>
> Reverse lookups are all perfectly ok!!
>
> What am I missing here???
>
> In Debian Etch ages ago I had to include the statement:
>
> test. IN NS ns-m.test.
>
> but of course with this version of Bind it doesn't like it.....
>
> I am completely lost as I've said above on my Sol9 boxes running Bind 
> 9 from Blastwave all is fine using exact same syntax in zone files so 
> why don't my forward zone files work now???
>
> Many thanks for any help!
>
> --Kaya
>
>
>
>
> _______________________________________________
> bind-users mailing list
> bind-users at lists.isc.org
> https://lists.isc.org/mailman/listinfo/bind-users
>
>