While looking for a way to get a dump of a zone, I ran: samba-tool dns query kaylee firefly.michael.mol.name '*' ALL Here's the result: $ samba-tool dns query kaylee firefly.michael.mol.name '*' ALL Password for [administrator@FIREFLY.MICHAEL.MOL.NAME]: ERROR(runtime): uncaught exception - (8, 'WERR_NOMEM') File "/usr/lib64/python2.7/site-packages/samba/netcmd/__init__.py", line 175, in _run return self.run(*args, **kwargs) File "/usr/lib64/python2.7/site-packages/samba/netcmd/dns.py", line 974, in run None, record_type, select_flags, None, None) I have 10GB of RAM on that box, 7GB that's free or disk cache.
This is a problem with wild-card search. If you want to search the entire zone, please use @ instead of '*'.
(In reply to comment #1) > This is a problem with wild-card search. > > If you want to search the entire zone, please use @ instead of '*'. We should return WERR_DNS_ERROR_NAME_DOES_NOT_EXIST (as windows) instead of WERR_NOMEM...
Upstream already has a patch to netcmd/dns.py to dump correct message in case user specifies * in the name. 8e7f8a2 netcmd/dns: Catch wildcard patterns when querying for name
(In reply to comment #3) > Upstream already has a patch to netcmd/dns.py to dump correct message in case > user specifies * in the name. > > 8e7f8a2 netcmd/dns: Catch wildcard patterns when querying for name I think we should also fix the server.
Ping!
> Upstream already has a patch to netcmd/dns.py to dump correct message in case > user specifies * in the name. > > 8e7f8a2 netcmd/dns: Catch wildcard patterns when querying for name That patch was effectively reversed with 29b3a2b0d1e5abc1ca9f112f680251e34fa6e3af as part of the fix for bug #12952 ("Samba DNS server does not honour wildcards"). The fix for bug #12952 entails the server fix mentioned in comment 4. Now in a testenv I see: $ bin/samba-tool dns query -U$USERNAME%$PASSWORD $SERVER addom.samba.example.com '*' ALL use "@" to dump entire domain, looking up * ERROR: Record or zone does not exist