| Port forwarding to itself? Hello,
I have an inexpensive router that provides NAT and also provides DNS services.
Meaning any client connecting to it via DHCP or static IP can point to its address at 192.168.1.1 and receive answers to DNS queries.
When I do an IP config I get my DHCP assigned address, default gateway as 192.168.1.1 and Primary DNS as 192.168.1.1.
The router is assigned a static address from my ISP.
What I want to know is whether I can port foward port 53 UDP to its address at 192.168.1.1 so that I can connect to it from the wan as my DNS resolver. Basically I want to connect to it from the world by pointing to its IP address.
I know people port foward port 80 for web servers to machines on the subnet; however can a router allow a port forward to itself?
As in port foward UDP port 53 to 192.168.1.1? |
|
bdnhsv
join:2012-01-20
Huntsville, AL | I've never tried to forward something back to a router itself, but it might be possible. I'd guess you'd just have to give it a shot and find out. One thing I think might be a problem would be that if it works all your devices inside your network might not be able to resolve DNS queries because the replies from your ISP's DNS servers would forward back to .1 itself instead of the device that requested it inside your LAN. I'd be interested to hear your results if you decide to test it. |
|
| reply to rizwan602
said by rizwan602:What I want to know is whether I can port foward port 53 UDP to its address at 192.168.1.1 so that I can connect to it from the wan as my DNS resolver. i was in a similar situation before... i needed to get VPN connections through a hotel wifi network.. the idea was explained here:
»www.thegreenbow.com/vpn_faq.html#VPN24
it essentially required TCP 80 to be forwarded to UDP 500 and TCP 443 to be forwarded to UDP 4500..
and as i recall, it didn't work for my router. they have a disclaimer:
quote:
some router models do not provide the capability to reroute ports within itself and two routers might be needed
so if you try your idea and it doesn't work, perhaps using two routers may work. send 53 traffic to some internal router on your network, which in turn sends that traffic right back to the edge router on the same port. |
|
 wayjacPremium,MVM
join:2001-12-22
Indy
kudos:1 | reply to rizwan602
said by rizwan602:I have an inexpensive router that provides NAT and also provides DNS services. Meaning any client connecting to it via DHCP or static IP can point to its address at 192.168.1.1 and receive answers to DNS queries The router is not a dns server.....
All dns queries are forwarded to the dns ip's assigned by the isp
One exception to this is the router may provide lan dns lookups |
|
 billaustinthey call me Mr. BillPremium,MVM
join:2001-10-13
North Las Vegas, NV
kudos:2 | reply to rizwan602
Why would you want to go to so much effort when there are so many public DNS servers available?
If you're really serious about doing such a thing, you will need to setup your own DNS server on your LAN, and forward the appropriate ports to the server. |
|
| reply to rizwan602
i am going to go with what others have said...
why do you want to do this? what is your overall goal, here? |
|
| Here is the reason:
(Without naming a specific company) -- There is a very useful DNS service that provides me DNS level protection from phishing and malware web sites.
However I am only allowed access to the advanced DNS queries to this service from 1 ip address that I define within that DNS service's control panel.
If I set my router to this 1 ip address, lets say for example, that IP address is a.b.c.d then I can define a.b.c.d as "my ip address" inside the DNS service's control panel. When I do that, any DNS queries coming from a.b.c.d are given enhanced protected results. Other ip addresses such as e.f.g.h are NOT provided enhanced protected results.
Since I am on the go and I could be anywhere with an ip address that is NOT a.b.c.d then I can point to ip address a.b.c.d as my DNS resolver, which will port forward to 192.168.1.1 internally to the router, which will perform the DNS query (and seen from the DNS service as coming from a.b.c.d). It will receive the enhanced protected results from the DNS service and this DNS resolved response will be given back to me, even though I am on an ip address that is not a.b.c.d ...
This way my office computer can use a.b.c.d as the DNS resolver, and so can my laptop and other computers.
Rizwan
said by tomdlgns:i am going to go with what others have said...
why do you want to do this? what is your overall goal, here?
|
|
| are you trying to use your home WAN IP connection for DNS lookups when you are not at your house?
what is the service, OpenDNS?
keep in mind that if you are on someone elses network, sometimes the IP settings you use on your computer have no bearing on their network.
for example, if you connected your computer to my network, regardless what your settings are, my firewall blocks it and uses what i have configured. even if you put an invalid IP in the DNS server setting on your adapter, my firewall would ignore it and assign your device the DNS servers the rule tells it to use. |
|
bdnhsv
join:2012-01-20
Huntsville, AL | reply to rizwan602
Have you given any thought to setting up your own VPN server and then connecting remotely via that? I believe that would accomplish what you are wanting to do, as once you connected to your VPN server you would have an address inside your home network and your DNS queries would be handled just as if you were sitting in your house. |
|
