ad.de.doubleclick.net and bind8/9

[phn at icke-reklam.ipsec.nu]

Dirk Janssen <dirk at no.netspam.de> wrote:
> Hi,

> I encountered a problem on all our recursive caching-only nameservers
> (and even others) running bind8.4.4/bind8.4.5 with resolving the host
> mentioned above. When the cache is empty (after restart) then the host
> can be resolved, but if you ask just for one time for the nameserver(s)
> of 3de.doubleclick.net (the domain to where the cname points) then you
> get an answer of an unresolvable host (with a TTL of 1 Week). After
> that, ad.de.doubleclick.net can't be resolved anymore and the query end=
s
> up in a timemout (probably for 1 Week) what is really annoying because =
a
> lot of websites using this ad-server are incredibly slow because of thi=
s
> issue.
> So far I think this is a problem of doubleclick (it would be nice if
> somebody could also check and verify this). But what I've encountered i=
s
> that bind9.2.3 behaves in another way. What you get here is a SERVFAIL
> and not a timeout and even this SERVFAIL comes just for a short time (i=
t
> seems to depend from how often you queried the ns of
> 3de.doubleclick.net?). What's the reason for this different behaviour?
> Is the timeout a bug of bind8? What would be the correct rfc-conform
> behaviour?
> Because of performance issues I really don't want to upgrade to bind9.

> Regards,

> Dirk

The fix is easy, create a "doubleclick.net" zone with only a SOA=20
record. Keeps lots of banners away!



--=20
Peter H=E5kanson        =20
        IPSec  Sverige      ( At Gothenburg Riverside )
           Sorry about my e-mail address, but i'm trying to keep spam out=
,
	   remove "icke-reklam" if you feel for mailing me. Thanx.