[Pdns-users] Newbie Question

Tom Rossi trossi at msites.com
Wed Apr 11 18:58:59 UTC 2007


Tobias,

So you experienced the same thing?  A failure when a CNAME resolves to a
host on another authoritative nameserver?  Were you using nslookup for your
testing?

Thanks,
Tom

On 4/11/07, Tobias Orlamuende <t.orlamuende at webspace4you.ch> wrote:
>
>  Not that I am able to help, but:
>
> We had some quite similar behaviour some weeks ago while testing some
> things.
> We had our two productive NS (powerdns) and one NS for testing (also
> powerdns). While explicitly asking the testing one which had records for a
> special CNAME it returned the IP resolved by a wildcard on the productive
> one.
> I also found out that if you point a CNAME to a record belonging to
> another domain all resolves fine as long as the "other" domain is served by
> the same server. E.g.:
> test1.mytest.com => CNAME => something.anothertest.com
> If there is another authoritative server for anothertest.com than the one
> asked for mytest.com things fail. If it is on the same and authoritative,
> everything works.
> Since we found another possibility to solve "our" problem we just
> asked ourselves if this behaviour is either a bug or a feature :-)
> Maybe somebody could explain what the idea behind that behaviour is or
> confirm it as a bug.
>
> Cheers
>
> Tobias
>  ------------------------------
>  *From:* pdns-users-bounces at mailman.powerdns.com [mailto:
> pdns-users-bounces at mailman.powerdns.com]
> *Sent:* Dienstag, 10. April 2007 22:43
> *To:* Derrik Pates
> *Cc:* pdns-users at mailman.powerdns.com
> *Subject:* Re: [Pdns-users] Newbie Question
>
>  Yes, when it starts in the monitor mode it connects to the mysql server.
> Also, I can resolve any of my A records, just not the CNAME record which is
> formatted as I provided earlier.
>
> On 4/10/07, Derrik Pates <demon at devrandom.net> wrote:
> >
> > Tom Rossi wrote:
> > > The second thing I tried was to remove the recursor key and use the
> > pdns
> > > as strictly authoritative.  The database remains the same -- a CNAME
> > for
> > > www.test.com <http://www.test.com>.  Again, I used nslookup to try and
> > > resolve, but now I get a "** server can't find www.test.com
> > > < http://www.test.com>: SERVFAIL"  Shouldn't it have responded with
> > the
> > > value of the CNAME even if it couldn't recurse to resolve it?
> >
> > That sounds like the database itself is misconfigured. Is there anything
> >
> > in the system logs from PowerDNS stating that it's successfully
> > connected to the database? What backend are you using?
> >
> > --
> > Derrik Pates
> > demon at devrandom.net
> >
>
>
> _______________________________________________
> Pdns-users mailing list
> Pdns-users at mailman.powerdns.com
> http://mailman.powerdns.com/mailman/listinfo/pdns-users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.powerdns.com/pipermail/pdns-users/attachments/20070411/d9928c73/attachment-0001.html>


More information about the Pdns-users mailing list