Re: spurious updates

[Bruce Campbell <bruce.campbell@ripe.net>]

On Tue, 29 Jan 2002, Simon Coffey wrote:

> I've proposed a draft before that would reserve a TLD for use on private
> networks,  for exactly this kind of reason - to stop internal DNS naming
> structures leaking out to the internet in some way or another.    For
> example if psg were using psg.pri as their internal win2k domain, (not
> .com) I don't believe this sort of problem would occur.
> (Oh, and yes, I'd prefer Win2k wouldnt do this kind of thing at all. But
> it does.)

urm, Randy is complaining about dynamic IP addresses from Hosts *outside*
his administrative control.  The problem is not with the psg end, but with
the sites that are referencing psg in some-to-be-determined manner.

If everyone did use a good naming schemes, we'd be happy.  If we, as
nameserver operators who get unwanted dynamic updates, were able to point
people at some sort of naming standard and say 'Fix it', we'd be happier.

The classic example of organisations making up their own standards and not
referencing others, is Microsoft's suggestion of 'Use "INT" for your
Internal naming structures'.  The nameservers for 'int.' thus get a nice
loading of dynamic updates.

Regards,

-- 
                             Bruce Campbell                            RIPE
                   Systems/Network Engineer                             NCC
                 www.ripe.net - PGP562C8B1B                      Operations