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

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

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: W2K3 Enterprise R2 servers not accessible
    ... "Are you able to resolve their IP addresses using ... I have gone to a DOS prompt on my server in Domain B. I type nslookup and ... it now brings back the DNS server information. ...
    (microsoft.public.windows.server.dns)
  • Re: troubleshooting DNS
    ... Can your DNS server Ping out when it can't resolve names? ... If the forwarders, recursion, and TCP/IP configuration are all ... Can your DNS server ping everywhere it needs to go by IP ... itself and ONLY itself as DNS server in it's IP configuration settings. ...
    (microsoft.public.windows.server.dns)
  • Re: RWW Issue
    ... can resolve this issue: ... | I remote desktop into it. ... | desktop is enabled to allow remote connections. ... | DNS server failed the update request. ...
    (microsoft.public.windows.server.sbs)
  • Re: DNS forwarders not working
    ... >>> So my solution was to set up DNS forwarders on my DNS server to try ... >>> resolve the third party queries using a forwarder to their server. ... Their DNS server will to resolve Internet FOR YOU? ... > get EITHER internet or 3rd party working but not both a the same time. ...
    (microsoft.public.win2000.dns)
  • Re: recursion
    ... his cache and asks the forwarders. ... Why would I disable recursion at the Advanced tab? ... disabling recursion on a DNS server happens when DNS clients are to be limited to resolving names authoritatively managed on a specific server. ... this is the case when a DNS server has only DNS names data for an internal network or when the DNS server is incapable of resolving external DNS names and clients are expected to retry another DNS server to resolve these names. ...
    (microsoft.public.windows.server.dns)