cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Highlighted
New Contributor

NetVanta 3140 DNS Resolution Issue

First time setting up one of these and I'm running into an issue where DNS resolution will work for a while, then stop.  Router was setup using webui.  I think it has something to do with my DHCP pool settings?  If I enter the DNS IPs under DHCP pool -> Optional Settings name resolution will work for a short period of time with the router assigning ISP DNS to clients, but after 10-20 minutes it stops working.  Everything else works fine if I statically assign DNS on clients but clearly there's a problem here.

My config file is attached, with some identifying material scrubbed.

0 Kudos
Reply
3 Replies
Highlighted
Honored Contributor
Honored Contributor

Re: NetVanta 3140 DNS Resolution Issue

While you have a name server specified for the router itself, you aren't providing DNS server information to your DHCP pools. Do the following (assuming that you want the pools to use the same name servers as in your configuration for the device itself):

!

ip dhcp pool "LAN"

  network 192.168.1.0 255.255.255.0

  default-router 192.168.1.1

  dns-server 66.28.0.45 66.28.0.61

!

You'll need to have the DHCP devices release and renew their connections to pick up the change.

0 Kudos
Reply
Highlighted
New Contributor

Re: NetVanta 3140 DNS Resolution Issue

Huh, that's what I figured, but when I would set DNS in the GUI under DHCP Server Pool "LAN" -> Optional Settings, clients could resolve DNS for a short period of time, then they would stop, and when I checked back at DNS under "optional settings" the DNS entries would be blanked out.  Is this a bug in the GUI?  Or am I missing something?

0 Kudos
Reply
Highlighted
Honored Contributor
Honored Contributor

Re: NetVanta 3140 DNS Resolution Issue

It could be a bug, but this is unlikely as it would affect others and there would be reports of it. Entering nameservers into DHCP pools is a very common configuration and such a bug would bring a lot of attention.

Perhaps the configuration was not saved? I would try to enter it into the CLI, then write to memory and reboot to see if it sticks.

It could also be malicious. Looking at your configuration, telnet access is enabled with default password. I'd recommend disabling telnet completely and also make sure to remove the "admin" user from the default configuration.

0 Kudos
Reply