> > > Amazing, but it doesn't work!
> >
> > What doesn't work, and in what way doesn't it work?
>
> Well, I created a record in /etc/named.conf
>
> zone "zone.domain.com" {
> type slave;
> file "named.zone.hosts";
> masters {
> 192.168.0.1;
> };
> };
Has 192.168.0.1 been configured to be a master for zone.domain.com? If
so, then what does the zone file for zone.domain.com look like?
> in /var/named/named.hosts I added:
>
> IN NS ns.zone.domain.com
There should be a trailing dot here, i.e.
IN NS ns.zone.domain.com.
^
> I've changed serial and so on. And yes I succeed in resolving the subdomain
> zone.domain.com from my primary name server, but from out side
> nslookup ns.zone.domain.com
> doesn't resolve the host
> and
> nslookup ns.zone.domain.com ns.domain.com
> returns the address of ns.domain.com, but not the address of
> ns.zone.domain.com
>
> I've properly created the named records and configuration file on
> ns.zone.domain.com, resolve.conf etc.
> I added in options the ip of ns.zone.domain.com as forwarder.
> Seems everything is OK but still it doen't work.
> I don't know if it is a named problem or slow zone transfer (which I
> consider not possible - I've tried named-xfer).
> I run bind-8.1.2
I would need to see the complete zone files for domain.com and
zone.domain.com, and the named.conf file from the master (192.168.0.1)
in order to provide advice.
-- Glynn Clements <glynn@sensei.co.uk> - To unsubscribe from this list: send the line "unsubscribe linux-net" in the body of a message to majordomo@vger.rutgers.edu