How to point incoming traffic to internal web servers with internal DNS server

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

How to point incoming traffic to internal web servers with internal DNS server

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
How to point incoming traffic to internal web servers with internal DNS server
How to point incoming traffic to internal web servers with internal DNS server
2021-12-02 11:26:08
Model: TL-R470T+  
Hardware Version: V6
Firmware Version: 6.0.4 Build 20200313 Rel.32850

I have a simple query as 'how to point domain names to on-premise web-apps?'

Here's my setup: 

Internally my DNS server points all domain names properly to its respective apps/servers/ports. But I am not sure how to direct external traffic (outside LAN) to point to proper internal apps. 

 

<fixed-public-ipv4> points to <Modem> 

 

[A] Modem Configs: 

1. Modem IP 192.168.0.1 subnet:/24

2. Modem> Network > LAN > DHCP server > 

 Primary DNS server set to <192.168.0.2> (WS 2k19 DNS server)

 

3. Transmission > NAT 

random port for VPN (works fine) ponts to internal OpenVPN server 

nothing else.

therefore port 80 on <public-ipv4> gives not found error. (that's fine). 

 

[B] DNS Server configs: 

DNS server has several forwarding DNS for zones such as 

mysite1.myorg.local --> .0.31
mysite2.myorg.local --> .0.32
mysite3.myorg.local --> .0.33
 

also public domains

myorgsite.com --> .0.34
testing.myorgsite.com --> .0.35

etc. 
[C] A records of DNS from domain registrar points to <public-ipv4> of my modem.  

 

[D]Desired outcome:

The websites domain names reaches my modem but dont load the proper webserver/app from on-premise LAN. Although I have pointed my primarly DNS as internal local DNS server. 
I need myorgsite.com from outside query to load server/app from .0.34

What is missing? Do I need to add something in "tranmission" section? NAT, routing pages?

This seems simple and obvious but I do not have a how-to guide on it. 

Thank you 

 

 

  0      
  0      
#1
Options
2 Reply
Re:How to point incoming traffic to internal web servers with internal DNS server
2021-12-03 05:57:33

@johnycage 

I think put the internal DNS servers to the LAN > DNS

That's how I config for my Pi-hole. I set up my pi hoe DNS server to block ads. IP is 10.0.0.2, I set the 10.0.0.2 to be my LAN DNS. And I don't have many ads showing since then. 

 

  0  
  0  
#2
Options
Re:How to point incoming traffic to internal web servers with internal DNS server
2021-12-03 07:49:16

@John1234 Yes, that's pointed to internal DNS server. (ie. on LAN page DCHP server section I have mentioned primary DNS address as my WS2k19 server) & it's serving well for internal/ LAN network.

But for incoming traffic lets say mysite2.com reaches to <mypublic-ip> on modem but it stays there. Because I have not assigned it to go anywhere in "transmission > NAT " section. 

  0  
  0  
#3
Options

Information

Helpful: 0

Views: 709

Replies: 2