Discussion Locked

Cisco 806 won't resolve DNS

0 helpful
4 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I've got a Cisco 806 Broadband Router running IOS 12.2 with the Firewall Feature set. The router is connected to DSL line.

Here is the problem. I have connectivity out to the Net and can ping IP addresses, but the router can't (won't?) resolve domain names.

As you will see from my configuration below (shortened to get under the TR character limit, but the important stuff is there), nameservers are defined. However, when I try to ping a FQDN, it references the DNS server, and it seems to be submitting the resolution request to the DNS. In spite of this, it can't resolve the name. I get an error saying the domain was not found or the protocol is not running.

I've turned on debug for DNS, but it only tells me that the request is timing out.

From what I can tell, the configuration is correct. Unfortunately I cannot post the whole thing here because of the T/R character limit, but the access list I am using is below. In any event, I have tried removing the access-list entirelyand it has not changed anything.

I know it is not the line or the DSL gateway, because if I connect a Netgear DSL router, everything is just fine.

Anybody have any ideas?

access-list 111 permit tcp any any eq www
access-list 111 permit icmp any any administratively-prohibited
access-list 111 permit icmp any any echo
access-list 111 permit icmp any any echo-reply
access-list 111 permit icmp any any packet-too-big
access-list 111 permit icmp any any time-exceeded
access-list 111 permit icmp any any traceroute
access-list 111 permit icmp any any unreachable
access-list 111 permit udp any eq bootps any eq bootpc
access-list 111 permit udp any eq bootps any eq bootps
access-list 111 permit udp any eq domain any
access-list 111 permit esp any any
access-list 111 permit udp any any eq isakmp
access-list 111 deny ip any any

4 replies

by maxwell edison

This is a blindfolded, shot-in-the-dark at a moving target, but since you're using DNS, would disabling DHCP in the router possibly resolve the problem?

Maxwell

by joemoran

I actually tried disabling the router DHCP server, but it didn't help. The WAN interface need to get assigned it's IP from the gateway via DHCP, though. If I give it a static (the one it would get via DHCP anyway) then I can't get out, period. Thanks though.

by gjohnson

Try

access-list 111 permitTCP any eq domain any

Depending on the device you talk to, you can use either UDP or TCP or both. Can't figure why it won't work without the access list altogether though?? Have you tried reinstalling the IOS image with a freshly downloaded version to ensure that you don't have a corrupted IOS image?

Geo

by joemoran

OK, now this is weird. I sorta figured out is going on. As I suspected, the config is OK. Right after I power up the router, DNS won't work. However, if I unplug the WAN port and then plug it right back in, it works like a champ.

Makes no senseto me, except that I possibly have a bad router. Thoughts?

This discussion is closed to new replies.