Re: Adding openresolv to base

[Roy Marples <roy%marples.name@localhost>]

Jeremy C. Reed wrote:
> > this, is BSD licensed and works fine in / without /usr mounted. It can also
> > write support files for named(8) and dnsmasq(8)(pkgsrc) to use.
>
> What does "write support files for named(8)" mean? Example?

Attached are the two files it creates.
Global forwarders and per zone forwarders.
They should be included in the named configuration, also attached.

Similar files can be created for dnsmasq.

> > Attached is a patch to dhclient-script which adds resolvconf support to
> > demonstrate how easy it is to integrate.
>
> Anyone working on pppd part?

My understanding is that there are no default ppp scripts and it's up to 
the user to write them.

Obviously the presence of resolvconf (or similar) makes handling 
resolv.conf a lot easier.

Thanks

Roy

# Generated by resolvconf
forward first;
forwarders {
        10.44.1.1;
};

# Generated by resolvconf
zone "development.ltl" {
        type forward;
        forward first;
        forwarders {
                10.44.1.1;
        };
};

# $NetBSD: named.conf,v 1.4 2006/03/23 13:50:44 itojun Exp $

# boot file for secondary name server
# Note that there should be one primary entry for each SOA record.

options {
        directory "/etc/namedb";
        listen-on {
                127.0.0.1;
        };
        allow-recursion { localhost; localnets; };
        include "resolvconf-options.conf";
};
include "resolvconf-zones.conf";

zone "." {
        type hint;
        file "root.cache";
};

zone "localhost" {
        type master;
        file "localhost";
};

zone "127.IN-ADDR.ARPA" {
        type master;
        file "127";
};

zone "1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa" 
{
        type master;
        file "loopback.v6";
};

# example secondary server config:
#
# zone "Berkeley.EDU" {
#       type slave;
#       file "berkeley.edu.cache";
#       masters {
#               128.32.130.11;
#               128.32.133.1;
#       };
# };

# zone "32.128.IN-ADDR.ARPA" {
#       type slave;
#       file "128.32.cache";
#       masters {
#               128.32.130.11;
#               128.32.133.1;
#       };
# };

# example primary server config:
# 
# zone "Berkeley.EDU" {
#       type master;
#       file "berkeley.edu";
# };

# zone "32.128.IN-ADDR.ARPA" {
#       type master;
#       file "128.32";
# };