The rule in Cisco redirected does not work in a different network subnet, how to solve?

Question

System administration

Good afternoon,
here is my port forwarding:

ip nat inside source static tcp 172.16.1.5 53 xxx.xxx.xxx.xxx 53 extendable ip
nat inside source static udp 172.16.1.5 53 xxx.xxx.xxx.xxx 53 extendable
xxx.xxx.xxx 80 extendable

network #1 172.16.1.0

interface GigabitEthernet0/0
description LAN
mac-address 68b5.99b7.bd85
ip address 172.16.1.1 255.255.0.0
ip nat inside
ip virtual-reassembly in
duplex auto
speed 100

WAN xxx.xxx.xxx.xxx

interface GigabitEthernet0/1
mac-address f80f.41f2.f81b
no ip address
ip nat outside
ip virtual-reassembly in
duplex auto
speed auto
pppoe enable group global
pppoe-client dial-pool-number 1

network #2 192.168.1.0

interface GigabitEthernet0/2
ip address 192.168.1.112 255.255.255.0
ip mtu 1492
ip nat inside
ip virtual-reassembly in
duplex full
speed 100

DNS does not work between networks No. 1 and No. 2 or is it wrong with the rules?
Hosts 172.16.1.10

Answer 1

Set the no-payload flag on DNS forwarding, otherwise the tsiska crawls into DNS packets and replaces addresses when issuing. We once had private addresses from 192.168 in the public DNS cache, it was fun to joke around.
As for "does not work" - do packets from 192.168.1.0 go to 172.16.1.0 at all?

Answer 2

Do you have both networks on the same router?