Fair enough, I can handle the DNS myself. Perhaps the ignore routine can
locate the closing "}" brackets so it can deal with the multi line directives?
While I'm at it, are there any useful DHCPcd options worth putting in? I have
a rh 5.1 box on a cable modem that works great (including the firewall config)
except that after the cable goes down (seems to happen often enough) and the
dhcpcd deamon gives up, the cable side nic stays down until I do a manual
"ifup eth0". I need an automagic way of getting the line back up when
available. Then sending a dynamic DNS update to my stable server just in case
the IP has changed.
Right now I have the client do the ifup and then Lynx to a DNS update page.
Jacques Gelinas wrote:
> On Fri, 20 Nov 1998, DS wrote:
>
> I have added minimal bind-8 support so people could move to bind-8 using
> their current configuration. More options have to be supported. Also
> parsing unknown option needs some work. There are various case involved.
> The same apply the the dhcpd.conf file which is sharing mostly the same
> layout (no suprise since it comes from the same place).
>
> These options have to be added anyway.
>
> Other configuration file are much easier to deal when meeting unknown
> options. Most have a single line format (one option per line). So skipping
> those and rewriting them is easier. The syntax of named.conf is more
> sophisticated.
---
You are currently subscribed to linuxconf as: [[email protected]]
To unsubscribe, forward this message to [EMAIL PROTECTED]