[as112-ops] AS112 nameservers as NS for parked domains

[Warren Kumari]

On Monday, December 1, 2014, Jonathan Stewart <jonathan.stewart at gmail.com>
wrote:

> I assume that the motivation for this is because somebody will check if a
> valid DNS server is present at that IP address, even though the check is
> not to see if it's authoritative for the zone?
>
> Why not just use 1.1.1.1 as your nameserver, if you want to provide a fake
> IP address?  Or ns1.google.com if it need a domain name?
>
>
Because that's *really* impolite.

Simply choosing an IP at random and using it as a bit bucket is similar to
dropping your chewing gum on the ground because doing the right thing was
too hard.
Just because a bunch of people use 1.1.1.0/24 (and 1.2.3/24) as garbage
destinations doesn't make it right - see
http://www.potaroo.net/studies/1slash8/1slash8.html (Geoff Huston from
APNIC report on this).
Believe me, Google also doesn't really want random stuff pointed at ns[1-4].
google.com - sure it will get lost in the noise, but doesn't mean it's
right...

W

I can't really see why anyone would do this.
>
> On Mon, Dec 1, 2014 at 2:04 PM, William F. Maton Sotomayor <
> wmaton at ottix.net> wrote:
>
>>
>> Hi all,
>>
>>         I recall seeing a posting either here in this list or in another
>> list about someone registering or parking a domain by using the AS112
>> anycast addresses as their nameservers.
>>
>>         Can anyone think of reasons why this is or isn't a good idea both
>> from the perspective of the domain name operator and the AS112 operator?
>>
>> wfms
>> _______________________________________________
>> as112-ops mailing list
>> as112-ops at lists.dns-oarc.net
>> https://lists.dns-oarc.net/mailman/listinfo/as112-ops
>>
>
>
>
> --
>      Jonathan
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.dns-oarc.net/pipermail/as112-ops/attachments/20141201/155a358a/attachment.html>