[Pdns-users] CNAME Problems

[Ole Hejlskov]

Hi!

I'm having some problems with wildcard CNAMEs in my PowerDNS, which I
recently rolled out on my primary DNS server.

Some people are complaining about their mail.domain.tld A record points
at the same as domain.tld, if they have a wildcard CNAME record.
I have an example:
---
[workspand] ~$ host mail.dit-webdomain.dk 62.242.36.51
Using domain server:
Name: 62.242.36.51
Address: 62.242.36.51#53
Aliases: 

mail.dit-webdomain.dk has address 62.242.36.51
Using domain server:
Name: 62.242.36.51
Address: 62.242.36.51#53
Aliases: 

mail.dit-webdomain.dk is an alias for dit-webdomain.dk.
Using domain server:
Name: 62.242.36.51
Address: 62.242.36.51#53
Aliases: 

mail.dit-webdomain.dk is an alias for dit-webdomain.dk.
dit-webdomain.dk mail is handled by 20 mx20.domainteam.dk.
dit-webdomain.dk mail is handled by 30 mx30.domainteam.dk.
dit-webdomain.dk mail is handled by 10 mail.dit-webdomain.dk.
---

Two things I don't understand about this is:
mail.dit-webdomain.dk has address 62.242.36.51
And later on it says: 
mail.dit-webdomain.dk is an alias for dit-webdomain.dk

Now I'll probably get a response saying that I can't use the output for
anything, and that I should use dig, and here is the output:

---
[workspand] ~$ dig -t any @62.242.36.51 mail.dit-webdomain.dk

; <<>> DiG 9.3.0 <<>> -t any @62.242.36.51 mail.dit-webdomain.dk
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 62384
;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;mail.dit-webdomain.dk.         IN      ANY

;; ANSWER SECTION:
mail.dit-webdomain.dk.  7200    IN      A       62.242.36.51

;; Query time: 7 msec
;; SERVER: 62.242.36.51#53(62.242.36.51)
;; WHEN: Fri Mar 11 11:44:34 2005
;; MSG SIZE  rcvd: 55
---

Now I get the right results, but my caching DNS server 82.192.176.2
sometimes returns the wrong IP for mail.dit-webdomain.dk. Hmpf!

I've had a few domains with this problems, and if I restart my caching
server it returns the right answer. 

The bad thing about this is the fact that sometimes I can't reproduce
the error, but the customers complain about it..

Is there a solution to this problem?

Some system info:

OS: FreeBSD 5.3-RELEASE-p5
PowerDNS: 2.9.17, build from FreeBSD ports with MySQL support

I use a custom database, which I can supply if requested.

Best regards
Ole Hejlskov