NAT and DNS HELP

Forum|Forum|6 years ago
October 25, 2019
8 replies
7073 views

Hi all,

I have a FG80C installed and running. My ISP provides me via a antena connection my internet connection. I have my WAN1 configured using DHCP and it gets assigned a WAN address of 192.168.20.x which then in turn gives me an external IP of 185.x.x.x.x.

I'm running a server which I have configured on my DMZ 192.168.10.x and I use virtual IPs to forward the traffic this this server on the DMZ. I have policies created too.

On the control panel on my domain registrant I have a glue record pointing the name servers to my server, myserver.com on the DMZ where I'm running a unix hosting control panel and bind. Externally everything works fine. The problem is internally on my LAN. I can't resolve any of the myserver.com addresses. As they are all pointing to my external IP 185.x.x.x.

What do I need to setup to be able to resolve those external "mysever.com" addresses on my internal LAN?

Dave_Hall

New Member

Based on your description of the problem and if we are talking about one or a handful of FQDNs, you could use dnstranslation, which is explained here or here.

e.g.

config firewall dnstranslation edit <index_int> set src <185.x.x.x.x> set dst <192.168.10.x> set netmask <address_ipv4mask>

end

Gypsy_DaveAuthor

New Member

Strangely when using the CLI commands mentioned I receive a reply from nslookup on the LAN computer for resolving mydomain.com to 192.168.10.174 ? The server which is hosting that domain has only configured the address 192.168.10.2 (and the external 185.x.x.x. also). There is no 192.168.10.174 anywhere on my lan? Where is it getting that from?

config firewall dnstranslation edit <index_int> set src <185.x.x.x.x> set dst <192.168.10.x> set netmask <address_ipv4mask> end

Dave_Hall

New Member

Flush the DNS server cache (e.g. ipconfig /fushdns) on the computer and make sure it has the correct DNS server IPs assigned to it (from the DHCP server). If the computer is receiving the proper DNS server IP info, check the local DNS records on the DNS server (service) are correct and/or DNS forwarders configured/set to point to a local address in your internal LAN.

Mind you, if you already have a domain server running a DNS service, you may as will configure local DNS records for the myserver.com addresses.

Sign up

Login with SSO

Login to the community

Login with SSO