[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
nxdomain rfc2308 type 2, but authority is incorrect
In message <57AB8024.7010702 at ttec.com>, Joe Maimon writes:
> William Herrin wrote:
> > On Wed, Aug 10, 2016 at 2:05 PM, Joe Maimon <jmaimon at ttec.com> wrote:
> >> www.kissimmee.org
> >> Windows 2008 dns cannot resolve it.
> >> BIND can.
> > Hi Joe,
> > Does Windows 2008 like anything in the "hosting" TLD?
> > I notice that the nameresolve.com servers returning the CNAME to
> > kissimmee-fl.vts.hosting are also returning an SOA record for
> > "hosting" in the authority section which looks very strange to me.
> > Perhaps Windows is rejecting it as an invalid, possibly dangerous
> > response packet?
> > Regards,
> > Bill Herrin
> I think that provided SOA record is a "local" or "alternate" version and
> its existence is why the nxdomain response is being sent to the windows
> dns server that accepts it at face value (but does not appear to store
> it in cache, so this is not precisely cache poisoning)
Nameresovle.com's servers are returning answers that can be seen
as a cache poisioning attempt. They are NOT authorative for
".hosting" but have been configured as if they are. This is a big
NO NO. You don't configure youself as authoritative for a zone
that has not been delegated to you and in particular you don't
configure yourself as authoritative for "." or a TLD.
Windows 2008 is quite correct in rejecting this answer. Named would
as well except for the number of DNS hosters that do this sort of
garbage. Named just sees the CNAME and stops processing the message
> Here is another example, unrelated to the new TLD's
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742 INTERNET: marka at isc.org