> I'm sending this message only to you because the linux-net may not like the
> junk with that problem and furthermore - it seems none else is interested
> in that speciffic (for me) problem exept us.
> I think that sometimes its not so important to give the right and exact
> advice but to try to think over the problem and the best way is to share
> your idea.
>
> > 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?
>
> ;zone.domain.com
OK.
> ;domain.com
You also need e.g.:
zone IN NS ns.domain.com.
IN NS ns2.domain.com.
IN NS ns.zone.domain.com.
ns.zone IN A 192.168.1.1
otherwise the rest of the world won't know that the subdomain has been
delegated.
> /etc/named.conf on 192.168.1.1 (ns.zone.domain.com)
This configures named as a forwarding-only server, so you shouldn't be
trying to delegate anything to it.
If you want it to be authoritative for zone.domain.com, you will need
to add e.g.
zone "zone.domain.com" {
type slave;
file "named.zone";
masters { 192.168.0.1; };
};
> options {
> forward-only;
> forwaredrs {
Also, you've mis-spelt `forwarders'.
-- 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