Re: Level3 DNS not resolving for our domains

2015-12-30 Thread Randy Bush
>> rocketktg.com > > ;; ADDITIONAL SECTION: > ns1.rocketktg.com.244 IN A 68.235.47.109 > ns2.rocketktg.com.244 IN A 68.235.47.110 rfc2182 section 6

Re: Level3 DNS not resolving for our domains

2015-12-30 Thread Stephane Bortzmeyer
On Wed, Dec 30, 2015 at 11:12:29PM +0100, Alarig Le Lay wrote a message of 35 lines which said: > Both are in the same AS, perhaps a routing issue? Indeed. This is a warning in ZoneMaster and I observe also that 10-15 % of the RIPE Atlas probes c

Re: Level3 DNS not resolving for our domains

2015-12-30 Thread Jared Mauch
> On Dec 30, 2015, at 5:12 PM, Alarig Le Lay wrote: > > On Wed Dec 30 15:48:26 2015, Otto Monnig wrote: >> rocketktg.com > > ;; ADDITIONAL SECTION: > ns1.rocketktg.com.244 IN A 68.235.47.109 > ns2.rocketktg.com.244 IN A 68.235.47.110

Re: Level3 DNS not resolving for our domains

2015-12-30 Thread Alarig Le Lay
On Wed Dec 30 15:48:26 2015, Otto Monnig wrote: > rocketktg.com ;; ADDITIONAL SECTION: ns1.rocketktg.com. 244 IN A 68.235.47.109 ns2.rocketktg.com. 244 IN A 68.235.47.110 Both are in the same AS, perhaps a routing issue? -- Alarig

Re: Level3 DNS not resolving for our domains

2015-12-30 Thread Otto Monnig
rocketktg.com -- Otto Monnig > On Dec 30, 2015, at 3:18 PM, Stephane Bortzmeyer wrote: > > On Wed, Dec 30, 2015 at 03:02:39PM -0600, > Otto Monnig wrote > a message of 24 lines which said: > >> Sorry for not providing domains - I did so intentionally, as I >> belie

Re: Level3 DNS not resolving for our domains

2015-12-30 Thread Stephane Bortzmeyer
On Wed, Dec 30, 2015 at 03:02:39PM -0600, Otto Monnig wrote a message of 24 lines which said: > Sorry for not providing domains - I did so intentionally, as I > believe this is a policy change at L3, rather than a technical > issue. And how are we supposed to debug, without even one domain na

Re: Level3 DNS not resolving for our domains

2015-12-30 Thread Otto Monnig
Sorry for not providing domains - I did so intentionally, as I believe this is a policy change at L3, rather than a technical issue. One of our companies hosts multiple domains and the issue is widespread among those domains at several locations. -- Otto Monnig > On Dec 30, 2015, at 11:07 AM

Re: Level3 DNS not resolving for our domains

2015-12-30 Thread Josh Luthman
Works for me: >dig google.com @4.2.2.2 +short 216.58.216.238 I expect your IP (either /32 or larger) may have done too many requests within a finite time window. Those DNS servers quit responding after too many inquiries (I don't know the count or time frame). Josh Luthman Office: 937-552-2340

Level3 DNS not resolving for our domains

2015-12-30 Thread Otto Monnig
Is anyone seeing issues with domains not resolving at 4.2.2.[1-6]? All other test DNS servers function correctly. Thank you, -- Otto Monnig CTO KTG IP, LLC