Re: Net::DNS install assistance

2005-09-11 Thread Chris
On Saturday 10 September 2005 08:50 pm, jdow wrote:
> From: "Chris" <[EMAIL PROTECTED]>
>

>
> Does resolv.conf STILL show local host?
>
> And does your local host also support a caching server for the whole
> internet? That's the usual setup you need.
> {^_^}

Thanks to everyone for replying to me on this.  The answer was provided to me 
in a reply from Olaf M. Kolkman, the maintainer for NET::DNS:

All these tests are skipped for good reasons, you do not have to
worry about them.

The IP address is the IP address of your box. Its a private IP
address, an indication that you may be using a NAT. Being behind a
NAT is a common case for failure.


If I understand NAT correctly my DSL modem is also acting as a router thus 
providing the Network Address Translation.

-- 
Chris
Registered Linux User 283774 http://counter.li.org
14:44:42 up 1 day, 2:57, 1 user, load average: 0.35, 0.25, 0.19
Mandriva Linux 10.1 Official, kernel 2.6.8.1-12mdk



Re: Net::DNS install assistance

2005-09-10 Thread jdow

From: "Chris" <[EMAIL PROTECTED]>


On Saturday 10 September 2005 11:29 am, jdow wrote:


> t/05-rr-txtok
> t/05-rr-unknownok
> t/05-rrok
> t/06-updateok
> t/07-misc..ok
> t/08-onlineok
> t/09-tkey..ok
> t/10-recurse...skipped
>all skipped: Cannot run these tests from this IP:192.168.1.2
>
> I'm particulary concerned by the last test - Cannot run tests from
> 192.168.1.2.  I assume, and I'm not sure, that its reading nameserver
> info from my resolv.conf:
>
> nameserver 192.168.1.2
> # nameserver 127.0.0.1
> # nameserver 207.217.120.83
> # nameserver 207.217.126.81
> nameserver 207.69.188.185
> nameserver 207.69.188.186
> nameserver 207.69.188.187
>
> Should there be a different ip, ie..127.0.0.1 instead of 192.168.1.2?

Likely. That is what I have. I run the name server on the same machine
as SpamAssassin so it's 127.0.0.1 rather than the external address.
(And yes, I do know I am a bad girl for mixing firewall and servers on
the same machine.)

{^_^}


Thats what I thought.  I changed my resolv.conf to show nameserver 
127.0.0.1

did a network restart, but the Net::DNS tests are determined to use
192.168.1.2, I wonder if a system restart is needed?


Does resolv.conf STILL show local host?

And does your local host also support a caching server for the whole
internet? That's the usual setup you need.
{^_^} 





Re: Net::DNS install assistance

2005-09-10 Thread Chris
On Saturday 10 September 2005 05:33 pm, Gary W. Smith wrote:
> If it's just one of the test that's failing then you might just want to
> try installing it anyways.  It could be that the particular test is
> buggy.
>
> Gary
>
Its installed and appears, AFAICT, as it did before the upgrade. But, who am I 
to tell for sure. SA is working the same as before, all the RBL tests are 
still working so maybe its something I didn't even need.

-- 
Chris
Registered Linux User 283774 http://counter.li.org
17:42:30 up 5:55, 1 user, load average: 1.04, 1.14, 0.90
Mandriva Linux 10.1 Official, kernel 2.6.8.1-12mdk


RE: Net::DNS install assistance

2005-09-10 Thread Gary W. Smith
If it's just one of the test that's failing then you might just want to
try installing it anyways.  It could be that the particular test is
buggy.

Gary

