Cannot access site in linux

[IronFox]

I dual boot with fedora and windows and for some reason under linux I cant get to animesuki at all. Whats up?

[SeijiSensei]

What happens if you click here?

If that works, but this doesn't, you have a DNS problem. What's the contents of /etc/resolv.conf?

[IronFox]

When I type in the actual ip address, i get on fine, type in animesuki.com and the farthest i get is "Connecting ...".

# generated by NetworkManager, do not edit!

domain domain.actdsltmp

search domain.actdsltmp

nameserver 192.168.0.1
nameserver 205.171.3.65

[SeijiSensei]

Well, your upstream DNS server knows how to resolve animesuki.com, both with and without "www." as a prefix:

[somebody@somewhere bin]# host www.animesuki.com 205.171.3.65
Using domain server:
Name: 205.171.3.65
Address: 205.171.3.65#53
Aliases:

www.animesuki.com has address 69.42.221.126

[somebody@somewhere bin]# host animesuki.com 205.171.3.65
Using domain server:
Name: 205.171.3.65
Address: 205.171.3.65#53
Aliases:

animesuki.com has address 69.42.221.126

What host is 192.168.0.1? I'm guessing it's the router. Try removing the "nameserver 192.168.0.1" line from /etc/resolv.conf and see if that fixes the problem.

It sounds to me like the router itself isn't configured to determine your upstream DNS server correctly. If you browse the router's configuration through its web interface see if 205.171.3.165 is listed as the "primary" DNS server; if it isn't, "make it so." Then you need to run "ipconfig /flushdns" on any Windows machines behind the router, or better yet, reboot them.

Fixing the router's DNS entries is a long-term solution. For now, deleting the line in /etc/resolv.conf should fix your immediate problem.

Remember that consumer devices like routers expect to see Windows, or perhaps OS X, behind them. Since you can't run the auto-configuration CD, you'll often need to adjust the router manually to make sure it has the right configuration.

Now if 192.168.0.1 is some other host on your network that's running a DNS server like ISC BIND, that's a whole other kettle of fish as they say. Then we need to start talking about what types of traffic you allow to and from the Internet, and how that DNS server is configured.

[IronFox]

192.168.0.1 is my modem and 192.168.1.1 is my router.

Removing that line worked!

[SeijiSensei]

Well there's no way your modem at 192.168.0.1 is going to be able to resolve names, so that answers one question. The next question is how that address appeared in /etc/resolv.conf. If the computer gets its information using DHCP from the router, then the router is misconfigured to give out the 192.168.0.1 address as a valid DNS server. It probably should be giving out its own address, or that upstream server address, or both. You should browse the DHCP configuration in the router and see what it thinks the DNS servers are and fix them if need be.

One other trick you can perform to keep the machine from altering the contents of /etc/resolv.conf at reboot is to make that file read-only. The easiest way is to open a terminal window and, as root, "chmod 0444 /etc/resolv.conf". Now if the DHCP client in the Linux box tries to overwrite your resolv.conf upon reboot, it won't be able to do so. You'll probably have to change this back to 0644 if you change ISPs since you might be needing a different DNS server after the switch.