1

I have a wildcard DNS on my external service: *.example.com

I have one specific service, that I need to NOT resolve externally, to help a VPN service type connection fail silently.

If there a way to make a specific entry NOT resolve? i.e. server.example.com should not resolve.

thanks

1 Answer 1

3

Lookups to Wildcard DNS entries will fail if they match any existing non-wildcard record. You could set up a "dummy" TXT record for server.example.com and host lookups (A or CNAME) for that record should fail to resolve.

The BIND example would be:

server.example.com.      IN     TXT    "Nothing to see here"
5
  • 1
    I don't think that will fail if they match any existing record is the best way to describe expected wildcard behavior (it seems suggest both that they actually matched and that something failed), wildcards are simply defined such that they do not match any branches that exist. May 18, 2015 at 5:55
  • Putting a dummy "TXT" record isn't going to help if the query asked for an "A" record. May 18, 2015 at 7:36
  • @ThatGraemeGuy - I'm not an expert, but the rules of wildcard DNS (and my experience with disappearing MX resolution when adding A records) suggests that it will work. See the "host1.example." example on the Wikipedia article for Wildcard DNS.
    – Andy
    May 18, 2015 at 7:51
  • @ThatGraemeGuy Yes, as Andy said the wildcard rules are based on the existence of names, not on specific record types. The proposed solution will work. May 18, 2015 at 8:04
  • @Andy: So I've run into a weird vote locking thing: "You last voted on this answer 5 hours ago. Your vote is now locked in unless this answer is edited.". If you can find some way to make a minor edit to your answer I can reverse my downvote. May 18, 2015 at 12:47

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .