akamaitechnologies.com sending queries to the wrong dns server?
Carl Byington
carl at byington.org
Thu Jul 26 20:05:01 UTC 2012
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
client 23.3.104.194#52078 (116.226.242.64.in-addr.arpa): view normal:
query (cache) '116.226.242.64.in-addr.arpa/PTR/IN' denied
client 193.108.152.26#60940 (96.226.242.64.in-addr.arpa): view normal:
query (cache) '96.226.242.64.in-addr.arpa/PTR/IN' denied
dig 226.242.64.in-addr.arpa ns
;; ANSWER SECTION:
226.242.64.in-addr.arpa. 13783 IN NS ns2.savvis.net.
226.242.64.in-addr.arpa. 13783 IN NS ns3.savvis.net.
226.242.64.in-addr.arpa. 13783 IN NS ns1.savvis.net.
dig 96.226.242.64.in-addr.arpa ptr
;; ANSWER SECTION:
96.226.242.64.in-addr.arpa. 14400 IN CNAME 96.0-25.226.242.64.in-
addr.arpa.
96.0-25.226.242.64.in-addr.arpa. 86400 IN PTR
totally.bogus.name.delegation.
;; AUTHORITY SECTION:
0-25.226.242.64.in-addr.arpa. 86400 IN NS bigblue.pcsolve.com.
0-25.226.242.64.in-addr.arpa. 86400 IN NS ns2.pcsolve.com.
Akamai is sending queries for 116.226.242.64.in-addr.arpa/PTR to the
pcsolve dns servers. Am I missing something, or is that just wrong? The
PTR records are inside the 0-25.226.242.64.in-addr.arpa zone.
Akamai seems to be confused by the rfc2317 delegation.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.14 (GNU/Linux)
iEYEARECAAYFAlARoq0ACgkQL6j7milTFsGZ4QCfcr1wYAAzH1WHn/Jrrlk9Rt7O
Fn0An17rh//4om4F/BS/EVBK3q8kXiXf
=6ov0
-----END PGP SIGNATURE-----
More information about the bind-users
mailing list