On Friday 19 October 2007 01:03, Paul Vixie wrote:
i agree that it's something BIND should do, to be
comprehensive. if someone is excited enough about this to consider
sponsoring the work, please contact me ([EMAIL PROTECTED]) to discuss details.
Sounds like a really bad idea to me.
The
1) Does anyone else find this flaw in the DNS system
as annoying as I do? If authority is to be regularly
moved around between ISPs (who may be hosting thousands
As an operator of both free and paid DNS services, I wish there was a
quick and easy way to pull a list of all of the zones that
This report used to be quite useful in that regard:
http://www.cymru.com/DNS/lame.html
Perhaps Rob needs a coffee injection to get that going again?
(BTW: Need/want some more of our famous Colo Blend Mr. Thomas?)
--chuck
Justin Scott wrote:
I suppose the problem with having an official list to query would be
getting all of the various registries to participate and keep it
regularly updated. I personally qualify this as a slight inconvenience,
but I'm not sure I would call it a flaw in the DNS system.
If we
Hi, Chuck!
This report used to be quite useful in that regard:
http://www.cymru.com/DNS/lame.html
Perhaps Rob needs a coffee injection to get that going again?
Oh, my, I'd totally forgotten about that report. I do need to get
that going again. I'll dig around now to see what we can
Justin Scott wrote:
As an operator of both free and paid DNS services, I wish there was a
quick and easy way to pull a list of all of the zones that were
delegated to a specific IP address. I say IP because people can now
register their own DNS name servers at the registrar and use our IP
How annoying or frustrating is it for people?
Is it so annoying that you'd be willing to pay for
a list of every public-facing NS record pointed at
a given IP?
Nope. As I mentioned earlier, I qualify this as a minor inconvenience
on the servers that I manage. It may be for someone who
Justin Scott wrote:
We also have home-grown scripts that figure out whether a domain is
delegated to us or not and flag the ones that aren't. In the case of
the free service we flag them for two weeks and if they still aren't
delegated to us after that period we disable them on the DNS servers
[EMAIL PROTECTED] (David Ulevitch) writes:
I should also mention the related work starting over here:
http://www.nanog.org/mtg-0710/presentations/Vixie-lightning.pdf
indeed. while i don't have even a tenth of the analysis expertise of someone
like robt, wessels, florian, or april, i am most
On Thu, 18 Oct 2007, Jack Bates said:
We use home-grown scripts to follow the NS trail and verify that we are
I do something similar with a nagios plugin (perl script). It
reports lameness and serial mismatch. I've put it online here:
The correct way to change a delegation is to:
* add the new servers as stealth servers for the
current zone.
* if the old master is to be removed, make it a slave
of the new master.
* add the new NS records to the zone.
* wait for all
[EMAIL PROTECTED] (Mike Lewinski) writes:
Justin Scott wrote:
I suppose the problem with having an official list to query would be
getting all of the various registries to participate and keep it
regularly updated. I personally qualify this as a slight inconvenience,
but I'm not sure
12 matches
Mail list logo
