-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 For the Internet, ns1 going down should cause all resolvers to switch over to ns2. This should happen automatically, with the only result being a slight slowdown of resolution for a very small fraction of your web visitors, ftp users, etc.
Of course, if ns2 is at all flakey, you're in trouble. For local users, the picture may be different, depending on your resolving architecture. Stub resolvers don't handle failures well, so if users are hitting your authoritative servers directly, having ns1 go down could easily be a problem. Chris Buxton Professional Services Men & Mice On Aug 9, 2008, at 12:43 AM, MontyRee wrote: > > Hello, all. > > > I have operated two dns(primary and secondary) for one domain like > below. > > > example.com IN NS ns1.example.com > example.com IN NS ns2.example.com > > > and there was a event that ns1.example.com dns was down. > As I know, if ns1 dns is down, all requests go to the ns2.example.com. > > But when ns1.example.com dns was down, actually some people can't > lookup the domain. > > What's the problem and how can I solve this problem? > > If I adding some dns server like ns3,ns4.ns5, it would be helpful to > solve this problem? > > > Thanks. > > > Regards. > > > > > > > > > > _________________________________________________________________ > 간편하고 정확한 나만의 맞춤 검색, Live Search! > http://search.live.com > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAkighvgACgkQ0p/8Jp6Boi1f5wCgiOqCGYszaa9Evt/WryHDGhU8 LPAAn0wDMn02t3+9mSb8QkFcn5LiMHoy =2gcC -----END PGP SIGNATURE-----
