Folks,
I am having problems with a certain domain with powerdns recursor.
If I dig for visolve.com, it comes up with SERVFAIL.
If I dig for visolve.com ns, it responds correctly.
If I replace powerdns recursor with dnsmasq, slaving off our upstream
(probably running bind9) visolve.co
On Wed, Jan 31, 2007 at 11:08:13AM +0200, Andy Rabagliati wrote:
> I am having problems with a certain domain with powerdns recursor.
Which version?
--
http://www.PowerDNS.com Open source, database driven DNS Software
http://netherlabs.nl Open and Closed source services
On Wed, 31 Jan 2007, bert hubert wrote:
> On Wed, Jan 31, 2007 at 11:08:13AM +0200, Andy Rabagliati wrote:
> > I am having problems with a certain domain with powerdns recursor.
>
> Which version?
>
Apologies.
2.9.19-3build1, on Ubuntu dapper.
Cheers, Andy!
On Wed, Jan 31, 2007 at 12:03:04PM +0200, Andy Rabagliati wrote:
> > On Wed, Jan 31, 2007 at 11:08:13AM +0200, Andy Rabagliati wrote:
> > > I am having problems with a certain domain with powerdns recursor.
> > Which version?
> Apologies.
> 2.9.19-3build1, on Ubuntu dapper.
Many, many, many issu
On Wed, 31 Jan 2007, Andy Rabagliati wrote:
> Folks,
>
> I am having problems with a certain domain with powerdns recursor.
>
> If I dig for visolve.com, it comes up with SERVFAIL.
[...]
> How do I debug this problem ?
I am now running from pdns-recursor_3.1.4-1_i386.deb, and I see the
On Wed, Jan 31, 2007 at 12:59:17PM +0200, Andy Rabagliati wrote:
> > How do I debug this problem ?
>
> I am now running from pdns-recursor_3.1.4-1_i386.deb, and I see the same
> problem.
You might not be running 3.1.4 - please double check. "my" 3.1.4 doesn't
exhibit the problem.
If that does
On Wed, 31 Jan 2007, bert hubert wrote:
> If that doesn't help, please run the recursor on the foreground, like this:
>
> pdns_recursor --daemon=no --trace
>
> And show us the output while querying for the domain that has the problem.
> Please include all logging from the start, and all 'dig' ou
On Wed, Jan 31, 2007 at 02:09:24PM +0200, Andy Rabagliati wrote:
> > And show us the output while querying for the domain that has the problem.
> > Please include all logging from the start, and all 'dig' output.
>
> I verified I have no old copies of pdns_recursor lying around.
Thanks.
> The m
On Wed, 31 Jan 2007, bert hubert wrote:
> On Wed, Jan 31, 2007 at 02:09:24PM +0200, Andy Rabagliati wrote:
>
> > The machine musselcracker is our firewall. My desktop (quail) routes
> > through it.
> > From my desktop (also ubuntu dapper), I see this :-
>
> To recap:
>
> dig on desktop: can t
On Wed, Jan 31, 2007 at 04:40:14PM +0200, Andy Rabagliati wrote:
> same story. iptables rules are generally more liberal from the firewall
> itself than for traffic passing through - I use firehol as a ruleset
> generator.
>
> I was thinking it might be a UDP vs TCP issue ??
I don't think so. Do
On Wed, 31 Jan 2007, bert hubert wrote:
> Your firewall rules might not be set up to deal with that.
>
I used firehol to generate my rulesets.
http://comments.gmane.org/gmane.comp.security.firewalls.firehol.user/535
visolve.com (76.*) is erroneously listed as an unrouteable IP by firehol.
Sor
11 matches
Mail list logo