search for: rscott

...ers: >> Thanks Rowland. Perhaps because I expected these basic issues to have >> been resolved long ago I never thought to check the SOA records. You are >> perfectly correct - the second DC is not listed > > since when is more than one NS listed in the SOA? > > http://rscott.org/dns/soa.html > > MNAME ("Primary NS") - This entry is the domain name of the name > server that was the original source of the data (this entry MUST be > your primary nameserver). This is your primary nameserver, and MUST be > the one and only server that you ever up...

...ic issues to have >>>> been resolved long ago I never thought to check the SOA records. >>>> You are >>>> perfectly correct - the second DC is not listed >>> >>> since when is more than one NS listed in the SOA? >>> >>> http://rscott.org/dns/soa.html >>> >>> MNAME ("Primary NS") - This entry is the domain name of the name >>> server that was the original source of the data (this entry MUST be >>> your primary nameserver). This is your primary nameserver, and MUST be >>> the...

Thanks Rowland. Perhaps because I expected these basic issues to have been resolved long ago I never thought to check the SOA records. You are perfectly correct - the second DC is not listed. I will say however that other than this, All the DNS issues I encountered during my early testing phase, and there were a lot of them, occurred with both internal and BIND DNS. As a consequence, we use

...sic issues to have >>>> been resolved long ago I never thought to check the SOA records. You are >>>> perfectly correct - the second DC is not listed >>>> >>> >>> since when is more than one NS listed in the SOA? >>> >>> http://rscott.org/dns/soa.html >>> >>> MNAME ("Primary NS") - This entry is the domain name of the name >>> server that was the original source of the data (this entry MUST be >>> your primary nameserver). This is your primary nameserver, and MUST be >>> the...

...d long ago I never thought to check the SOA records. >>>>>> You are >>>>>> perfectly correct - the second DC is not listed >>>>> >>>>> since when is more than one NS listed in the SOA? >>>>> >>>>> http://rscott.org/dns/soa.html >>>>> >>>>> MNAME ("Primary NS") - This entry is the domain name of the name >>>>> server that was the original source of the data (this entry MUST be >>>>> your primary nameserver). This is your primary nameserv...

...rds. >>>>>>>> You are >>>>>>>> perfectly correct - the second DC is not listed >>>>>>> >>>>>>> since when is more than one NS listed in the SOA? >>>>>>> >>>>>>> http://rscott.org/dns/soa.html >>>>>>> >>>>>>> MNAME ("Primary NS") - This entry is the domain name of the name >>>>>>> server that was the original source of the data (this entry MUST be >>>>>>> your primary nameserver...

...land. Perhaps because I expected these basic issues to have >>> been resolved long ago I never thought to check the SOA records. You are >>> perfectly correct - the second DC is not listed >> >> since when is more than one NS listed in the SOA? >> >> http://rscott.org/dns/soa.html >> >> MNAME ("Primary NS") - This entry is the domain name of the name >> server that was the original source of the data (this entry MUST be >> your primary nameserver). This is your primary nameserver, and MUST be >> the one and only server...

Author: rscott Repository: /hg/zfs-crypto/gate Revision: 62b93b722bf87e37f0366e06956dcbcbcefe10f9 Log message: 6314417 ASSERT failure on Panther during memory/cpu stress test Files: update: usr/src/uts/sun4u/cpu/us3_common.c

...gt;>> been resolved long ago I never thought to check the SOA records. >>>>> You are >>>>> perfectly correct - the second DC is not listed >>>> >>>> since when is more than one NS listed in the SOA? >>>> >>>> http://rscott.org/dns/soa.html >>>> >>>> MNAME ("Primary NS") - This entry is the domain name of the name >>>> server that was the original source of the data (this entry MUST be >>>> your primary nameserver). This is your primary nameserver, and MUST be...

...to have >>>>> been resolved long ago I never thought to check the SOA records. You are >>>>> perfectly correct - the second DC is not listed >>>>> >>>> since when is more than one NS listed in the SOA? >>>> >>>> http://rscott.org/dns/soa.html >>>> >>>> MNAME ("Primary NS") - This entry is the domain name of the name >>>> server that was the original source of the data (this entry MUST be >>>> your primary nameserver). This is your primary nameserver, and MUST be...

...ht to check the SOA records. >>>>>>> You are >>>>>>> perfectly correct - the second DC is not listed >>>>>> >>>>>> since when is more than one NS listed in the SOA? >>>>>> >>>>>> http://rscott.org/dns/soa.html >>>>>> >>>>>> MNAME ("Primary NS") - This entry is the domain name of the name >>>>>> server that was the original source of the data (this entry MUST be >>>>>> your primary nameserver). This is your...

...;>>>> You are >>>>>>>>> perfectly correct - the second DC is not listed >>>>>>>> >>>>>>>> since when is more than one NS listed in the SOA? >>>>>>>> >>>>>>>> http://rscott.org/dns/soa.html >>>>>>>> >>>>>>>> MNAME ("Primary NS") - This entry is the domain name of the name >>>>>>>> server that was the original source of the data (this entry >>>>>>>> MUST be >&g...

...t to check the SOA records. >>>>>> You are >>>>>> perfectly correct - the second DC is not listed >>>>>> >>>>> >>>>> since when is more than one NS listed in the SOA? >>>>> >>>>> http://rscott.org/dns/soa.html >>>>> >>>>> MNAME ("Primary NS") - This entry is the domain name of the name >>>>> server that was the original source of the data (this entry MUST be >>>>> your primary nameserver). This is your primary nameserv...

Hi, I'm using rsync on 2 sme servers and attempting to get sync2nas to work from my windows 2003 servers to my sme server for backup purposes I can successfully rsync between the two sme servers and in a local setting can run syn2nas between windows and sme server however I cannot get syn2nas to work outside the local network, My ultimate goal is the allow my windows server to backup to sme