Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    TLD Forwarding to Dyndns is being blocked

    Scheduled Pinned Locked Moved NAT
    3 Posts 2 Posters 775 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • B
      bhunt
      last edited by

      Hi Everyone,

      I setup pfSense on my virtual host and I am extremely pleased with it aside from one issue, which is that my vpn.foo.com domain requests die at the firewall.  So the setup is this:

      vpn.foo.com forwards to xxx.dyndns.org which is configured to update with my external DHCP IP.

      This has worked in the past with my DD-WRT routers, but now, vpn.foo.com times out, but xxx.dyndns.org comes right through the firewall properly.

      Any ideas or insight would be greatly appreciated.  Thanks!

      1 Reply Last reply Reply Quote 0
      • johnpozJ
        johnpoz LAYER 8 Global Moderator
        last edited by

        well does your local name resolution think its authoritative for foo.com for some reason?  This is a common mistake made, so you setup foo.com with some dyndns provider and then sure why not lets use foo.com as my local domain in pfsense –- so pfsense.foo.com, now when you ask pfsense hey what about xxx.foo.com, he sends back no records for xxx.foo.com since I am the authoritative nameserver for foo.com why should I go ask anyone else about it.

        An intelligent man is sometimes forced to be drunk to spend time with his fools
        If you get confused: Listen to the Music Play
        Please don't Chat/PM me for help, unless mod related
        SG-4860 24.11 | Lab VMs 2.7.2, 24.11

        1 Reply Last reply Reply Quote 0
        • B
          bhunt
          last edited by

          johnpoz, thanks for the reply.

          I ended up resolving this issue by changing the NAT reflection from 'System Default' to 'Pure NAT'.

          1 Reply Last reply Reply Quote 0
          • First post
            Last post
          Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.