In message <[email protected]>, Wouter Cloetens writes: > On 01/08/12 16:13, Mark Andrews wrote: > > In message<[email protected]>, Wouter Cloetens writes: > >> On 01/08/12 03:26, Curtis Villamizar wrote: > >>> Anything DNS related should be reliable. Therefore a secondary would > >>> be preferable to not having one. > >> > >> OTOH, the use case of a DNS lookup for a hostname or IP address for > >> which the last-hop router is offline (at the time of the lookup) is > >> limited. > >> It is there; e.g. batch log processing on web servers, but that is for > >> informative purposes only, and doesn't cause connection failures. > > > > This is crazy talk. We have absolutely no idea what will or will > > not end up being run from the home. Whether people will need to > > lookup information about the home when it is unreachable or not. > > How do you debug if you can reach home or not if you can't get the > > addresses of the machines at home? > > If you need to run a reliable service, you shouldn't be running it from > your home. The use case of homenet is restricted to that.
The only real difference between home and commercial is SLA agreements and MTR. Home is a perfectly fine place to run some services. Some services can only be run from the home. Additionally PTR records are not the only think that gets stored in the reverse DNS. > What you understand as "crazy talk," I see as; trying to get something > working, in best-effort mode, taking into account the limitations of a > home network with a CE router in front of it. > We assume that a DynDNS-style approach simply will never scale for every > IPv6 address in the home, and therefore the home router has to be > authoritative, handling the requests. Actually dynamic DNS is extremely cheap and can scale to every device. Costs to host zones in volume are in single dollar digits / zone / year. Automation reduces these costs towards the pure hardware and comm costs which continue to drop. > > The DNS was designed with the idea that there would be redundent > > servers. It is not designed to deal with not being able to connect > > to any servers for a zone and it really does not work well when > > this is the case. > > If you *are* running a service from home, there is always the option of > setting up DynDNS specifically for those hosts that need to be accessible. > -- > Architect Core Gateway SoftAtHome R&D RGW http://www.softathome.com/ > http://www.linkedin.com/in/wcloetens Vaartdijk 3/B701, B-3018 Wijgmaal > Tel: +32-16-852010 Mobile: +32-492-277790 Fax: +32-16-852099 > > This message and any attachments are confidential, intended solely for > the addressees and are SoftAtHomes ownership. > Any unauthorized use or dissemination is prohibited. If you are not the > intended addressee of this message, please cancel it immediately and > inform the sender. -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: [email protected]
_______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
