Instant On - Wired

 View Only
  • 1.  OpenResolver open on WAN interfaces.

    Posted 22 days ago

    Hi everyone,

    I have a question regarding TCP/53 and UDP/53 being open to the Internet on the SG1004 4G, version 3.4.1.0. I haven't found a way to disable this access and allow DNS queries only from internal networks.

    Could someone please advise me on how to configure this?



    ------------------------------
    Cristian Menghi
    ------------------------------


  • 2.  RE: OpenResolver open on WAN interfaces.

    Posted 15 days ago

    Hi Cristian,

    By default the gateway doesn't answer DNS from the Internet. Its DNS service only serves local networks, and Security → Firewall blocks all incoming traffic, including port 53. 

    If you want to use your own DNS servers, you can set them statically. 

    LAN (DNS given to your clients):
    Networks → LAN → [network] → IP Assignment → DNS Resolution → DNS Servers → Static
    Enter your server's IP. Clients get it through DHCP and query it directly over the LAN. You can also set a Domain Suffix.

    WAN (DNS used by the gateway itself):
    Networks → WAN → [WAN network] → Connectivity → DNS Server Assignment → Static
    Enter the DNS you want the gateway to use instead of your ISP's.



    ------------------------------
    Sylvain Bouchard
    ------------------------------



  • 3.  RE: OpenResolver open on WAN interfaces.

    Posted 23 hours ago
    Hi, 

    In https://portal.instant-on.hpe.com in the path you describe:

    Security → Firewall blocks all incoming traffic, including port 53. isn't present

    And cant create a firewall rule to block port 53/UDP on firewall rules isn't possible.


    Thks.
    --  Cristian Menghi Services & Consulting Mail: cmenghi@rootway.com Cel: (+598) 99 74 1301 Uruguay





  • 4.  RE: OpenResolver open on WAN interfaces.

    Posted 23 hours ago

    Hi Cristian,

    Thanks for your question. By default the Instant On gateway doesn't answer DNS queries coming from the Internet. Its built-in DNS service only answers clients on your local networks, and the default firewall blocks all incoming traffic on the WAN, including TCP/UDP 53. There's no setting to disable because the port isn't open on the gateway itself.

    If a scan shows port 53 open on your public IP, here is what to check:

    1. Test from outside your network
    Scanning your own public IP from inside the LAN doesn't test the WAN side. Use a device that is really outside, such as a phone on mobile data or a remote server:
    nslookup hpe.com <your-public-IP> 
    If the query times out or is refused, the gateway isn't an open resolver.
    Also note that nmap often reports UDP 53 as "open|filtered" when it gets no reply. That doesn't mean a resolver answered.

    2. Check whether the public IP really belongs to the gateway (double NAT)
    Go to Devices → [your gateway] → Overview → Connectivity and look at the IP address.
    If it's a private address (10.x, 172.16–31.x, 192.168.x or 100.64–127.x), something sits in front of the gateway, a router or modem, or the carrier's network. Many of them run their own DNS forwarder on the WAN side, and that's what the scan is finding. Disable it on that device, or put it in bridge/passthrough mode.

    If you want to use your own DNS server, configure it statically 

    a) To give your clients your own (internal or external) DNS server:
    Networks → LAN → [your network] → IP Assignment → DNS Resolution

    • DNS Servers: select Static
    • Enter the Primary DNS Server and Secondary DNS Server (for example your domain controller's LAN IP)
    • Optionally set a Domain Suffix (for example your AD domain)

    Clients on that network will receive these servers through DHCP. Your LAN clients can already reach an internal DNS server directly, so no inbound rule or port forwarding is needed.

    b) To make the gateway itself use specific resolvers instead of your ISP's:
    Networks → WAN → [your WAN network] → Overview → Connectivity

    • DNS Server Assignment: select Static
    • Enter the Primary DNS Server and Secondary DNS Server

    Neither setting opens port 53 on the WAN.

    If an external test (step 1) still gets an answer from your gateway's public IP 



    ------------------------------
    Sylvain Bouchard
    ------------------------------