What should a NAT router be passing to the clients as DNS?

[SunnyD]

I'm trying to figure this out. For the life of my, I just don't get it. I have a Microsoft MN-700 router, it works, don't knock it.

However, my internet is through earthlink, and I seem to constantly be having issues with their DNS servers, mostly when trying to access my hosted domain (hosted elsewhere mind you). Every once in a while, their name servers seem to forget that my domain even exists. I can do a nslookup on it, and it will just plain fail. If I nslookup from any other DNS, life is good.

Now the question I have is that in looking at the settings, I've noticed that DHCP from my router is assigning the DNS to the clients as 192.168.20.1 - itself. It's not pushing any valid DNS IP address. Is this supposed to happen this way? Shouldn't I be seeing my ISP's DNS entries on the clients? I am so confused.

 

[spidey07]

thats normal for SOHO gear.

 

[Nothinman]

If the router is doing DNS caching it should provide it's own IP, if not it should provide those of the ISP.

 

[Rafael]

I don't know very much about your router. And I got a Linksys WRT54GS.
But in my router there's an option called DNSMasq for DHCP, and when I set it up, it attributes the IP of my router as the DNS server.
I think there is an option on your router that disable this, and the router will give your ISP DNS server, or whatever DNS server you set on your router.
About the problems to access your hosted domain, even if you set a different DNS server on your computer or on your router this happens?
I think you can set up other DNS server than your ISP DNS servers, as long as they are public DNS servers.

 

[RebateMonger]

With most operating systems, you can manually set whatever DNS server(s) you like on your client computers.

 

[Nothinman]

With most operating systems, you can manually set whatever DNS server(s) you like on your client computers.

Which pretty much defeats the purpose of using DHCP.