-Original Message-
From: Chris [mailto:[EMAIL PROTECTED] 
Sent: Saturday, September 10, 2005 2:32 PM
To: users@spamassassin.apache.org
Subject: Re: Net::DNS install assistance

On Saturday 10 September 2005 04:17 pm, [EMAIL PROTECTED] wrote:
> Hi,
>
> just guessing maybe this test requires the nameserver to have a
public
> address
>
> Wolfgang Hamann
>
Admittedly I do not know much about this, I guess that's very possible.
I've 
read the man page(s), gone to the Net::DNS home page and haven't really
seen 
anything that answers this.

-- 
Chris
Registered Linux User 283774 http://counter.li.org
16:23:00 up 4:35, 2 users, load average: 0.65, 0.57, 0.47
Mandriva Linux 10.1 Official, kernel 2.6.8.1-12mdk


Re: Net::DNS install assistance

2005-09-10 Thread Chris
On Saturday 10 September 2005 04:17 pm, [EMAIL PROTECTED] wrote:
> Hi,
>
> just guessing maybe this test requires the nameserver to have a public
> address
>
> Wolfgang Hamann
>
Admittedly I do not know much about this, I guess that's very possible.  I've 
read the man page(s), gone to the Net::DNS home page and haven't really seen 
anything that answers this.

-- 
Chris
Registered Linux User 283774 http://counter.li.org
16:23:00 up 4:35, 2 users, load average: 0.65, 0.57, 0.47
Mandriva Linux 10.1 Official, kernel 2.6.8.1-12mdk


Re: Net::DNS install assistance

2005-09-10 Thread hamann . w


Hi,

just guessing maybe this test requires the nameserver to have a public 
address

Wolfgang Hamann

>> 
>> On Saturday 10 September 2005 01:34 pm, Gary W. Smith wrote:
>> > It is seeing the correct name server.  You might want to blow away the
>> > cached files (make clean) or re-download the module (CPAN after blowing
>> > away the original source files).  It's possible that the make process
>> > created a cache file containing the 192.x.x.x IP and it keeps using that
>> > one instead of getting the proper information for resolv.conf.
>> >
>> > HTH,
>> >
>> > Gary
>> Uninstalled and reinstalled (via CPAN) Net::DNS, seems the only test thats 
>> giving the 192.168.1.2 error is:
>> 
>> t/10-recurse...skipped
>> all skipped: Cannot run these tests from this IP:192.168.1.2
>> 
>> all other tests show 'ok'
>> 
>> -- 
>> Chris
>> Registered Linux User 283774 http://counter.li.org
>> 15:30:54 up 3:43, 1 user, load average: 0.82, 0.68, 0.49
>> Mandriva Linux 10.1 Official, kernel 2.6.8.1-12mdk
>> 




Re: Net::DNS install assistance

2005-09-10 Thread Chris
On Saturday 10 September 2005 01:34 pm, Gary W. Smith wrote:
> It is seeing the correct name server.  You might want to blow away the
> cached files (make clean) or re-download the module (CPAN after blowing
> away the original source files).  It's possible that the make process
> created a cache file containing the 192.x.x.x IP and it keeps using that
> one instead of getting the proper information for resolv.conf.
>
> HTH,
>
> Gary
Uninstalled and reinstalled (via CPAN) Net::DNS, seems the only test thats 
giving the 192.168.1.2 error is:

t/10-recurse...skipped
all skipped: Cannot run these tests from this IP:192.168.1.2

all other tests show 'ok'

-- 
Chris
Registered Linux User 283774 http://counter.li.org
15:30:54 up 3:43, 1 user, load average: 0.82, 0.68, 0.49
Mandriva Linux 10.1 Official, kernel 2.6.8.1-12mdk


RE: Net::DNS install assistance

2005-09-10 Thread Gary W. Smith
It is seeing the correct name server.  You might want to blow away the
cached files (make clean) or re-download the module (CPAN after blowing
away the original source files).  It's possible that the make process
created a cache file containing the 192.x.x.x IP and it keeps using that
one instead of getting the proper information for resolv.conf.

HTH,

Gary 

-Original Message-
From: Chris [mailto:[EMAIL PROTECTED] 
Sent: Saturday, September 10, 2005 10:16 AM
To: Gary W. Smith; users@spamassassin.apache.org
Subject: Re: Net::DNS install assistance

I'm running firestarter, I have it setup to allow connections from 
192.168.1.2, 127.0.0.1, 192.168.1.1, should I also add "localhost" or is
that 
the correct term?  Nslookup shows:

[EMAIL PROTECTED] chris]$ nslookup earthlink.net
Server: 127.0.0.1
Address:127.0.0.1#53



Re: Net::DNS install assistance

2005-09-10 Thread Chris
On Saturday 10 September 2005 11:49 am, you wrote:
> You mentioned firewall.  Is it possible that you are not opening up the
> right connections to localhost or to the 192.x.x.x machine?
>
> We tend to mix firewall and server software on the same machine from
> many small small clients.  I'm assuming that you are using iptables.
> Did you open up lo for all traffic to and from itself?  Port 53 tcp and
> udp to/through the firewall?
>
> You can test if the resolv.conf is pointing to the proper location after
> the change.  Just run a nslookup and see which server it wants to pickup
>
I'm running firestarter, I have it setup to allow connections from 
192.168.1.2, 127.0.0.1, 192.168.1.1, should I also add "localhost" or is that 
the correct term?  Nslookup shows:

[EMAIL PROTECTED] chris]$ nslookup earthlink.net
Server: 127.0.0.1
Address:127.0.0.1#53

