joltdudeuc

iTrader: (6)

Some site work, others don't.

Modem issue?

I just replaced my router, same DNS issues (but got rid of the damn IP address issues I was having)

DSL Modem is doing the PPPoE and the router is just taking it DHCP.

I'm thinking I might try having the Router do the PPPoE.


Any thoughts?

Thanks!

-Gagan

ldivinag

iTrader: (3)

did you register the new router with your DSL (i assume) provider?

evsoul

iTrader: (1)

only the gateway needs to be set to PPPoE...

Does this same thing happen on all computers on the connection? Or do you only have the one hooked up?

Are you connected wireless or wired?

mcowger

iTrader: (8)

Is your MTU set right - PPPoE connections tend to have a lower MTU (around 1260 ish)

joltdudeuc

iTrader: (6)

Not sure if I have to do this. I think only cable users would do this right?

joltdudeuc

iTrader: (6)

I can either have the modem do it or have the router do it. Right now the modem is doing it. Seems like its getting better so I think it was just that it needs some time to gather DNS data?

Other thing I did was set the DNS server to 192.168.0.1 (modem address). Router address is set to 192.168.1.1

joltdudeuc

iTrader: (6)

MTU is 1500 (default)

Looks like I can access dlink.com now. Some other sites are available now as well.

I'm wired to the router.

Onizuka

iTrader: (17)

Do not set your DNS to the modem address.

The DNS should be the DNS from your service provider. This may be the reason you're having strange internet issues since your computers that are trying to access the internet cannot resolve host names.

joltdudeuc

iTrader: (6)

Originally it was set to routers IP.

I'll go into the modem and see if I can find out the DNS server IPs from there.

mattsn0w

iTrader: (23)

try setting your DNS server to 68.183.193.243. this is my own personal DNS server I run.
I'm willing to bet your router's DNS resolver is broken or your ISP is having DNS issues. otherwise it's the POS dlink.

verc

iTrader: (12)

Gagan, can you nslookup the sites that you cannot access? If not what's the error the CLI gives?

Follow mattsn0w's advice actually - your DNS server can be whatever the F you want it to be really.