cool down man. humahagibis ka naman agad eh =) just re-read the original post:
---ORIGINAL POST--- 1. what is the priority of the ns that is given to the client? is it the first ns and if it fails it goes to the second? is it round-robin? 2. is there any way of controlling this? ---END--- i got the feeling that the poster wanted to control which of his servers will answer dns request most of the time and do not want to be under the mercy of the client's querying algorithms/preference. On 3 Jul 2003, Hagibis Fan wrote: > sure all these may work..but my $0.2 is: why??? > the point of having multiple DNS servers > is to spread zone info on as wide as possible; > they should also contain IDENTICAL information > (one master and all the other slaves loading > on the master). no issue here. we are not trying to defeat DNS itself. that all NS servers have identical info is a given. > so for > 2 IPs on the same machine is kinda pointless > since they'll go down the same way. I'd spread > DNS servers as far apart as I can (different > computer, different network segment, diffrent > country!). so anyway it shouldt matter which > dns server gets priority, they should contain > the same info! the purpose of multiple IPs is too simply increase round-robin hit rate probability for a prefered server. IT is NOT to increase uptime. the downside to this is that "dead spot" hit rate also increases if the preferred server goes down and it is totally useless for clients not doing round-robin--> which brings us to udp-proxying with failover solution. > PLUS, all the other nameservers > cache yur info already anyway (the client's > ISP's name servers WILL HAVE your zone info > and WILL STAY on their cache as per your > Zone's TTL values...so why bother to cache > it.. > > so anyway i dont know what the original poster > wanted to do.....its rare that one has like a hundred > zones so why load balance it (if load balancing > is the objective)-- > udp-proxy+failover with DNS: so that you can make the preferred machine serve most queries during its uptime no matter what algo the client is using without the nasty side-effect of introducing an increased dead-spot hit rate during its downtimes. load-balancing was just optional because most L4 hardware offer it for orgs with hundreds of zones or for DOS protection. pe-preno na ko dito. =) pong -- Philippine Linux Users' Group (PLUG) Mailing List [EMAIL PROTECTED] (#PLUG @ irc.free.net.ph) Official Website: http://plug.linux.org.ph Searchable Archives: http://marc.free.net.ph . To leave, go to http://lists.q-linux.com/mailman/listinfo/plug . Are you a Linux newbie? To join the newbie list, go to http://lists.q-linux.com/mailman/listinfo/ph-linux-newbie
