Hey Slava,
You can use a small DNS proxy that will forge only this specific record
while for others it will just pass it.
By adding a forward DNS zone and add the proxy as the forward DNS server.
This is *not* recommended but these are the tools you have.
If the DNS proxy is not the well written your users will have troubles.
On 2/2/2013 11:41 PM, 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
--
Eliezer Croitoru
http://www1.ngtech.co.il
_______________________________________________
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe
from this list
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
