Win2003 DNS cache lookup errors hotfix

  • Thread starter Thread starter Travis
  • Start date Start date
T

Travis

We have a server 2003 box that intermittantly does not
resolve names properly. This is a known issue, KB ID:
830905 - However, MS doesn't seem to make it very easy to
aquire the hotfix mentioned.

Do they expect everyone to pay $99 for a support call to
make this thing work?
 
In
Travis said:
We have a server 2003 box that intermittantly does not
resolve names properly. This is a known issue, KB ID:
830905 - However, MS doesn't seem to make it very easy to
aquire the hotfix mentioned.

Do they expect everyone to pay $99 for a support call to
make this thing work?
Click to expand...

Not if the hotfix is what it needs.
 
-----Original Message-----
In Travis <[email protected]> posted a question
Then Kevin replied below:

Not if the hotfix is what it needs.

--
Best regards,
Kevin D4 Dad Goodknecht Sr. [MVP]
Hope This Helps
============================
--
Click to expand...
So how am I supposed to get the hotfix?
I don't see any method of contacting them, phone, email,
etc. that doesn't first prompt me for my credit card.
 
In (e-mail address removed) <[email protected]>
posted a question
Then Kevin replied below:
So how am I supposed to get the hotfix?
I don't see any method of contacting them, phone, email,
etc. that doesn't first prompt me for my credit card.
Click to expand...
That, I suppose is a catch 22, you give them the credit card if the hotfix
fixes it then the card isn't charged. If the hotfix does not fix it or there
is some other problem that is covered in the KB then you pay.
If the problem is proven to be an unknown bug that requires a hotfix, it is
on them.
That is why you should be very sure of the problem you have before you call.

What exactly are you symptoms?

Are you behind a firewall?
If you are that is a known problem that is really the fault of the
firewall's non-support of EDNS0 extensions which some firewalls reject the
packets. If a firmware update is not available for your firewall, you have
to turn off EDNS0 support in Win2k3.
828731 - An External DNS Query May Cause an Error Message in Windows Server
2003
http://support.microsoft.com/default.aspx?scid=kb;en-us;828731
 
Thanks for the response Kevin,
I'm aware of the Extended DNS problem - which our cisco
PIX does have problems with. But even after turning off
EDNS the problems continued. It seems to just be certain
domains, (like AOL - as listed in the EDNS KB article) -
and rr.com (I think that's RoadRunner?) Anyway, I made
the reg adjustment with no luck - so I decided it must be
this other problem.... I suppose I could have done
something wrong, but turning off EDNS wasn't too
complicated, so I doubt it.
Thanks,
Travis-
-----Original Message-----
In (e-mail address removed)
Click to expand...
 
In (e-mail address removed) <[email protected]>
posted a question
Then Kevin replied below:
Thanks for the response Kevin,
I'm aware of the Extended DNS problem - which our cisco
PIX does have problems with. But even after turning off
EDNS the problems continued. It seems to just be certain
domains, (like AOL - as listed in the EDNS KB article) -
and rr.com (I think that's RoadRunner?) Anyway, I made
the reg adjustment with no luck -
Click to expand...

From the article you posted it says that clearing the cache fixes the
problem have you tried that? The article also states that this only affect
some hosts, not domains.
The fact that you are using a PIX firewall makes it very suspicious. I'm
just trying to save you a call, this is a very common question posted to
this group.
This is mot a registry adjustment it is a command using dnscmd which is not
installed by default (dnscmd) you must install the server support tools from
the server CD.
 
Back
Top