Saturday, June 22, 2002, 7:20:09 PM, Dave Warren wrote: >> 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. You can also use dig to find out how long till the cached response will expire at that nameserver. I'll give you an example If I do: dig @ns.qnis.net wxweb.com a I get the following response: wxweb.com. 10M IN A 63.160.181.144 I have a 10M TTL set on that record, so the ns.qnis.net nameserver (the nameserver of a local ISP here in Fresno) will now cache that data for 10 minutes (hence the 10M in the response). If I do it again a little over a minute later I get this response: wxweb.com. 8m55s IN A 63.160.181.144 It is telling me that its remaining TTL in cache for that record is 8 minutes and 55 seconds. If you know the address of the nameservers being used by the customer, you can use dig to query them and see how long the TTL is on the cached bad data. -- Best regards, William X Walsh <[EMAIL PROTECTED]> -- OpenSRS installation and customizations Payment Processing Integration Apache Installation and Support Services http://www.wxsoft.com/
