Discuss mailing list

[Jeff Taylor <shdwdrgn AT sourpuss.net>]

Keep in mind that the zone files and various lists are only being used
for human reference.  When you configure DNS service on your computer,
you are entering an IP address directly.  It would certainly make
everyone's life much easier if there were a method for using hostnames
for your DNS entries... however since you need dns working to look up
the hostnames, you get into a catch-22 situation.

If someone were to write a Windows service that periodically updated the
computer's DNS entries based on the information we provide, then having
rapid updates to server status would be more useful.  It would be a
simple matter for me to add country-based entries to the zone file that
only list the servers which are currently functional, then users could
simply pick which list they want to use as their pool, and their
computer could automatically be kept up to date with the appropriate
information.  THIS is something that I think would really make us stand
out ahead of other alternate DNS services, because then no-one should
have any issues with name resolution despite the rotating pool of public
servers.

On 10/10/2012 12:01 PM, Jamyn Shanley wrote:
> Given how critical DNS is to both the end-user experience and general
> net functionality, I don't understand why non-responsive servers
> aren't removed from the zonefiles within 15 minutes of a problem.
> There's no reason why they couldn't be put back in rotation within an
> hour or two of being 100% functional again, but I gotta say if my
> local ISP had a policy that allowed them 7 days to get one of their
> DNS servers fixed (and also left the problematic server listed on
> their website/documentation) I'd be ... disappointed in their
> professionalism.