Today I opened 3 urls and surfed site with no problem. Then I could not open one new site and got this message ''DNS error occurred. Server cannot be found. The link may be broken'. esterdayya this site opened BUT I got the same message (DNS error occurred. Server cannot be found. The link may be broken'') when i I tried to navid gate beyond home page? Is this a settings problem?

The internet uses something called DNS. It is similar to a phonebook for the internet, except instead of referencing people to phone numbers, it references IP addresses to webpages.
This error means that someone has purposely removed Facebook and Youtube from the listings in that "book" If you are at a school or workplace, you probably won't be able to fix this without help from a system administrator.
If at home, my suggestion would be to try another DNS Server, or "book".
This webpage explains how to set up an alternative DNS Server
http://code.google.com/speed/public-dns/docs/using.html

Where did you see that error message? Other web site working?
Did you set DNS server to your router or your ISP's server IP address? I suggest you to use the internal IP address of your router as the default gateway and the DNS server setting on your computer if necessary. On your router, you can set to use ISP's DNS server if necessary. Usually you don't need to set anything on your router, it will detect it for you automatically. For some web sites, you may need to open some more port and have your ISP check all the settings on their site to make sure everything is working if you added the router recently.

hi r_raiche

1. Take a regular ethernet cable and plug it into the ethernet port of your computer

2. Plug the other end into ethernet port of the DWL-710

3. On your computer (assuming you have Windows XP Pro with the NON-classic start menu), go to Start > My Network Places

4. On the top left under "Network Tasks" click on "View Network Connections"

5. Right click on "Local Area Connection" and then down to "Properties"

6. A pop-up window with 3 tabs should come up. Under the "General" tab, there is a list of icons with checkmarks next to them. Highlight the "Internet Protocol TCP/IP" on and click the "Properties" button underneath

7. Tick "Obtain an IP address automatically" and "Obtain DNS server address automatically"

8. Click on "OK" then "OK" again

9. Open up Firefox (or IE) and type 192.168.0.30 into the URL field

10. Type in the default username and password

BACKUP YOUR SYSTEM

this has helped me in the past.. i hope it helps you out

Been troubled lately by that pesky DNS error? Notice that your PS3 can still browse the net, but not log in? Happen to be a Roadrunner customer? Happen to have any other ISP with a crummy DNS server? Well then read on...

The main issue turns out to be a Roadrunner (or any other ISP's) DNS problem. The fix is simple. When configuring your PS3 network (regardless of wired or wireless), use the manual option. If you use DHCP, leave address resolution at automatic BUT CHANGE THE DNS SERVER ENTRY TO MANUAL.

I replaced the Roadrunner (or any other ISP's) DNS entries with addresses from the Open DNS project which is a free, secure DNS server that anyone can use. It's safe, easy, and works.

The DNS addresses are:

208.67.222.222 or/and 208.67.220.220

Once replaced, you should have no problem logging in.

here is the url i got it from http://boardsus.playstation.com/t5/PlayStation-Network/Solution-for-your-DNS-error-80710102-problems-Works-for-all-ISP/m-p/42264211/message-uid/42264211

When a DNS server error occurs, your Playstation 3 will not be able to connect to your home network. This means you cannot take advantage of the many online features that the Playstation 3 has. There is no real reason why certain DNS server errors occur, but fixing them should be simple.

LINK to article for help!

Introduction
Your Web server thinks that your URL has been temporarily redirected to another URL. The client system is expected to immediately retry the alternate URL.
302 errors in the HTTP cycle
Any client (e.g. your Web browser or our CheckUpDown robot) goes through the following cycle when it communicates with your Web server:

• Obtain an IP address from the IP name of your site (your site URL without the leading 'http://'). This lookup (conversion of IP name to IP address) is provided by domain name servers (DNSs).
• Open an IP socket connection to that IP address.
• Write an HTTP data stream through that socket.
• Receive an HTTP data stream back from your Web server in response. This data stream contains status codes whose values are determined by the HTTP protocol. Parse this data stream for status codes and other useful information.

This error occurs in the final step above when the client receives an HTTP status code that it recognises as '302'.
Resolving 302 errors - general
The 302 response from your Web server should always include an alternative URL to which redirection should occur. If it does, a Web browser will immediately retry the alternative URL. So you never actually see a 302 error in a Web browser, unless perhaps you have a corrupt redirection chain e.g. URL A redirects to URL B which in turn redirects back to URL A. If your client is not a Web browser, it should behave in the same way as a Web browser i.e. immediately retry the alternative URL.
If the Web server does not return an alternative URL with the 302 response, then either the Web server sofware itself is defective or your Webmaster has not set up the URL redirection correctly.
Resolving 302 errors - CheckUpDown
Redirection of URLs may occur for low-level URLs (specific URLs within your Web site such as www.isp.com/products/index.html) when you reorganise your web site, but is relatively uncommon for the top-level URLs (such as www.isp.com) which most CheckUpDown users ask us to check. So this error should be fairly infrequent.
The 302 response from your Web server should always include an alternative URL to which redirection should occur. If it does, CheckUpDown automatically tries the alternative URL. This in turn may possibly lead to another redirection which CheckUpDown then tries. This continues for a maximum of 5 redirections. As soon as 5 redirections have occurred, CheckUpDown gives up and reports the 302 error for your account. So you should only ever see the 302 error if 1) your Web server gives no alternative URL on the 302 response or 2) the number of redirections exceeds 5. This second condition should be fairly unlikely - and may indicate a recursive pattern e.g. URL A redirects to URL B which in turn redirects back to URL A.
You first need to check that the IP name we use to check for your account is accurate. If you or your ISP have configured something so that any access using this name should now be redirected to another name, then you need to update your CheckUpDown account to start using the new name.
If you believe that the IP name we use is exact (should not be redirected), please try accessing the current URL using a Web browser. Note carefully which URL actually gets displayed, because your browser may silently switch to a substitute URL if it receives an 302 message from your Web server. If you see any evidence of a new URL, try accessing that directly from your browser. If this works (you see your Web site as expected), then this new URL is what you may need to update on your CheckUpDwon account. If this is a temporary redirection, then you may also need to reinstate the original IP name at a later date when the redirection is no longer effective.
If none of the above help, we can analyse the underlying HTTP data streams we receive from your Web server. These can provide additional information about the new URL(s) which your Web server thinks we should be accessing. Before doing this, we prefer you to identify any deliberate changes on your side, liaising with your ISP if needs be.
302 errors should occur infrequently, because top-level URLs do not change often. If they do change, then this is typically because a redirection URL is being suggested. This pervasive change is unlikely to occur by accident, so most often we can resolve this error by updating our system records for your account following a deliberate change of URL on your part, whether this change is temporary or permanent.

