> Actually, these files are essentially ANDed together. It doesn't just
> stop once it has read your /etc/resolv.conf, it keeps going and adds
in
> servers from the other two files. The relevant code is here:
>
http://search.cpan.org/src/CREIN/Net-DNS-0.48/lib/Net/DNS/Resolver/UNIX.
pm
Also you
Austin Weidner wrote:
Hopefully someone else can learn from this because the docs are a little
deceiving, as you said it says in the docs that the order is checked like:
/etc/resolv.conf
$HOME/.resolv.conf
./.resolv.conf
However it was checking like this:
$HOME/.resolv.conf
/etc/resolv.conf
I've su
> Do you have any of the other files:
>
> >> /etc/resolv.conf
> >> $HOME/.resolv.conf
> >> ./.resolv.conf
>
> where . and $HOME are for the user SA runs as.
>
> Jeff C.
Jeff,
Thanks for the reply... I am happy to say: PROBLEM SOLVED! I was so happy to
see this:
debug: RBL: succe
On Thursday, February 17, 2005, 8:56:40 PM, Austin Weidner wrote:
>> According to the docs:
>>
>> On UNIX systems the defaults are read from the following files, in the
>> order indicated:
>>
>> /etc/resolv.conf
>> $HOME/.resolv.conf
>> ./.resolv.conf
>>
>> What OS is this server
> According to the docs:
>
> On UNIX systems the defaults are read from the following files, in the
> order indicated:
>
> /etc/resolv.conf
> $HOME/.resolv.conf
> ./.resolv.conf
>
> What OS is this server running?
>
> Try running this:
>
> perl -MNet::DNS -e '$r=Net::DNS::Resolv
On Thu, Feb 17, 2005 at 04:51:50PM -0500, Chris Santerre wrote:
> This is ALWAYS a good idea, and why I don't use RPMs.
Heh. I try to only use RPMs to solve this issue. ;) Installing things
manually leaves somewhat random files all over the place, RPMs know what files
are what.
The thing is t
>
>So I thought maybe Net::DNS looks at it when it is first
>installed. Tried
>to reinstall Net::DNS from source, still nothing. Wonder if I
>need to remove
>the RPM version before installing from source? I have:
This is ALWAYS a good idea, and why I don't use RPMs.
>perl-Net-DNS-0.31-3.1
I
That version of Net::DNS is too old. Upgrade that and see if it fixes
it.
Tom
Austin Weidner wrote:
According to the docs:
On UNIX systems the defaults are read from the following files, in the
order indicated:
/etc/resolv.conf
$HOME/.resolv.conf
./.resolv.conf
What
> According to the docs:
>
> On UNIX systems the defaults are read from the following files, in the
> order indicated:
>
> /etc/resolv.conf
> $HOME/.resolv.conf
> ./.resolv.conf
>
> What OS is this server running?
>
> Try running this:
>
> perl -MNet::DNS -e '$r=Net::DNS::Resolv
Austin Weidner wrote:
-
Does Net::DNS even look in resolv.conf? There seems to be some links to a
file called ".resolv.conf". I wonder if Net::DNS isn't even looking there?
According to the docs:
On UNIX systems the defaults are read from the following files, in the
order indicated:
/
> 1. there have been some reports that Net::DNS will only look at the very
> first nameserver listed in /etc/resolv.conf. Have you checked how long
> that takes to look up a (non-cached!) record?
I tried switching the order of the nameservers, no luck. Tried adding a new
nameserver (public names
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Austin Weidner writes:
> > 127.0.0.2 is the standard answer that Spamcop gives if the requested
> > address is in its list. If the address is not in its list, if returns
> > a NOT FOUND. So it looks like you are right in that the problem is not
>
> 127.0.0.2 is the standard answer that Spamcop gives if the requested
> address is in its list. If the address is not in its list, if returns
> a NOT FOUND. So it looks like you are right in that the problem is not
> access-related. Do you have a "dns_available" entry in your
> /etc/mail/spa
Austin Weidner wrote:
Try seeing if you can use nslookup to find a currently blacklisted
address. At this very moment, 64.12.184.133 is in the spamcop bl.
Try doing
nslookup 133.184.12.64.bl.spamcop.net
and see if that returns an address.
Kevin,
Thanks for the reply. That was a good idea:
--
> Try seeing if you can use nslookup to find a currently blacklisted
> address. At this very moment, 64.12.184.133 is in the spamcop bl.
> Try doing
>
> nslookup 133.184.12.64.bl.spamcop.net
>
> and see if that returns an address.
Kevin,
Thanks for the reply. That was a good idea:
> *cough*
>
> I'll repeat myself..
>
> " Either that or you are using comcast's nameservers, and they've decided
> to block access to RBLs by their users."
>
> Are you using comcast's nameservers? If so, it is possible that they have
> blocked their namserver from answering queries for common R
Try seeing if you can use nslookup to find a currently blacklisted
address. At this very moment, 64.12.184.133 is in the spamcop bl.
Try doing
nslookup 133.184.12.64.bl.spamcop.net
and see if that returns an address.
Austin Weidner wrote:
Hmm, sounds like your resolv.conf is pointing to a na
-
My /etc/resolv.conf file is pointing to my server providers nameservers.
These work find, because:
-
[EMAIL PROTECTED] tmp]# nslookup msn.com
Server: xxx.xxx.xxx.xxx <-- my isp namesever
Address:xxx.xxx.xxx.xxx #53
Non-authoritative answer:
Name:
At 02:58 PM 2/17/2005, Austin Weidner wrote:
Ignore the Comcast thing, that was a pure coincidence. My ISP is Comcast,
but that didn't have anything to do with the NS lookup that spamassassin
did. I think when it runs that test it does a random main domain or ISP
(I've seen sourceforge.net, linux.o
> Hmm, sounds like your resolv.conf is pointing to a nameserver that doesn't
> allow recursion, and only answers queries about comcast.net addresses.
>
> Either that or you are using comcast's nameservers, and they've decided to
> block access to RBLs by their users. I'm a comcast subscriber at ho
Looks to me like you can do queries to your own internal DNS server, but
cannot directly query an exterior DNS server. This would happen if you
are behind a firewall and only your internal DNS server is allowed to
make queries to other DNS servers outside the firewall.
Hope that helps,
Kevin
At 01:32 PM 2/17/2005, Austin Weidner wrote:
debug: is Net::DNS::Resolver available? yes
debug: Net::DNS version: 0.48
debug: trying (3) comcast.net...
debug: looking up NS for 'comcast.net'
debug: NS lookup of comcast.net succeeded => Dns available (set
dns_available to hardcode)
debug: is DNS ava
22 matches
Mail list logo
