hi, > swinog.ch nameserver = a.ns.swinog.ch > swinog.ch nameserver = b.ns.swinog.ch > swinog.ch nameserver = c.ns.swinog.ch > swinog.ch nameserver = d.ns.swinog.ch > swinog.ch nameserver = e.ns.swinog.ch > swinog.ch nameserver = f.ns.swinog.ch > swinog.ch nameserver = g.ns.swinog.ch > swinog.ch nameserver = h.ns.swinog.ch > a.ns.swinog.ch internet address = 62.220.128.88 > b.ns.swinog.ch internet address = 62.220.128.98 > c.ns.swinog.ch internet address = 130.59.1.30 > d.ns.swinog.ch internet address = 130.59.10.30 > e.ns.swinog.ch internet address = 195.162.161.182 > f.ns.swinog.ch internet address = 81.94.96.96 > g.ns.swinog.ch internet address = 146.228.10.16 > h.ns.swinog.ch internet address = 146.228.14.10
Not afraid of DNS-poisoning? If any of the above DNS would be 0wned and would send falsified data for swinog.ch, the page could be hijacked to point somewhere else. More servers = more risk. RFC2182 [1], Section 5, is very clear about this: More servers also increase the likelihood that one server will be misconfigured, or malfunction, without being detected. Oh and even more :) On the other hand, having large numbers of servers adds little benefit, while adding costs. At the simplest, more servers cause packets to be larger, so requiring more bandwidth. This may seem, and realistically is, trivial. However there is a limit to the size of a DNS packet, and causing that limit to be reached has more serious performance implications. Why didn't you just increase the TTL? The current TTL of 1800 is far too low, causing unecessary traffic and latency, as it does not stay long enough in the ISP's caches. It is common to use TTL's around 172800 (2 days), at least for static addresses. If your server is down for more than 2 days, you're out of business anyway. [1] ftp://ftp.rfc-editor.org/in-notes/rfc2182.txt -daniel ---------------------------------------------- [EMAIL PROTECTED] Maillist-Archive: http://www.mail-archive.com/swinog%40swinog.ch/
