injecting a temp entry into dns cache

[Jeff Reasoner]

Interesting. Intentionally "poison" your own cache so your users aren't
inconvenienced by anothers misconfiguration. Not sure how you go about
doing that on box. Perhaps bigger brains on this list can say.

I have had occasion to forge answers locally as an immediate fix for
name resolution issues which caused significant operational problems.

I elected to add the zone in named.conf and answer the query correctly
(and authoritatively) until I could get the owner to correct things. You
will probably need to add other zone records too - MX and any other A
records you can think to search for.

Personally, I wouldn't consider doing something like that in this
situation as you've described. However, mere inconvenience as I perceive
it may be significant your view. 

On Sat, 2013-02-02 at 16:41 -0500, Veaceslav Revutchi wrote:
> There is a credit union website that our users access from work and
> their dns has been broken for the past few days where the www. version
> works,  but the plain name (without the www.) points to some old IP
> that's not responding. Tried to call them and all I got was that they
> know they have some kind of problem, but they ask users to type www.
> in their browser until it's resolved.
> 
> In situations like this I would like to be able to inject an entry
> into the cache on our recursive resolvers and point it to the correct
> IP until the domain
> owner fixes the problem (poison my own cache so to speak). Is this
> something that can be done with bind without having to create a zone
> for the broken domain and make our servers act as authoritative for
> it?
> 
> Thank you,
> Slava
> _______________________________________________
> Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list
> 
> bind-users mailing list
> bind-users at lists.isc.org
> https://lists.isc.org/mailman/listinfo/bind-users