Alan, I'm so sorry! You are absolutely correct! I thought I tested that scenario last night, but I just tested again and it works. So with DNS records like the following:
*.example.com CNAME host.anotherdomain.com example.com A 192.168.0.1 I am able to resolve "anything.example.com" as well as "example.com". This will work fine BUT a CNAME would be ideal for our setup. We have hundreds of domains that all point to the same ip address. If I choose this configuration, I will need to update those hundreds of A records. Its all in a database now, so at least that won't be too difficult! Thanks! Tom On Thu, Jun 26, 2008 at 12:15 PM, Alan Hodgson <[EMAIL PROTECTED]> wrote: > On Thursday 26 June 2008, "Tom Rossi" <[EMAIL PROTECTED]> wrote: >> Alan, >> >> Sorry, I should have included scenario 4 which also does not work: >> >> SCENARIO 4 >> >> *.example.com CNAME host.anotherdomain.com >> example.com A 192.168.0.1 >> >> This will resolve "anything.example.com" but will NOT resolve >> "example.com" > > > That's odd. I know 2.9.21 works fine with that exact setup here, using the > PostgreSQL backend - just tested it. > > -- > Alan > _______________________________________________ > Pdns-users mailing list > Pdns-users@mailman.powerdns.com > http://mailman.powerdns.com/mailman/listinfo/pdns-users > _______________________________________________ Pdns-users mailing list Pdns-users@mailman.powerdns.com http://mailman.powerdns.com/mailman/listinfo/pdns-users
