---
title: Why can't I surf?
slug: why-cant-i-surf
description: "Follow our comprehensive troubleshooting guide to resolve browsing issues with your public IPs on the Cloud Panel. Learn how to add IPs, check DNS settings, and confirm connectivity to our DNS servers. 
createdAt: 2024-01-19T13:54:45.975Z
---

In order to use our service, you will need to register your public IP(s) on our Cloud Panel.
Below are some tips that may help you in case you are unable to browse:


- If you are using a **Load-Balancer system** (or backup line), you will need to add a*ll public IPs on your Cloud Panel*.
- Check your router/firewall and make sure there are no filters on port 53 (DNS), which could block traffic on our ip classes (185.236.104.0/24 and 185.236.105.0/24).
- Check that our DNS ( **Primary: 185.236.104.104, Secondary: 185.236.105.105**) are reachable from your network using a tool such as ping/tracer.
- Verify that the *public IP(s)* registered on the cloud are currently in use.
  You will be able to view your IP via the following link [what is my ip.](https://www.whatsmyip.org/)
- Verify that there are *no blocking rules on DNS resolution on the router/firewall*.

To verify this you will be able to use a different port instead of the standard port (53).
Using the following commands, you will be able to check if there are any blocking rules on DNS resolution.
Open cmd on your device and run the following commands:
*-nslookup*
*-set port=53535*
*-domain\_blocked* (where domain\_blocked is the domain that should be blocked).
If the result is 185.236.107.107 it means that the domain has been filtered, so there is a redirection on port 53.
In this case you will need to disable the redirection rules on the router/firewall.

- Verify that you have *correctly configured DNS on your device* (or via DHCP service).
- If you configure DNS on the router, it does not mean that internally the devices use these DNS, so we will need to configure a *DHCP service* or firewall rules to force the use of our DNS on the internal network.
- Verify that your *public IP is registered on the system* (network menu).
- Log in to your *Cloud panel* and verify that your license has not expired.

If the problem has not been resolved, please open a support ticket by [clicking here](https://cloud.flashstart.com/customerarea/support/tickets/).

**Other ways to ask:**

- Why do I have difficulty navigating?
- The problems related to navigation.



## Overview&#x20;

To utilize the filtering service, your public IP must be registered on the Cloud Panel. If you are experiencing browsing difficulties, perform the following diagnostic checks to identify and resolve the issue.

## Connectivity and IP Verification

- **Load Balancing:** If your network utilizes a Load-Balancer system, ensure every active external IP is added to your Cloud Panel.
- **Current IP Match:** Confirm that the public IP registered in the cloud matches your active connection. You can check this by using an external[ IP lookup tool](https://www.whatsmyip.org/).
- **Server Reachability:** Use network utilities like ping or traceroute to verify that our primary and secondary servers are fully reachable from your network.

## Firewall and Redirection Diagnostics

- **Traffic Blocking:** Check your router or firewall to ensure there are no filters on port 53 that could block outbound traffic to our IP classes.
- **DNS Redirection Test:** Verify that there are no hidden blocking rules intercepting your resolution requests. You can test this by using an alternate port instead of the standard port. Open the command prompt on your device and run the following commands sequentially.

```bash
nslookup
set port=53535
domain_blocked
```

If the result returns 185.236.107.107, the domain is being filtered properly on the alternate port, indicating there is a localized redirection rule hijacking your standard port traffic. You must disable these redirection rules on your router or firewall.

- **Device Distribution:** Verify that you have correctly configured the custom DNS directly on your device. Configuring it solely on the router's interface does not guarantee internal routing; you must actively configure a DHCP service or local firewall rules to force internal devices to use the correct servers.

## Account and System Status

- Verify that your current public IP is properly active and registered on the system.
- Log in to your Cloud Panel to ensure your service license has not expired.

If the problem remains unresolved after completing these checks, please open a [technical support ticket](https://cloud.flashstart.com/customerarea/support/tickets/).

