> What is happening so that I do NOT lie to another customer, although be > it not on purpose? I do NOT like NOT knowing the truth. > > If anyone out there knows FIRST HAND, not HEARSAY, please respond. All > of us, do NOT know for sure, we are more then likely repeating > what we have been TOLD. What is the LOGICAL explanation?
Perhaps you should grab yourself a copy of dig and check out how the process works for yourself. You can poke at the root servers, your ISP's nameservers, whatever you like, and verify the TTLs being passed out. You should be able to confirm who is caching what from this information, and the authority flag returned from a DIG query. > All I know for a FACT, is that when I worked at AOL, I was told just > what I said, and that is what to say > to customers who call, and say they can't get their website to work, we > had to ask if they had just made a change > to their nameserver, that way we did not spend a bunch of time poking > through the pc, seeing if our software had a problem. I might be way off base, but if I remember correctly AOL used to to mishandle this and cache DNS data longer then the zonefile's TTL. AOL still, to this day, mishandles email headers, fails to process usenet crossposts properly, and any number of other small issues which show how little regard AOL has for internet standards. -- The nice thing about standards, there is enough for everyone to have their own.
