Re: Can not resolve www.microsoft.com or www.yahoo.com

Hmm... I had to do any "ANY" type search via DNSStuff to get anything
returned. Same type of search works via nslookup against a fully patched
Windows 2003 DNS server. Considering that Microsoft recently issued
http://www.microsoft.com/technet/security/Bulletin/MS06-041.mspx, my next
step would be to setup a server in VM and then patch to the point of not
taking anything that updates the DNS binaries to see what happens.

"BooPee" <BooPee@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:A7E02ED6-CB79-49A4-B557-0866C070AA4C@xxxxxxxxxxxxxxxx
If I use BIND as DNS server it resolves www.lotus.com without any problem.
I
have also tryed with Netware DNS and it can also resolve. I where talking
to
a friend of mine at another company also running windows 2003 DNS server
and
he had the exact same problem, strange isn't it.

Any other out there having the same problem?


"neo [mvp outlook]" skrev:

Try cross checking with www.dnsstuff.com to see if records exists. In
this
case, I would say Lotus DNS provider {AT&T} isn't advertising a "www"
host
record or they are having issues. Try http://lotus.com.

"BooPee" <BooPee@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:539212FC-660A-4B4A-85E8-BAE5FDEDCF2E@xxxxxxxxxxxxxxxx
I have the same problem. I can not resolve www.lotus.com. I'v tested
changing
EDNS to 0 but the error still occurs.

"MecII" skrev:

Thank you , Thank you, Thank you!!!!!

The Microsoft workaround fixed the problem. I am not sure yet what is
preventing this from working, since my Cisco router is well above the
required software version stated that is needed to support the EDNS0
but
for
now at least we can resolve the two sites.

Thanks again!!

"neo [mvp outlook]" wrote:

Have you tried turning off EDNS0 support?
http://support.microsoft.com/kb/828731/en-us

"MecII" <MecII@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:8A0F818F-0D22-448F-B2DF-0F8AE1191CE8@xxxxxxxxxxxxxxxx
For some reason I am unable to resolve www.microsoft.com and
www.yahoo.com. I
can get to update.microsoft.com and just about any other website.

I have noticed that the one common componets of the two sites is
that
they
both use akadns.net, when I use someone elses network and do a
nslookup.
But
when I do an nslookup on my network, I get DNS timed out. I have
exteneded
the timeout to 60 seconds but that does not help.

If I set "server= 164.109.1.3" or uses the IP address of my ISP's
DNS
server
in nslookup then nslookup can resolve. (the ISP's DNS address is
the
same
address that is set in my forwarders on my DNS servers)

I have compared my root hints against other posting in the
newsgroup
and
the
are the same.

I am running Windows 2003 AD with 2 DNS servers and both server
use
forwarders to my ISP's DNS server. The "Do not use recursion for
this
domain"
is unchecked.

If anyone has an idea on why this is not working i would sure
appreciate
the
help.

Thanks








.

Relevant Pages

  • Re: Some DNS server names will not resolve using internal servers
    ... I have done all the nslookup commands. ... All of our external ISP DNS ... Is there a trace i could do on the DNS server to tell me what is happening? ...
    (microsoft.public.windows.server.dns)
  • Re: Group Policy and performance during logon procces from client
    ... Note that there are some problems regarding to the use of FW in the Windows XP machine, make sure that the FW are configured correctly with GPO. ... Assuming DNS AD Integrated Zone ... Do not place the ISP DNS server or any other DNS on the client or DNS Server NIC properties, ...
    (microsoft.public.windows.server.active_directory)
  • RE: In-place upgrade to AD 2003
    ... point to itself as the primary DNS server. ... During the upgrade, name the internal DNS name different from Public DNS ... When you set up a new Windows 2003 DC and transfer the FSMO roles, ...
    (microsoft.public.windows.server.migration)
  • Re: DNS cache poisoning?
    ... Windows DNS and thanks to numerous others for reporting. ... On Windows 2000 SP3 and above, the DNS server DOES protect against DNS ... BIND4 and BIND8 forwarders will not filter the cache poisoning attack to ...
    (Incidents)
  • Re: Windows 2003 SBS DNS timeouts
    ... I've got a Windows 2003 Small Business Server running a DNS server. ... Usually resolving addresses (e.g. by using a web browser or by using ... try a query using nslookup: ...
    (microsoft.public.windows.server.dns)
Loading