Public bug reported:

Original from Habbie:
https://github.com/PowerDNS/pdns/issues/389

Thank you for looking into the wildcard feature and updating it in 3.0!

Now NS records are resolved before * records, but apparently not in an
100% correct way - as it seems, the resolution is still not fully
conform RFC or as in bind.

If I have the following records on my PDNS server:

*.tld A 168.0.0.1
dom.tld NS ns.a.com
dom.tld NS ns.b.com

...and on ns.a. and b.com we have:
dom.tld A 195.0.0.0.1
sub.dom.tld CNAME dom.tld

dom.tld is resolved correctly, but sub.dom.tld (no matter if defined as
CNAME or totally undefined) is resolved to 168.0.0.1 instead of
195.0.0.0.1

If an NS record is present for a sub.dom.tld, no further (wildcard)
answers should be given out by PDNS - rather a servfail should result.

Thank you for PowerDNS and or your great work!

** Affects: pdns (Ubuntu)
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1217940

Title:
  widlcard entries not handeled correctly in 3.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pdns/+bug/1217940/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to