Level3 DNS not resolving for our domains

Mailman List Mirror (Read Only)
1

Is anyone seeing issues with domains not resolving at 4.2.2.[1-6]? All other test DNS servers function correctly.

Thank you,

2

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
Direct: 937-552-2343
1100 Wayne St
Suite 1337
Troy, OH 45373

3

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.

4

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 name?

Level 3 public DNS resolvers work fine for me (tested with several
names, both DNSSEC and not DNSSEC).

5

rocketktg.com <http://rocketktg.com/>

6

;; 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?

7

Seems like a good candidate for reading http://www.rfc-editor.org/rfc/rfc2182.txt

- jared

8

a message of 35 lines which said:

Both are in the same AS, perhaps a routing issue?

Indeed. This is a warning in ZoneMaster
<https://zonemaster.net/test/b9c2efd5a10f2eb8> and I observe also that
10-15 % of the RIPE Atlas probes cannot resolve this name (so it is
not just Level 3). The name servers unfortunately do not reply to ICMP
echo so it is hard to debug.

9

rocketktg.com <http://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