can you tell me step by step how to do that? i'm very new to this sort of thing.
Main Topics
Browse All Topicshow can i clear my dns?
i've already tried:
ipconfig /release
ipconfig /renew
ipconfig /cleardns
ipconfig /flushdns
etc, etc.
the site in question i'm trying to view, all of my friends can access it fine, yet i'm still resolving an old version of the site before the website has moved hosts.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
ipconfig /flushdns will clear your LOCAL computer's DNS cache, but if the DNS server that your computer is pointed to has an old dns record, then the old one will "come right back" so to speak. To resolve this you need to point your client to a DNS server that has the "new" DNS record... apparently your friends are already pointed to a DNS server with the new record.
go to the TCP/IP properties of your NIC (from control panel (network connections), rightclick your NIC, choose properties, choose TCP/IP, choose properties,,, then put in the IP address of another DNS server. Apparently the one you are pointed to now has old info.
from what you have explained, it sounds as though your ISP is blocking it,,,, there is nothing you can do about that other than switching ISPs. If you wait a while your ISP's DNS server will get the correct DNS info. Until then you can go directly to the new IP address. Ask your friends what the new IP is and you can access it by http://123.123.123.123 where 123.123.123.123 is the new address.
centax it's unusual for ISP's to block access to public DNS server in my expierience...
-First let me say, if you tell me the name of the site I could most probably tell you what to send to rogers to have them resolve the issue for everyone... Here what I would need....
1. Go to run and type CMD.. at the prompt type ipconfig /all (enter) -paste the results here for "DNS Servers . . . . . . . . . . . :"
2. List the domain name you cant reach...
Here is what I would do with that info;
At the prompt type...
nslookup -q=soa domainname.com. ns1.kumatech.ca.
-Look at the results....
nslookup -q=soa domainname.com. YOUR.DNS.IP FROM ROGERS.
-Look at the results.... do they differ.... they must!
Other good detail lookups ar
nslookup -q=a www.domainname.com. YOUR.DNS.IP FROM ROGERS.
-Look at the results....
nslookup -q=a www.domainname.com. ns1.kumatech.ca.
-Look at the results....
What's the point?
Nslookup can query for specific record types against specific servers... So DNS double start of authority and the typical invalid dns host records that result from this can be checked using your own pc running a version of windows NT...
Business Accounts
Answer for Membership
by: HousenetPosted on 2005-09-25 at 21:34:37ID: 14956406
Hello, go to TCP properties and specify another primary DNS server IP in you Nic properties.
-The DNS server's you are using to resolve the site do not have current zone information about that domain. Typically this occures when an ISP used to host the DNS zone, the SOA has changed and someone forgot to ask the old ISP to remove the DNS zone to remove the double SOA and likley invalid domain information.