Re: dns - golog

[Thomas Leavitt <thomas () thomasleavitt org>]

What would a query result for a non-functioning domain look like? Or
would this only apply to unregistered domains? Would a common user be
able to distinguish between a domain that was registered, but for which
DNS was not functioning, and one that was unregistered? If I were a
user, and forgot to renew a domain, would it immediately go into this
pool when it expired - thus presenting all of the potential viewers not
with an DNS error message, but someone else's advertising?

If I ran utilities and services which expected to obtain a different
response, depending on whether a DNS query was successfully resolved,
what would happen to them?

How would, say, SMTP servers which rejected hosts for which no valid DNS
could be determined, behave as a result of this set up - would mail no
longer be rejected if it came from
evilspammer () adfasdfjjlasdfafdkasdf com? How about programs designed to
time out when DNS lookups failed... etc. etc. There are a whole host of
issues that emerge when you deliberately and consciously "break" DNS
this way...

if golog has answers to these questions, it might be interesting to hear
them...

... finally, why go through all this hassle for what has to be an
utterly trivial amount of money resulting from people being presented
with something totally unexpected and clicking on a link therein... how
valuable are these people as customers? I can't imagine much...

Thomas

Martin Hannigan wrote:
> >     * From: Luke Besson
> >     * Date: Thu Oct 19 08:54:47 2006
> > I work for a big French ISP and I manage the DNS architecture (based
> > on Linux+Bind); Golog proposed to our society the DNS redirect
> > service (redirect all the not existant domains according to marketing
> > criteria).
> > Even if our marketing team would like to join this solution, our
> > technical team opposes hardly to such a not-standard implementation
> > of the DNS.
> > Can you suggest me any objective reason in order to invalidate this
> > proposal?
>
>
> This is a network autonomy issue. What occurs inside the provider
> edge related to routing and applications is the responsibility of
> the provider and they have the right to modify answers or routes
> in their networks, even if they are not "theirs".
>
> There is some "holy grail" you should consider, like making sure that
> etrade.com is etrade.com, the legitimate IP/trademark holder.
>
> The questions to ask yourself as an organization are something
> like this:
>
> a) is there enough revenue here to consider?
>
> b) is someone else going to capture revenue between my customer
>    and myself if I don't?
>
> c) will this break my network or the networks of others?
>
> If you can answer the first two yes, the third is worth
> trying to make "no".
>
>
> -M<
>
>
>
>
>
>
>
> -- 
> Martin Hannigan                                (c) 617-388-2663
> Renesys Corporation                            (w) 617-395-8574
> Member of Technical Staff                      Network Operations
>                                                hannigan () renesys com