Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

my bind config

carrie     IN A
*.carrie   IN A
*.test.carrie IN A


nslookup  carrie 

nslookup a.test.carrie

but when I execute nslookup test.carrie

*** Can't find test.carrie: No answer
share|improve this question
Is there anything useful in the nameserver logs? – Flup Jun 26 '13 at 8:22
up vote 10 down vote accepted

The wildcard is working fine, which is why a.test.carrie resolves. Your issue is that test.carrie doesn't resolve.

The reason is simply that you haven't got a record for test.carrie.

*.test.carrie matches immediate subdomains of test.carrie, but matches neither test.carrie itself, nor any subdomains of subdomains of test.carrie.

Add another record without the wildcard.

share|improve this answer
why test.carrie dosen`t match wildchard *.carrie – leo Jun 26 '13 at 8:30
@leo I'm pretty sure it's because *.test.carrie partially defines test.carrie. Does test2.carrie resolve? If so, try adding *.test2.carrie and see if it breaks. Remember to allow time for your DNS cache to expire for accurate testing. – Dan Jun 26 '13 at 8:33
nslookup test2.carrie Address: after add *.test2.carrie IN A execute nslookup test2.carrie *** Can't find test2.carrie: No answer – leo Jun 26 '13 at 8:37
@leo As I thought, there's your answer. Once you add a wildcarded subdomain, BIND will no longer match that subdomain with the wildcard. This is almost certainly expected behaviour – Dan Jun 26 '13 at 8:42
@Dan Your wording there in the comment is a little off but you're correct. Wildcards match beneath the scope of a dot. – Andrew B Jun 26 '13 at 17:21

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.