nanog mailing list archives
Re: Verizon transparent web caching issue? WASRe: Data Center QoS equipment breaking http 1.1?
From: Nathan Ward <nanog () daork net>
Date: Sat, 1 Aug 2009 13:13:19 +1200
On 1/08/2009, at 1:06 PM, up () 3 am wrote:
Again, turned out to be my own stupidity. It was just DNS on a secondary DNS server, which was pointing to the old IP, which was redirecting to the new IP, but at that point, the headers are lost.I would have thought that on MacOSX (my client; the server is FreeBSD 7.2-STABLE), if I tell the /etc/resolv.conf to look at the primary name server only, which has the correct info, plus doing a dnscacheutil -flushcache, that this wouldn't be an issue.Apparently, I was wrong, or perhaps it doesn't override what Verizon does with my browser's queries, despite what nslookup shows in a terminal window.
As you are on OS X, have a read of http://developer.apple.com/documentation/Darwin/Reference/Manpages/man5/resolver.5.html It lets you do per-domain resolvers, and so on. -- Nathan Ward
Current thread:
- Data Center QoS equipment breaking http 1.1? up (Jul 31)
- Re: Data Center QoS equipment breaking http 1.1? up (Jul 31)
- Verizon transparent web caching issue? WASRe: Data Center QoS equipment breaking http 1.1? up (Jul 31)
- Re: Verizon transparent web caching issue? WASRe: Data Center QoS equipment breaking http 1.1? jay (Jul 31)
- Re: Verizon transparent web caching issue? WASRe: Data Center QoS equipment breaking http 1.1? up (Jul 31)
- Re: Verizon transparent web caching issue? WASRe: Data Center QoS equipment breaking http 1.1? Nathan Ward (Jul 31)
- Verizon transparent web caching issue? WASRe: Data Center QoS equipment breaking http 1.1? up (Jul 31)
- Re: Data Center QoS equipment breaking http 1.1? up (Jul 31)