Search Again: Re: primary problem From: Men & Mice Support Date: Friday, August 27, 1999 Time: 10:49:00 am >I have resgistered a host at networksolutions (ns0.galaktos.net) but there >is a mistake with the primary and secondary servers. I have a vitual domain >: bpmobile.com > >my configuration : >---------------- > >NS0.galaktos.net A 62.160.79.142 >NS0.oleane.net A 194.2.0.30 >NS1.oleane.net A 194.2.0.60 > >The test : >-------- [snip] >bpmobile.com. 86400 SOA ns0.galaktos.net. postmaster.galaktos.net. ( >1999082500 serial >28800 refresh (8 hours) >7200 retry (2 hours) >604800 expire (7 days) >86400 ) minimum (1 day) >bpmobile.com. 86400 NS ns1.oleane.net. => false this is the secondary >bpmobile.com. 86400 NS ns0.galaktos.net. => false this is the primary >bpmobile.com. 86400 NS ns0.oleane.net. The order in which servers are reported is not important. The primary is not the one that is reported first, rather it is the one named in the SOA record. Also remember that, as far as DNS resolution is concerned, there is no difference between primary and secondary name servers. They are all authoritative for the domain, so they are all considered equivalent. Equivalent records (like your 3 NS records) are permuted for each query, so that the load is spread across them. Generally speaking, a resolver will choose the first in the list. ____________________________________________________________________ Chris Buxton Men & Mice cbuxton@menandmice.com http://www.menandmice.com

Messages In This Thread: Re: primary problem by Men & Mice Support on Aug 27, 1999 at 10:49:00 am primary problem by bertrand petitfrere on Aug 27, 1999 at 11:27:00 am