[EMAIL PROTECTED] (Petri Helenius) writes:
I´m constantly seeing responses to queries for AOL servers which come
in from different IP addresses than the query was sent to.
due to the weakness of the 16-bit query id field, bind will throw that
stuff away. the source address and port has to
anyone here having problems resolving americaonline.aol.com with spoof
protection enabled on their dns servers? It appears AOL via a series of
cnames is specifying a non-authoritive dns server as authoritive for
internet.aol.com which is where the first url is cnamed.
I need a dns expert to
I´m constantly seeing responses to queries for AOL servers which come
in from different IP addresses than the query was sent to.
Pete
anyone here having problems resolving americaonline.aol.com with spoof
protection enabled on their dns servers? It appears AOL via a series of
cnames is
Just for everyone's information, the issue I originally mentioned has been
fixed, there was a weird NS entry loop in the aol dns but it's been
corrected and seems to function normally now (for IPv4 anyway, don't know
about that 4/6 issue someone mentioned).
One of the guys from AOL reads the
i don't know who aol is going to be able to send responses to who won't
apply those same restrictions.
NAT or content switch are the terms that come to mind.
Pete
dig www.aol.com.
; DiG 8.3 www.aol.com.
;; res options: init recurs defnam dnsrch
;; res_nsend to server default: Operation timed out
I think that's your problem. It seems aol is not answering queries
at all, when to be correct they should actually be sending back
responses
