wildcard not working after record deleted
Bryan.Bradsby at capnet.state.tx.us
Tue Jun 20 15:08:44 UTC 2017
At your service,
On Tue, 2017-06-20 at 10:51 -0400, Maria Iano wrote:
> The queries are being directed at an authoritative server, exactly as
> you describe above.
> We also pay for a secondary dns provider who pulls our zones from the
> same authoritative servers of ours which have this issue.
> The wildcard works when we send the query to one of our secondary
> provider's name servers.
> Here is the answer from one of the secondary provider's servers:
> ; <<>> DiG 9.10.2-P3 <<>> @<providers-server> <name> any
> ;; OPT PSEUDOSECTION:
> ; EDNS: version: 0, flags:; udp: 4096
> ;; QUESTION SECTION:
> ;<name> IN ANY
> ;; ANSWER SECTION:
> <name> 300 IN CNAME <data-in-wilcard-record>
BIND does not allow a CNAME at the apex of the zone, some other flavors
of DNS servers allow this.
Was the wildcard changed to a CNAME in the last edit?
More information about the bind-users