Timeline for DNS caching problem
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 14, 2017 at 9:47 | comment | added | tripleee | If you actually understand these things, maybe edit your question to rule out the common misunderstandings. | |
| May 14, 2017 at 9:45 | comment | added | tripleee | Overriding the upstream TTL is standard practice; there are insane TTL values you simply should not obey, and so overrides are part of the reality. Maybe updating your question with some actual diagnostics would help us see what you are really trying to solve here. What software are these clients running and what do the incorrect and the correct results look like? | |
| May 14, 2017 at 7:40 | comment | added | Rahul | Thanks, @tripleee. Can you give an advice how can I upgrade my knowledge and provide some sources to read. > DNS is cached by design. While adding record, TTL is set to 0, which supposed to have no caching. DNS server is not a problem. Problem is a client, which caches itselves DNS requests, as referring to DNS server from another client gives right answer. | |
| May 14, 2017 at 4:59 | history | edited | tripleee | CC BY-SA 3.0 | Typos |
| May 13, 2017 at 17:44 | history | answered | tripleee | CC BY-SA 3.0 |