> > Anyway, my head hurts a lot, I am going to bed. > > So does mine, from banging my head against the wall trying to understand > why you're so obstinate about this.. > > This will be my last post on this thread.. and this is one time that I will > not feel afraid to say that I hope I *NEVER* do business with you... > > I've had enough, I simply cannot be bothered trying to help you correct > your understanding. if this mail seems at all bitchy, it is probably, I'm > frustrated with your inability to listen.
Mike, I had one line in an email about another topic that said I had my DNS records on a USA server coz it made for fast changes to other DNs servers. since then I have been getting hammered about it being an incorrect statement. for me it is not incorrect. I have had a customer in the Brazil, with a site hosted in the US and the DNS on an NZ machine. When the NZ machine changed the DNS record I was still getting directed to the old site as was the Brazillian client. The NZ site used caching and all sorts of crap that made their updates slow and inaccurate. After moving the record to a US DNs server my client was getting through to the new machine succesfully. now if that isn't a case of a central ( to my client and I) DNs being more efficient I don't know what is. The theory is fine, the reality is different. The other reality is trying to get DNs servers who are close to me to release their hold on a DNS cache when the record changes. This happens a lot when swapping a server out for a live update to a new version of some software or another in a live 24/7 environment. The location of the DNS record becomes important for speed of changes to a wide network of users. Once again I got sick of working with little back woods DNs servers that didn't get changes through fast enough to make it a viable option to use them for my over seas clients. As I have stated before I realise there is no central DNS server.I know the Web is a web but there is a backbone to it, or at least a series of backbones to it. Dont tell me there isn't or else I will site you the links between here and the US, here and Australia ... and the main gateways that server them such as Waikato. >Bzzzzzzzzzt. It *does* *not* *matter*. the DNS records are not served from >your registrar, only the glue record is, which is sent to a relevant root >server for the TLD... they're served from there, and that record tells the >world where to go for that domain. The records are served from *YOUR* DNS >server. Which is in the US of bloody A....for the zillionth time. Now who is not listening..... > So does mine, from banging my head against the wall trying to understand > why you're so obstinate about this.. I become obstinant when people treat me like a moron by picking on a single line from an email on another topic which while it may not be 100% technically correct doesn't really matter because it didn't affect the amain thrust of what I was saying. I cant by bothered being 100% anal retentive correct about every line of every email. > > This will be my last post on this thread.. and this is one time that I will > not feel afraid to say that I hope I *NEVER* do business with you... > I've had enough, I simply cannot be bothered trying to help you correct > your understanding. if this mail seems at all bitchy, it is probably, I'm > frustrated with your inability to listen. My understanding is fine, thank you very much. I know there is one record for every domain. I know there are lookups that keep searching until they find the answer they want ( or not depending on the link) I know about caching and I know about droping caches and renewing lookups. But I also know the hash that caching can make on occaision and I have expereinced it. If I choose to believe putting my registration or record on a USA server makes it more efficient or faster that is for me to believe. Until you know and understand my reasoning you don't have the right to say I am wrong. To malign my aptitude in my chosen proffession is bloody rude. you have no idea what I do, why I do it or how I do it. To be told I am an incompetent DNs administrator or set them up for companies is a laugh as I never do that and have never done that or even suggested I do that. You might know more abut DNS etc than me, big deal. I know the trouble DNS caching can cause, the cockups people make and the trouble it presents in a real world situation. If I wasn't suffering from a class A migraine I might actually be able to summon enough wits together long enough to show you via diagram why it can cause problems. Instead all I will say is that having worked in the third world, having worked with large corporates, having worked with multinationals I can tell you the theory is not always the reality. Shane
