Changing output of bind

[Jeff Lightner]

If its "visitors" then its not "internal" is it?

It sounds like a really bad idea.  You should explain to the user the
proper use of dig and tell him that making an internal only version
different than that seen by everyone else in the world is apt to cause
problems in resolving DNS issues later.  

If you really must do it for "internal" use perhaps writing a wrapper
script around dig and calling it something else then doing your own
queries and formatting within that script.   Call it something like
"digint" so that when people later report results you'll know their
using something other than the standard dig tool.

-----Original Message-----
From: bind-users-bounce at isc.org [mailto:bind-users-bounce at isc.org] On
Behalf Of Andy Shellam (Mailing Lists)
Sent: Monday, December 11, 2006 9:27 AM
To: bind-users at isc.org
Subject: Re: Changing output of bind


>
> Wildcards have semantics which may be suprising for the beginner. For
> instance, they do not match if there are record with data of another
> type. 
>   
True, and this makes sense.
But in the OP's scenario - I'm guessing his "user" wants to correct URL 
typos from visitors to his website, at which case it'll always be 'A' 
records that are required to be returned from the wildcard.
> (You can play with ".museum", which have wildcards. Test
> anythingwhichdoesnotexist.museum and louvre.museum.)
>   
Does this mean that if the record matches the wildcard AND has a valid 
record as well, it'll get both returned in a "round-robin" fashion?
> !DSPAM:37,457d698530861891880165!
>
>
>   


-- 
Andy Shellam
NetServe Support Team

the Mail Network
"an alternative in a standardised world"

p: +44 (0) 121 288 0832/0839
m: +44 (0) 7818 000834