Bug 10435 - DNS wildcards not working on BIND or Internal DNS
Summary: DNS wildcards not working on BIND or Internal DNS
Status: RESOLVED DUPLICATE of bug 12952
Alias: None
Product: Samba 4.1 and newer
Classification: Unclassified
Component: DNS server (internal) (show other bugs)
Version: unspecified
Hardware: All All
: P5 normal (vote)
Target Milestone: ---
Assignee: Kai Blin
QA Contact: Samba QA Contact
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-02-10 16:35 UTC by Chris Alavoine
Modified: 2017-08-24 16:02 UTC (History)
5 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Chris Alavoine 2014-02-10 16:35:46 UTC 
Hi there,

I create a new domain under main search domain in Forward Lookup Zones and then add a wildcard entry and (same as parent folder) entry pointing to an internal address. For instance in the domain example.com I create new subdomain test.example.com with wildcard entry for *.test.example.com.

test.example.com resolves fine, but any wildcard refuses to work.

I have been requested to file this bug report as it was reproducible by Marc Muehlfeld.

Thanks,
Chris.
Comment 1 Bug Reporter 2015-08-11 15:28:33 UTC 
This is still an issue in 4.1.

Is this anywhere on the roadmap?
Comment 2 Hamza 2016-04-05 13:23:14 UTC 
I still have this issue in version 4.3.4.

If I add a wildcard record to the zone (e.g. *.example.com) wc.example.com can be resolved. But if I add a wildcard to the subdomain (e.g. *.test.example.com), wc.test.example.com can not be resolved.


Record entry: *	A192.168.1.123
----------------------------------

# nslookup wc.muc.pom
Name:   wc.muc.pom
Address: 192.168.1.123
----------------------------------

# nslookup wc.test.muc.pom
** server can't find wc.test.muc.pom: NXDOMAIN
----------------------------------

# nslookup *.test.muc.pom
Name:   *.test.muc.pom
Address: 192.168.1.123
Comment 3 Chris Alavoine 2016-04-05 13:25:54 UTC 
(In reply to Hamza from comment #2)
Hi Hamza,

Confirmed. 

I've tested each version for wildcard support since 10.02.2014 when I first filed the bug report. 

Chris.
Comment 4 Hamza 2016-04-05 13:52:34 UTC 
(In reply to Chris Alavoine from comment #3)
Hi Chris,

it seems that entries with '*' in sub-domains is not recognized as wildcard, but as an asterisk.

Unfortunately I can not use samba in a productive environment as long as this bug exists.
Comment 5 Chris Alavoine 2016-04-05 14:43:14 UTC 
(In reply to Hamza from comment #4)
Hi Hamza,

Yes, that is the bug.

As a workaround I've put a standard BIND server in front of my Samba DC's which resolves any wildcard sub-domains I have, anything else is then forwarded onto the DC's. Not pretty but it works.

Chris.
Comment 6 wizhippo 2016-07-28 14:33:52 UTC 
I too have this issue.  When adding a wildcard domain via windows DNS Manger or I get the record already exits.

When adding via samba-tool it adds it but not as a wild card but instead as an A entry for @.
Comment 7 Michal Dejmek 2016-09-17 18:36:36 UTC 
This problem has version 4.5.0. :(
Comment 8 Björn Jacke 2017-08-24 16:02:46 UTC 

*** This bug has been marked as a duplicate of bug 12952 ***