[164129] in North American Network Operators' Group
Re: DNS caching issues with AT&T, Verizon (UUNET) DNS Servers
daemon@ATHENA.MIT.EDU (Ilan Erenstein)
Wed Jun 26 09:44:43 2013
From: Ilan Erenstein <ilan@jobvite.com>
To: Anthony Williams <alby.williams@verizon.com>
Date: Wed, 26 Jun 2013 13:44:07 +0000
In-Reply-To: <51CAE8C9.9050708@one.verizon.com>
Cc: "<nanog@nanog.org>" <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
Thank you very much good sir. We appreciate it.
-Ilan
On Jun 26, 2013, at 6:12 AM, Anthony Williams <alby.williams@verizon.com> w=
rote:
>=20
> Ilan:
>=20
> I passed along your request on the UUNET end and the cache has now
> been flushed on the US side. I might have to do some POC digging on the
> UK side.
>=20
>=20
> jobvite.com@198.6.100.25 (UUNET (US)):
>=20
> jobvite.com. 300 IN SOA ns-1989.awsdns-56.co.uk.
> awsdns-hostmaster.amazon.com. (
> 2013062506 ; serial
> 7200 ; refresh (2 hours)
> 900 ; retry (15 minutes)
> 86400 ; expire (1 day)
> 300 ; minimum (5 minutes)
> )
>=20
>=20
> -Alby
>=20
>=20
>=20
>=20
>=20
>=20
>=20
> On 6/25/2013 11:28 PM, Ilan Erenstein wrote:
>> Hello all,
>>=20
>> I'm writing to all of you in hopes that you're able to help me. The web=
site for the company I work for jobvite.com<http://jobvite.com> was hosted=
by GoDaddy. They dropped our record and it was able to propagate to all I=
SPs DNS servers. I was able to move our record on OpenSRS but not before e=
mpty records were able to propagate to several DNS servers. Now our custom=
ers aren't able to pull up our website. This is also causing rejected/defe=
rred emails into our candidate system.
>>=20
>> This is what I'm seeing: http://www.digwebinterface.com/?hostnames=3Djob=
vite.com&type=3DSOA&colorize=3Don&useresolver=3D8.8.4.4&ns=3Dall&nameserver=
s=3D
>>=20
>> I need help with clearing the cache for AT&T and Verizon (UUNET) DNS ser=
vers to make sure they pick up the new record for our domain. Here are som=
e of the DNS servers from the above link:
>>=20
>> 165.87.13.129 (AT&T (US))
>> 158.43.240.3 (UUNET (UK))
>> 198.6.100.25 (UUNET (US))
>>=20
>> Any help in getting this problem resolved from the network folks in AT&T=
and Verizon (UUNET) would be greatly appreciated.
>>=20
>> Thanks,
>>=20
>> Ilan Erenstein
>> Jobvite Inc.
>> ilan@jobvite.com<mailto:ilan@jobvite.com>
>> (415) 866-8738
>>=20
>=20
>=20