Hi,I am hosting with this http://www.tucktail.com/ site,still now there is no problem for me,you too also try this one,All the best.

Your Web server thinks that the HTTP data stream sent by the client (e.g. your Web browser or our CheckUpDown robot) was correct, but access to the URL resource requires user authentication which 1) has not yet been provided or 2) which has been provided but failed authorization tests. This is commonly known as "HTTP Basic Authentication". The actual authentication request expected from the client is defined in the HTTP protocol as the WWW-Authenticate header field.
Generally this error message means you need to log on (enter a valid user ID and password) somewhere first. If you have just entered these and then immediately see a 401 error, it means that one or both of your user ID and password were invalid for whatever reason (entered incorrectly, user ID suspended etc.).
401 errors in the HTTP cycle
Any client (e.g. your Web browser or our CheckUpDown robot) goes through the following cycle:
Obtain an IP address from the IP name of your site (your site URL without the leading 'http://'). This lookup (conversion of IP name to IP address) is provided by domain name servers (DNSs).
Open an IP socket connection to that IP address.
Write an HTTP data stream through that socket.
Receive an HTTP data stream back from your Web server in response. This data stream contains status codes whose values are determined by the HTTP protocol. Parse this data stream for status codes and other useful information.
This error occurs in the final step above when the client receives an HTTP status code it recognises as '401'.
Fixing 401 errors - general
Each Web Server manages user authentication in its own way. A security officer (e.g. a Web Master) at the site typically decides which users are allowed to access the URL. This person then uses Web server software to set up those users and their passwords. So if you need to access the URL (or you forgot your user ID or password), only the security officer at that site can help you. Refer any security issues direct to them.
If you think that the URL Web page *should* be accessible to all and sundry on the Internet, then a 401 message indicates a deeper problem. The first thing you can do is check your URL via a Web browser. This browser should be running on a computer to which you have never previously identified yourself in any way, and you should avoid authentication (passwords etc.) that you have used previously. Ideally all this should be done over a completely different Internet connection to any you have used before (e.g. a different ISP dial-up connection). In short, you are trying to get the same behaviour a total stranger would get if they surfed the Internet to your Web page.
If this type of browser check indicates no authority problems, then it is possible that your Web server (or surrounding systems) have been configured to disallow certain patterns of HTTP traffic. In other words, HTTP communication from a well-known Web browser is allowed, but automated communication from other systems is rejected with an 401 error code. This is unusual, but may indicate a very defensive security policy around your Web server.
Fixing 401 errors - CheckUpDown
When you set up your CheckUpDown account, you may optionally provide two items 2. Web Site User ID and 3. Web Site Password. You should provide these only if your site uses HTTP Basic Authentication. If you provide them, the CheckUpDown robot always uses them. This will result in a 401 error if in fact your site does not use this authentication. Conversely, if you do not provide them and your site does use this authentication, you also get a 401 error.
If however your URL is open to all comers, then an 401 message should not appear. Because it indicates a fundamental authority problem, we can only resolve this by negotiation with the personnel responsible for security on and around your Web site. These discussions unfortunately may take some time, but can often be amicably resolved.
Alternatively or the other way around is :

open the XP hosts file, and do a manual insert there.
The hosts file is located at: C:\WINDOWS\system32\drivers\etc
The entry is: 192.168.0.1 www.routerlogin.net
You might need to flush your DNS records at this point, or simply restart your computer.
And then use the following URL to access the admin page:
http://www.routerlogin.net/setup.cgi?next_file=start.htm
***Here is another solution to the problem, which is a fairly straight-forward way to disable the annoying wizard.
Type in your browser:
http://www.routerlogin.com/CA_HiddenPage.htm
Select: Disable Configuration Assistant, and click on Apply.
You can re-enable it by navigating to http://192.168.0.1/CA_HiddenPage.htm (where 192.168.0.1 is your router’s IP address)

Go into the Tools area, select Options, then in the Privacy section, turn off DNS pre-fetching. Worked well for me.