On Wed, 19 Jan 2005 00:54, Lowell Gilbert wrote:
Ian Moore [EMAIL PROTECTED] writes:
I've just realised I'm not running a name server at all on my 5.3 system.
I have 4.9 installed on this computer too I'd set up the caching server
on it, I guess I forgot that step when I installed 5.3.
Ian Moore [EMAIL PROTECTED] writes:
On Wed, 19 Jan 2005 00:54, Lowell Gilbert wrote:
Ian Moore [EMAIL PROTECTED] writes:
I've just realised I'm not running a name server at all on my 5.3 system.
I have 4.9 installed on this computer too I'd set up the caching server
on it, I guess I
On Sat, 22 Jan 2005 02:32, Lowell Gilbert wrote:
Ian Moore [EMAIL PROTECTED] writes:
On Wed, 19 Jan 2005 00:54, Lowell Gilbert wrote:
Ian Moore [EMAIL PROTECTED] writes:
I've just realised I'm not running a name server at all on my 5.3
system. I have 4.9 installed on this computer
Ian Moore [EMAIL PROTECTED] writes:
I've just realised I'm not running a name server at all on my 5.3 system. I
have 4.9 installed on this computer too I'd set up the caching server on
it, I guess I forgot that step when I installed 5.3.
I'll set it up see that makes any difference.
Make
On Tue, 18 Jan 2005 12:50, Christian Hiris wrote:
On Tuesday 18 January 2005 01:09, John wrote:
On Mon, Jan 17, 2005 at 12:49:00PM -0600, John wrote:
On Mon, Jan 17, 2005 at 12:22:48PM -0600, John wrote:
On Tue, Jan 11, 2005 at 11:23:28PM +0900, Rob wrote:
Ian Moore wrote:
Hi,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday 18 January 2005 07:19, Ian Moore wrote:
Now I'm not sure what the best way to get around this would be. I run a
caching name server on the machine, so I guess I can tweak it to force
localhost.foo.com resolve to 127.0.0.1
I'm running
On Tue, 18 Jan 2005 17:13, Christian Hiris wrote:
On Tuesday 18 January 2005 07:19, Ian Moore wrote:
Now I'm not sure what the best way to get around this would be. I run a
caching name server on the machine, so I guess I can tweak it to force
localhost.foo.com resolve to 127.0.0.1
I'm