Question Locked

Cisco router does not pass DNS.

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

Hi Cisco 2621 does not allow DNS resolution from the outside and for the life of me cannot figure out why. I also tried to implement ip subnet-zero and ip classless but the command, though entered successfully, it did not show up in the config. Any input would be welcome.

Here is the nslookup from outside and also my run config.

--- SNIP ---

c:\nslookup www.mysite.com 12.34.67.98
*** Can't find server name for address 12.34.67.98: Server failed
Server: UnKnown
Address: 12.34.67.98

DNS request timed out.
timeout was 2 seconds.

--- END SNIP ---

Does the router need to be rebooted after the change? Any other ideas?

----------- SNIP -----------
Building configuration...

Current configuration : 3165 bytes
!
version 12.4
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname router-wp
!
boot-start-marker
boot-end-marker
!
enable secret 5 xxxxxxxxxxxxxxxxxxxxxxxx
!
no aaa new-model
no network-clock-participate slot 1
no network-clock-participate wic 0
ip cef
!
!
no ip dhcp use vrf connected
ip dhcp excluded-address 192.168.1.1 192.168.1.100
ip dhcp pool webport
network 192.168.1.0 255.255.255.0
dns-server 12.34.67.13 12.34.67.15
domain-name webport.ca
default-router 192.168.1.1
!
!
no ip domain lookup
ip name-server 12.34.67.13
ip name-server 12.34.67.15
ip name-server 192.168.1.105
ip name-server 192.168.1.99
ip auth-proxy max-nodata-conns 3
ip admission max-nodata-conns 3
!
!
interface FastEthernet0/0
description Connection to WAN
ip address 12.34.67.98 255.255.252.0 secondary
ip address 12.34.67.99 255.255.252.0 secondary
ip address 12.34.67.100 255.255.252.0 secondary
ip address 12.34.67.101 255.255.252.0 secondary
ip address 12.34.67.97 255.255.252.0
ip access-group FILTER-WAN-IN in
ip access-group FILTER-WAN-OUT out
ip nat outside
ip virtual-reassembly
duplex auto
speed auto
!
interface FastEthernet0/1
description Connection to LAN
ip address 192.168.1.1 255.255.255.0
ip nat inside
ip virtual-reassembly
duplex auto
speed auto
!
!
router rip
version 2
network 12.0.0.0
network 192.168.1.0
no auto-summary
ip forward-protocol nd
ip route 0.0.0.0 0.0.0.0 12.34.67.1
!
!
no ip http server
no ip http secure-server
ip nat inside source list 1 interface FastEthernet0/0 overload
ip nat inside source static udp 192.168.1.105 53 12.34.67.98 53 extendable
ip nat inside source static 192.168.1.105 12.34.67.98 extendable
ip nat inside source static 192.168.1.99 12.34.67.99 extendable
ip nat inside source static 192.168.1.100 12.34.67.100 extendable
!
ip access-list extended FILTER-LAN-IN
permit ip any any
permit tcp any host 12.34.67.97 eq pop3
permit tcp any host 12.34.67.97 eq smtp
permit tcp any host 12.34.67.97 eq ftp
permit tcp any host 12.34.67.97 eq ftp-data
permit tcp any host 12.34.67.97 eq 443
permit tcp any host 12.34.67.97 eq 22
permit udp any host 12.34.67.97 eq 22
permit udp any host 12.34.67.97 eq domain
permit udp any host 12.34.67.97 eq 23
permit tcp any host 12.34.67.97 eq telnet
permit udp any host 12.34.67.97 eq 25
permit udp any host 12.34.67.97 eq 50
permit tcp any host 12.34.67.97 eq 50
permit tcp any host 12.34.67.97 eq www
permit udp any host 12.34.67.97 eq 80
permit udp any host 12.34.67.97 eq 110
permit udp any host 12.34.67.97 eq 220
permit tcp any host 12.34.67.97 eq 220
permit udp any host 12.34.67.97 eq 443
permit udp any host 12.34.67.97 eq 3389
permit tcp any host 12.34.67.97 eq 3389
ip access-list extended FILTER-LAN-OUT
permit ip any any
!
access-list 1 permit 192.168.1.0 0.0.0.255
access-list 1 permit 12.34.67.0 0.0.0.255
access-list 1 permit any
!
!
control-plane
!
!
line con 0
line aux 0
line vty 0 4
password xxxxxxxx
login
!
!
end

router-wp#

12 replies

by cmiller5400

In the ACL you do not allow port 53 traffic (domain) inbound for TCP. Add the following statement to your ACL

permit tcp any host 12.34.67.97 eq domain

by peconet tietokoneet

You will need to re-boot the router/switch for it to save the new configuration, or do a "save and restart" in the settings of the router in question.
Hope all goes well.

by gary

The DNS is still not able to be queried. In the ACL, the IP is that of the inside interface fa0/1. Should the IP be that of the server or the interface?

by peconet tietokoneet

From the router in question and do a reset on the router then re-apply the settings again. Hopefully this should get it working again.

by symon.l

Depending on what cisco is it you shouldnt need to reboot to be honest need to ask what type of router before ya give duff information.

a simple "write memory" will do just fine.

by gary

I also noticed that a web application I have does not allow for checking of port 110 on that server.

by symon.l

Your ACL is not working because you haven't applied it anywhere. You have some statements in the FastEthernet 0/0 interface but these are not doing anything as the access lists they refer to do not exist in your config.

ip access-group FILTER-WAN-IN in
ip access-group FILTER-WAN-OUT out

These 2 ACLs do not exist, what exist are FILTER-LAN-IN and FILTER-LAN-OUT and ACL 1. Also these ACLs are allowing all traffic anyway, no point them being there (maybe this is the reason they are not applied).

I can see a few more errors with your config, in rip configuration I am unsure as to why you have declared a class A network. I think you need to change "network 12.0.0.0" to "network 12.36.64.0 255.255.252.0"

You seem to be confused as to what mask you are using for this network because in ACL 1 it defines it as a /24 class C network. If this is the case then the above statement needs to be changed to "network 12.36.67.0".

I am also a bit confused as to why you have all the scondary ip addresses configured on the FastEthernet 0/0 interface. The way they are configured they all belong to the same network and I would have thought this would have given an error and not let the commands be installed.

by gary

Thank you for your reply. My configuration is as follows:

1. The ACL's are in place to be implemented later on. The names are changed so that I can have it all wide open for testing.

2. The outside network is over a cable internet provider. My gateway is a /22 address so that is why I put the /22 in the ACL and RIP config.

3. The secondary addresses are tied to the box because I am given part of a /22 network and it did not seem to work by implementing a .248. Maybe my config was wrong but the 255.255.252.0 is the only way I was able to get it working.

I have multiple public IP's and have a couple of different servers (ie. one Windows and one BSD). I want one public address to be hard coded to one internal address without the need for Router on a Stick,VLAN, etc. From what I understand, NAT can handle the forwarding.

For the time being, I am more than willing to have a wide open config with no ACL in place as long as all ports/protocols are passed to each respective box.

Does this make sense or do I have the config all wrong and am going about it a backwards way?

by gary

do a complete write erase then paste the settings back in the router to start from scratch or do you mean just put the entries in a second time after a reboot?

by symon.l

Gary i was repying to Peconet Tietokoneet, not yourself as he was suggesting you would need to save / restart the cisco on each change which with that version you dont need to :)

This discussion is closed to new replies.