[116351] in North American Network Operators' Group
Re: Verizon transparent web caching issue? WASRe: Data Center QoS
daemon@ATHENA.MIT.EDU (Nathan Ward)
Fri Jul 31 21:14:27 2009
From: Nathan Ward <nanog@daork.net>
To: nanog list <nanog@nanog.org>
In-Reply-To: <Pine.BSF.4.64.0907312101460.97420@richard2.pil.net>
Date: Sat, 1 Aug 2009 13:13:19 +1200
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
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