-- 
Chris
Registered Linux User 283774 http://counter.li.org
12:10:39 up 23 min, 1 user, load average: 1.00, 0.82, 0.63
Mandriva Linux 10.1 Official, kernel 2.6.8.1-12mdk



RE: Net::DNS install assistance

2005-09-10 Thread Gary W. Smith
You mentioned firewall.  Is it possible that you are not opening up the
right connections to localhost or to the 192.x.x.x machine?  

We tend to mix firewall and server software on the same machine from
many small small clients.  I'm assuming that you are using iptables.
Did you open up lo for all traffic to and from itself?  Port 53 tcp and
udp to/through the firewall?

You can test if the resolv.conf is pointing to the proper location after
the change.  Just run a nslookup and see which server it wants to pickup

-Original Message-
From: Chris [mailto:[EMAIL PROTECTED] 
Sent: Saturday, September 10, 2005 9:43 AM
To: users@spamassassin.apache.org
Subject: Re: Net::DNS install assistance

> > Should there be a different ip, ie..127.0.0.1 instead of
192.168.1.2?
>
> Likely. That is what I have. I run the name server on the same machine
> as SpamAssassin so it's 127.0.0.1 rather than the external address.
> (And yes, I do know I am a bad girl for mixing firewall and servers on
> the same machine.)
>
> {^_^}

Thats what I thought.  I changed my resolv.conf to show nameserver
127.0.0.1 
did a network restart, but the Net::DNS tests are determined to use 
192.168.1.2, I wonder if a system restart is needed?

-- 
Chris
Registered Linux User 283774 http://counter.li.org
11:41:04 up 17:02, 1 user, load average: 1.04, 1.18, 1.04
Mandriva Linux 10.1 Official, kernel 2.6.8.1-12mdk


Re: Net::DNS install assistance

2005-09-10 Thread Chris
On Saturday 10 September 2005 11:29 am, jdow wrote:

> > t/05-rr-txtok
> > t/05-rr-unknownok
> > t/05-rrok
> > t/06-updateok
> > t/07-misc..ok
> > t/08-onlineok
> > t/09-tkey..ok
> > t/10-recurse...skipped
> >all skipped: Cannot run these tests from this IP:192.168.1.2
> >
> > I'm particulary concerned by the last test - Cannot run tests from
> > 192.168.1.2.  I assume, and I'm not sure, that its reading nameserver
> > info from my resolv.conf:
> >
> > nameserver 192.168.1.2
> > # nameserver 127.0.0.1
> > # nameserver 207.217.120.83
> > # nameserver 207.217.126.81
> > nameserver 207.69.188.185
> > nameserver 207.69.188.186
> > nameserver 207.69.188.187
> >
> > Should there be a different ip, ie..127.0.0.1 instead of 192.168.1.2?
>
> Likely. That is what I have. I run the name server on the same machine
> as SpamAssassin so it's 127.0.0.1 rather than the external address.
> (And yes, I do know I am a bad girl for mixing firewall and servers on
> the same machine.)
>
> {^_^}

Thats what I thought.  I changed my resolv.conf to show nameserver 127.0.0.1 
did a network restart, but the Net::DNS tests are determined to use 
192.168.1.2, I wonder if a system restart is needed?

-- 
Chris
Registered Linux User 283774 http://counter.li.org
11:41:04 up 17:02, 1 user, load average: 1.04, 1.18, 1.04
Mandriva Linux 10.1 Official, kernel 2.6.8.1-12mdk


Re: Net::DNS install assistance

2005-09-10 Thread jdow

From: "Chris" <[EMAIL PROTECTED]>


I was in the process of upgrading my Net::DNS module from .48 to .53 and I
noticed the following during tests:

t/00-load..ok
t/00-pod...ok
t/00-version...ok
t/01-resolver-env..ok
t/01-resolver-file.ok
   7/8 skipped: Could not read configuration file
t/01-resolver-opt..ok
t/01-resolver..ok
t/02-headerok
t/03-question..ok
t/04-packet-unique-pushok
t/04-packetok
t/05-rr-optok
t/05-rr-sshfp..skipped
   all skipped: Digest::BubbleBabble not installed.
t/05-rr-txtok
t/05-rr-unknownok
t/05-rrok
t/06-updateok
t/07-misc..ok
t/08-onlineok
t/09-tkey..ok
t/10-recurse...skipped
   all skipped: Cannot run these tests from this IP:192.168.1.2

I'm particulary concerned by the last test - Cannot run tests from
192.168.1.2.  I assume, and I'm not sure, that its reading nameserver info
from my resolv.conf:

nameserver 192.168.1.2
# nameserver 127.0.0.1
# nameserver 207.217.120.83
# nameserver 207.217.126.81
nameserver 207.69.188.185
nameserver 207.69.188.186
nameserver 207.69.188.187

Should there be a different ip, ie..127.0.0.1 instead of 192.168.1.2?


Likely. That is what I have. I run the name server on the same machine
as SpamAssassin so it's 127.0.0.1 rather than the external address.
(And yes, I do know I am a bad girl for mixing firewall and servers on
the same machine.)

{^_^} 





Net::DNS install assistance

2005-09-10 Thread Chris
I was in the process of upgrading my Net::DNS module from .48 to .53 and I 
noticed the following during tests:

t/00-load..ok
t/00-pod...ok
t/00-version...ok
t/01-resolver-env..ok
t/01-resolver-file.ok
7/8 skipped: Could not read configuration file
t/01-resolver-opt..ok
t/01-resolver..ok
t/02-headerok
t/03-question..ok
t/04-packet-unique-pushok
t/04-packetok
t/05-rr-optok
t/05-rr-sshfp..skipped
all skipped: Digest::BubbleBabble not installed.
t/05-rr-txtok
t/05-rr-unknownok
t/05-rrok
t/06-updateok
t/07-misc..ok
t/08-onlineok
t/09-tkey..ok
t/10-recurse...skipped
all skipped: Cannot run these tests from this IP:192.168.1.2

I'm particulary concerned by the last test - Cannot run tests from 
192.168.1.2.  I assume, and I'm not sure, that its reading nameserver info 
from my resolv.conf:

nameserver 192.168.1.2
# nameserver 127.0.0.1
# nameserver 207.217.120.83
# nameserver 207.217.126.81
nameserver 207.69.188.185
nameserver 207.69.188.186
nameserver 207.69.188.187

Should there be a different ip, ie..127.0.0.1 instead of 192.168.1.2?

-- 
Chris
Registered Linux User 283774 http://counter.li.org
11:17:05 up 16:38, 1 user, load average: 0.30, 0.68, 0.68
Mandriva Linux 10.1 Official, kernel 2.6.8.1-12mdk