Tim wrote:
> Realising you don't really want two configurations to have to do, but
> if it's your intention that *some* things should use 127.0.0.1, and
> other things should not, then I think you're stuck having to *manage*
> that.
I'm on the trail of a possible solution. Further ideas welcome.
On 6 October 2014 22:29:56 GMT+01:00, CLOSE Dave
wrote:
>I wrote:
>
>> We have a number of internal machines which run a local nameserver.
>> It's primarily a relay for the wider net but does a few other things
>> as well. So DHCP is configured to specify 127.0.0.1 as the nameserver
>> address fo
Allegedly, on or about 06 October 2014, CLOSE Dave sent:
> The difficulty is that, during kickstart the DHCP configuration is
> wrong. I'd much rather not have to use a different configuration for
> kickstart than for normal operation. While I can do that for an
> initial installation, it is far tr
I wrote:
> We have a number of internal machines which run a local nameserver.
> It's primarily a relay for the wider net but does a few other things
> as well. So DHCP is configured to specify 127.0.0.1 as the nameserver
> address for these machines.
>
> Of course, that is also what kickstart is
Allegedly, on or about 03 October 2014, CLOSE Dave sent:
> We have a number of internal machines which run a local nameserver. It's
> primarily a relay for the wider net but does a few other things as well.
> So DHCP is configured to specify 127.0.0.1 as the nameserver address for
> these machin
We have a number of internal machines which run a local nameserver. It's
primarily a relay for the wider net but does a few other things as well.
So DHCP is configured to specify 127.0.0.1 as the nameserver address for
these machines.
Of course, that is also what kickstart is told when it conne
