Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!


Shells Virtual Desktop
BMail.ag - Secure Email Service
Server.net
CPLicense.net
VPS Server
Buy VPN
Vultr
VMs for AI
HostDare
ReliableSite White-Label Dedicated Hosting for Resellers
InterServer VPS
BMail.ag - Secure Email Service
Best VPN
High-Performance Bare Metal Server Solutions
Karvl.com
Server Mania Cloud Hosting
DataWagon Hosting
AlphaVPS Hosting
Evoxt.com
Clouvider
Godlike VPS
VPS Hosting with NVMe
Residential IPs in the US & 4G Mobile Proxies in EU & US with Unlimited Bandwidth
ReliableSite White-Label Dedicated Hosting for Resellers
Shells Virtual Desktop
New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

The IncogNET thread - Discussion, news and updates.

1151618202127

Comments

  • @MannDude said:

    @ServerBachelor said:

    @MannDude said:

    @ServerBachelor said:

    @MannDude said:

    @musicalderp said:
    How's that email service coming?

    Hiatus lol.

    Was going to launch last year but decided against it since it was around Black Friday and all the mail related excitement was elslewhere. This was also a good decision on my behalf because it was going to be Netherlands based, but we migrated datacenters and had a few weeks of hell in regards to service quality in that POP... So it would have been a flop of a launch.

    I'm still on the fence about releasing it, however.

    Are issues persisting in NL? I have a shared hosting plan there (just idling) and my attempts to log into DA timeout.

    Edit: By contrast, no issues w/ shared hosting in the KCMO location.

    Shouldn't be. Common cause for that would be a blacklisting ld your IP in th firewall. If you've got a mail client trying to fetch emails on a scheduled polling and it fails due to password mismatch or something, you'll get blocked. But feel free to PM me your email used for WHMCS and your IP. I'll check it out.

    I was using IncogVPN on the NL location (23.137.248.235). Switched to a different location and I was able to log in to the NL shared hosting.

    csf.deny: 23.137.248.235 # lfd: (directadmin) Failed DirectAdmin login from 23.137.248.235 (NL/The Netherlands/-): 5 in the last 3600 secs - Sat Jan 25 15:22:41 2025
    

    Removed. Looks like it was blocked for almost a year, this is the first report we've received.

    Thanks, can confirm all works as expected now.

    Thanked by 1MannDude
  • MannDudeMannDude Patron Provider, Veteran

    Decided to use Cursor to modify the default WHMCS "six" theme. Just testing on a local dev install of WHMCS.

  • MannDudeMannDude Patron Provider, Veteran

    Getting around to working on the storage stuff.

    10TB HDD box, 8vCPU and 16GB RAM. 5Gbps port cap. Not bad.

    No guarantee we'll actually offer any storage servers long term but I've got a big box online. Let me see what I have leftover after doing things like setting up some crypto nodes (We run https://xmr.gd - But I want to run some LTC, ZCash and other nodes too).

    # ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## #
    #              Yet-Another-Bench-Script              #
    #                     v2025-04-20                    #
    # https://github.com/masonr/yet-another-bench-script #
    # ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## #
    
    Sat Dec 13 12:33:54 PM GMT 2025
    
    Basic System Information:
    ---------------------------------
    Uptime     : 0 days, 0 hours, 4 minutes
    Processor  : Intel(R) Xeon(R) CPU E5-2650 v4 @ 2.20GHz
    CPU cores  : 8 @ 2199.996 MHz
    AES-NI     : ✔ Enabled
    VM-x/AMD-V : ✔ Enabled
    RAM        : 15.6 GiB
    Swap       : 4.0 GiB
    Disk       : 9.6 TiB
    Distro     : Debian GNU/Linux 13 (trixie)
    Kernel     : 6.17.12-x64v3-xanmod1
    VM Type    : KVM
    IPv4/IPv6  : ✔ Online / ✔ Online
    
    IPv6 Network Information:
    ---------------------------------
    ISP        : IncogNet LLC
    ASN        : AS40663 IncogNet LLC
    Host       : IncogNET LLC
    Location   : Sofia, Sofia-Capital (22)
    Country    : Bulgaria
    
    fio Disk Speed Tests (Mixed R/W 50/50) (Partition /dev/vda3):
    ---------------------------------
    Block Size | 4k            (IOPS) | 64k           (IOPS)
      ------   | ---            ----  | ----           ---- 
    Read       | 74.63 MB/s   (18.6k) | 959.03 MB/s  (14.9k)
    Write      | 74.83 MB/s   (18.7k) | 964.07 MB/s  (15.0k)
    Total      | 149.47 MB/s  (37.3k) | 1.92 GB/s    (30.0k)
               |                      |                     
    Block Size | 512k          (IOPS) | 1m            (IOPS)
      ------   | ---            ----  | ----           ---- 
    Read       | 1.80 GB/s     (3.5k) | 1.31 GB/s     (1.2k)
    Write      | 1.90 GB/s     (3.7k) | 1.39 GB/s     (1.3k)
    Total      | 3.70 GB/s     (7.2k) | 2.70 GB/s     (2.6k)
    
    iperf3 Network Speed Tests (IPv4):
    ---------------------------------
    Provider        | Location (Link)           | Send Speed      | Recv Speed      | Ping           
    -----           | -----                     | ----            | ----            | ----           
    Clouvider       | London, UK (10G)          | 5.06 Gbits/sec  | 2.06 Gbits/sec  | 35.1 ms        
    Eranium         | Amsterdam, NL (100G)      | 5.31 Gbits/sec  | 4.33 Gbits/sec  | 31.3 ms        
    Uztelecom       | Tashkent, UZ (10G)        | 5.01 Gbits/sec  | 1.47 Gbits/sec  | 103 ms         
    Leaseweb        | Singapore, SG (10G)       | 3.43 Gbits/sec  | 488 Mbits/sec   | 164 ms         
    Clouvider       | Los Angeles, CA, US (10G) | 1.03 Gbits/sec  | 338 Mbits/sec   | 169 ms         
    Leaseweb        | NYC, NY, US (10G)         | 4.93 Gbits/sec  | 1.10 Gbits/sec  | 113 ms         
    Edgoo           | Sao Paulo, BR (1G)        | 3.72 Gbits/sec  | 769 Mbits/sec   | 221 ms         
    
    iperf3 Network Speed Tests (IPv6):
    ---------------------------------
    Provider        | Location (Link)           | Send Speed      | Recv Speed      | Ping           
    -----           | -----                     | ----            | ----            | ----           
    Clouvider       | London, UK (10G)          | 4.84 Gbits/sec  | 2.40 Gbits/sec  | 34.8 ms        
    Eranium         | Amsterdam, NL (100G)      | 5.35 Gbits/sec  | 4.26 Gbits/sec  | 31.3 ms        
    Uztelecom       | Tashkent, UZ (10G)        | 4.98 Gbits/sec  | 1.44 Gbits/sec  | 103 ms         
    Leaseweb        | Singapore, SG (10G)       | 3.04 Gbits/sec  | 1.47 Gbits/sec  | 164 ms         
    Clouvider       | Los Angeles, CA, US (10G) | 927 Mbits/sec   | 762 Mbits/sec   | 169 ms         
    Leaseweb        | NYC, NY, US (10G)         | 4.70 Gbits/sec  | 2.24 Gbits/sec  | 113 ms         
    Edgoo           | Sao Paulo, BR (1G)        | busy            | 659 Mbits/sec   | 221 ms         
    
    Geekbench 6 Benchmark Test:
    ---------------------------------
    Test            | Value                         
                    |                               
    Single Core     | 803                           
    Multi Core      | 3511                          
    Full Test       | https://browser.geekbench.com/v6/cpu/15548189
    
    YABS completed in 16 min 59 sec
    
    
  • olokeoloke Member, Host Rep

    @MannDude said:
    You can help us test our new Tor Relay tool here: https://incognet.io/tor-relay-config -- Maybe a good thin to test out on your new 1776 VPS. ;)

    Hi! I have some feedback.

    Snowflake

    # Generated Tor Relay Configuration
    # Generated by: Tor Relay Configuration Tool at incognet.io
    #
    # IMPORTANT: Review Tor's official documentation and check local laws
    # before deploying this configuration in production.
    #
    
    Nickname test
    ContactInfo [email protected]
    DataDirectory /var/lib/tor
    
    # Snowflake relay configuration
    # Snowflake helps users bypass censorship by acting as a temporary proxy
    ExitPolicy reject *:*
    ServerTransportPlugin snowflake exec /usr/bin/snowflake-client
    
    # Relay-only mode (disable client proxy)
    SocksPort 0
    
    # Performance and security settings
    # Disable client functionality
    ControlPort 0
    
    # Enable directory caching for better performance
    DirCache 1
    
    # Reduce memory usage (adjust based on your system)
    # MaxMemInQueues 512 MB
    
    # Logging (adjust level as needed: notice, info, warn, err)
    Log notice file /var/log/tor/notices.log
    
    # Automatically publish relay descriptor
    PublishServerDescriptor 1
    

    First of all, the configuration for "Snowflake relay" isn't really a relay, but a client. Snowflake relay doesn't need Tor to be installed on the server at all.

    It even says:

    ServerTransportPlugin snowflake exec /usr/bin/snowflake-client
    

    In torrc config generated by your site.

    Snowflake bridge doesn't really work like a relay, the terminology can be quite confusing but the binary you should run to help people connect is called snowflake proxy. It's because it proxies the traffic between snowflake client (the one that wants to connect to Tor) and a snowflake server (also called a relay in proxy docs, ran by Tor project themselves, the default one is snowflake.torproject.net ). You can read more on the Tor forum to see more knowledgeable people than me discussing it.

    In snowflake, there's also another component called broker. It helps your snowflake proxy find clients that need a connection. It's also hosted by Tor project themselves at snowflake-broker.torproject.net .

    Guard Relay

    # Generated Tor Relay Configuration
    # Generated by: Tor Relay Configuration Tool at incognet.io
    #
    # IMPORTANT: Review Tor's official documentation and check local laws
    # before deploying this configuration in production.
    #
    
    Nickname test
    ContactInfo [email protected]
    Address 7.7.7.7
    IPv6Address 2001:fe::af
    ORPort 9999
    DataDirectory /var/lib/tor
    
    # Guard relay configuration (non-exit)
    # Guard relays are the first hop in Tor circuits
    ExitPolicy reject *:*
    
    # Bandwidth limits
    BandwidthRate 10000000
    BandwidthBurst 20000000
    
    # Monthly bandwidth accounting
    AccountingMax 40000000000000
    AccountingStart month 1 00:00
    
    # Relay-only mode (disable client proxy)
    SocksPort 0
    
    # Performance and security settings
    # Disable client functionality
    ControlPort 0
    
    # Enable directory caching for better performance
    DirCache 1
    
    # Reduce memory usage (adjust based on your system)
    # MaxMemInQueues 512 MB
    
    # Logging (adjust level as needed: notice, info, warn, err)
    Log notice file /var/log/tor/notices.log
    
    # Automatically publish relay descriptor
    PublishServerDescriptor 1
    

    Next, selecting 2nd option. Why is it named "Guard Relay"? Maybe a more suiting name would be Middle/Guard Relay (more commonly seen even in Tor docs). You can't guarantee the relay will be a guard because it's determined by Tor Directory Authorities:

    Directory authorities assign the Guard flag to relays based on three characteristics: "bandwidth" (they need to have a large enough consensus weight), "weighted fractional uptime" (they need to be working most of the time), and "time known" (to make attacks more expensive, we don't want to give the Guard flag to relays that haven't been around a while first).

    Now, the DirCache 1 option does not seem to be necessary. I couldn't find much configs where it was specified explicitly as 1 is the default value. Setting it to 0 makes your relay not eligible for Guard (forcing Middle-only) but I'm not sure how it got to your config tool. The comment above (# Enable directory caching for better performance) also doesn't really explain what it is doing.

    That's not really important compared to IPv6Address option generated which does not even exist. Not sure which AI hallucinated it but I had to check myself to be sure:

    [WARN] Failed to parse/validate config: Unknown option 'IPv6Address'.  Failing.
    

    If you want to specify IPv6 address to use, you need to do that in ORPort directive like:

    ORPort [2001:fe::af]:9001
    

    Lastly (for this section), when specifying accounting, it auto-generated line:

    AccountingStart month 1 00:00
    

    It assumes traffic cap resets at the start of each month. That may not always be true, it would be nice to see some additional info (or field) to change it to other day/hour in the month.

    Exit Relay

    # Generated Tor Relay Configuration
    # Generated by: Tor Relay Configuration Tool at incognet.io
    #
    # IMPORTANT: Review Tor's official documentation and check local laws
    # before deploying this configuration in production.
    #
    
    Nickname test
    ContactInfo [email protected]
    Address 7.7.7.7
    IPv6Address 2001:fe::af
    ORPort 9999
    DataDirectory /var/lib/tor
    
    # Exit relay configuration
    # Exit relays handle traffic exiting to the Internet.
    # This configuration uses a strict exit policy blocking mail and abuse ports.
    
    # Strict exit policy - block mail ports to prevent abuse
    ExitPolicy reject *:25
    ExitPolicy reject *:587
    ExitPolicy reject *:465
    ExitPolicy reject *:2525
    
    # Block other common abuse ports
    ExitPolicy reject *:135
    ExitPolicy reject *:139
    ExitPolicy reject *:445
    ExitPolicy reject *:1433
    ExitPolicy reject *:3306
    ExitPolicy reject *:3389
    ExitPolicy reject *:5432
    ExitPolicy reject *:5900
    
    # Allow common web ports
    ExitPolicy accept *:80
    ExitPolicy accept *:443
    
    # Allow other common safe ports
    ExitPolicy accept *:20
    ExitPolicy accept *:21
    ExitPolicy accept *:22
    ExitPolicy accept *:53
    ExitPolicy accept *:110
    ExitPolicy accept *:143
    ExitPolicy accept *:993
    ExitPolicy accept *:995
    
    # Reject everything else
    ExitPolicy reject *:*
    
    # Bandwidth limits
    BandwidthRate 10000000
    BandwidthBurst 20000000
    
    # Monthly bandwidth accounting
    AccountingMax 40000000000000
    AccountingStart month 1 00:00
    
    # Relay-only mode (disable client proxy)
    SocksPort 0
    
    # Performance and security settings
    # Disable client functionality
    ControlPort 0
    
    # Enable directory caching for better performance
    DirCache 1
    
    # Reduce memory usage (adjust based on your system)
    # MaxMemInQueues 512 MB
    
    # Logging (adjust level as needed: notice, info, warn, err)
    Log notice file /var/log/tor/notices.log
    
    # Automatically publish relay descriptor
    PublishServerDescriptor 1
    

    Things from Guard relay section apply here as well. Additionally, I suggest adding some slider/choice of Exit policy. The current one looks a bit more restrictive than Reduced Exit Policy recommended by the Tor docs. At the same time, it doesn't really explain why certain ports are blocked and others unblocked. I would imagine some users would appreciate more fine grained control from the most restrictive (only accept 53, 80, 443) to least restrictive (the default Reduced Exit Policy, doesn't really make sense to run exits entirely unrestricted imo).

    Bridge

    # Generated Tor Relay Configuration
    # Generated by: Tor Relay Configuration Tool at incognet.io
    #
    # IMPORTANT: Review Tor's official documentation and check local laws
    # before deploying this configuration in production.
    #
    
    Nickname test
    ContactInfo [email protected]
    Address 7.7.7.7
    IPv6Address 2001:fe::af
    ORPort 9999
    DataDirectory /var/lib/tor
    
    # Bridge relay configuration
    # Bridges are unlisted relays that help censored users connect
    BridgeRelay 1
    ExitPolicy reject *:*
    
    # Bandwidth limits
    BandwidthRate 10000000
    BandwidthBurst 20000000
    
    # Monthly bandwidth accounting
    AccountingMax 40000000000000
    AccountingStart month 1 00:00
    
    # Relay-only mode (disable client proxy)
    SocksPort 0
    
    # Performance and security settings
    # Disable client functionality
    ControlPort 0
    
    # Enable directory caching for better performance
    DirCache 1
    
    # Reduce memory usage (adjust based on your system)
    # MaxMemInQueues 512 MB
    
    # Logging (adjust level as needed: notice, info, warn, err)
    Log notice file /var/log/tor/notices.log
    
    # Automatically publish relay descriptor
    PublishServerDescriptor 1
    

    What kind of bridge is it supposed to be?
    Assuming it's obfs4, it lacks the ServerTransportPlugin obfs4 exec /usr/bin/obfs4proxy option (and part about installing obfs4proxy binary itself). You can read the official Tor docs to see how a config for obfs4 bridge should look like.

    Additionally, it would be nice to see WebTunnel bridge setup too. It is not as easy to set up as snowflake or obfs4 (requires obtaining TLS certificate and exposing it on port 443), but it's been reported it works much better as some countries started blocking "unknown" traffic which obfs4 mimics.

    Other notes

    • The link to Nyx source (https://gitlab.torproject.org/tpo/core/nyx) is invalid. Not sure if it is still (or ever was on Torproject's gitlab), but the current one lives on Github: https://github.com/torproject/nyx/tree/master .

    • ...
      // Initialize on page load
      document.addEventListener('DOMContentLoaded', function() {
      updateRelayFields();
      
      // [UPDATE] Auto-scroll to generated configuration after form submission
      
      // Disable monthly quota if daily quota is set and vice versa
      const dailyQuota = document.getElementById('daily_quota');
      const monthlyQuota = document.getElementById('monthly_quota');
      ...
      

      It's interesting to see comments about updates in script source code ;)

      • I think I would feel safer if the config generation was done client-side by JavaScript entirely. I know a lot of relays are public anyways but I don't see any reason to not do it on client-side. Currently the site sends all option (including email contact and IP address) to the backend where in theory it could be stored. It should be no problem for AI to create the generation logic on the frontend.
    • Some fields are explained, some aren't. It would be nice to add more explanations for all presented options (and other options they may wanna use). It would make the tool more useful.

    • Overall, pretty disappointed. I hope it's an alpha-tool that's not meant for public. Currently some options seem to be hallucinated, outdated or incorrectly described. Not something I would expect from a host who charges big money in the name of free speech and privacy.

  • MannDudeMannDude Patron Provider, Veteran

    @oloke said:

    @MannDude said:
    You can help us test our new Tor Relay tool here: https://incognet.io/tor-relay-config -- Maybe a good thin to test out on your new 1776 VPS. ;)

    Hi! I have some feedback.

    Snowflake

    # Generated Tor Relay Configuration
    # Generated by: Tor Relay Configuration Tool at incognet.io
    #
    # IMPORTANT: Review Tor's official documentation and check local laws
    # before deploying this configuration in production.
    #
    
    Nickname test
    ContactInfo [email protected]
    DataDirectory /var/lib/tor
    
    # Snowflake relay configuration
    # Snowflake helps users bypass censorship by acting as a temporary proxy
    ExitPolicy reject *:*
    ServerTransportPlugin snowflake exec /usr/bin/snowflake-client
    
    # Relay-only mode (disable client proxy)
    SocksPort 0
    
    # Performance and security settings
    # Disable client functionality
    ControlPort 0
    
    # Enable directory caching for better performance
    DirCache 1
    
    # Reduce memory usage (adjust based on your system)
    # MaxMemInQueues 512 MB
    
    # Logging (adjust level as needed: notice, info, warn, err)
    Log notice file /var/log/tor/notices.log
    
    # Automatically publish relay descriptor
    PublishServerDescriptor 1
    

    First of all, the configuration for "Snowflake relay" isn't really a relay, but a client. Snowflake relay doesn't need Tor to be installed on the server at all.

    It even says:

    ServerTransportPlugin snowflake exec /usr/bin/snowflake-client
    

    In torrc config generated by your site.

    Snowflake bridge doesn't really work like a relay, the terminology can be quite confusing but the binary you should run to help people connect is called snowflake proxy. It's because it proxies the traffic between snowflake client (the one that wants to connect to Tor) and a snowflake server (also called a relay in proxy docs, ran by Tor project themselves, the default one is snowflake.torproject.net ). You can read more on the Tor forum to see more knowledgeable people than me discussing it.

    In snowflake, there's also another component called broker. It helps your snowflake proxy find clients that need a connection. It's also hosted by Tor project themselves at snowflake-broker.torproject.net .

    Guard Relay

    # Generated Tor Relay Configuration
    # Generated by: Tor Relay Configuration Tool at incognet.io
    #
    # IMPORTANT: Review Tor's official documentation and check local laws
    # before deploying this configuration in production.
    #
    
    Nickname test
    ContactInfo [email protected]
    Address 7.7.7.7
    IPv6Address 2001:fe::af
    ORPort 9999
    DataDirectory /var/lib/tor
    
    # Guard relay configuration (non-exit)
    # Guard relays are the first hop in Tor circuits
    ExitPolicy reject *:*
    
    # Bandwidth limits
    BandwidthRate 10000000
    BandwidthBurst 20000000
    
    # Monthly bandwidth accounting
    AccountingMax 40000000000000
    AccountingStart month 1 00:00
    
    # Relay-only mode (disable client proxy)
    SocksPort 0
    
    # Performance and security settings
    # Disable client functionality
    ControlPort 0
    
    # Enable directory caching for better performance
    DirCache 1
    
    # Reduce memory usage (adjust based on your system)
    # MaxMemInQueues 512 MB
    
    # Logging (adjust level as needed: notice, info, warn, err)
    Log notice file /var/log/tor/notices.log
    
    # Automatically publish relay descriptor
    PublishServerDescriptor 1
    

    Next, selecting 2nd option. Why is it named "Guard Relay"? Maybe a more suiting name would be Middle/Guard Relay (more commonly seen even in Tor docs). You can't guarantee the relay will be a guard because it's determined by Tor Directory Authorities:

    Directory authorities assign the Guard flag to relays based on three characteristics: "bandwidth" (they need to have a large enough consensus weight), "weighted fractional uptime" (they need to be working most of the time), and "time known" (to make attacks more expensive, we don't want to give the Guard flag to relays that haven't been around a while first).

    Now, the DirCache 1 option does not seem to be necessary. I couldn't find much configs where it was specified explicitly as 1 is the default value. Setting it to 0 makes your relay not eligible for Guard (forcing Middle-only) but I'm not sure how it got to your config tool. The comment above (# Enable directory caching for better performance) also doesn't really explain what it is doing.

    That's not really important compared to IPv6Address option generated which does not even exist. Not sure which AI hallucinated it but I had to check myself to be sure:

    [WARN] Failed to parse/validate config: Unknown option 'IPv6Address'.  Failing.
    

    If you want to specify IPv6 address to use, you need to do that in ORPort directive like:

    ORPort [2001:fe::af]:9001
    

    Lastly (for this section), when specifying accounting, it auto-generated line:

    AccountingStart month 1 00:00
    

    It assumes traffic cap resets at the start of each month. That may not always be true, it would be nice to see some additional info (or field) to change it to other day/hour in the month.

    Exit Relay

    # Generated Tor Relay Configuration
    # Generated by: Tor Relay Configuration Tool at incognet.io
    #
    # IMPORTANT: Review Tor's official documentation and check local laws
    # before deploying this configuration in production.
    #
    
    Nickname test
    ContactInfo [email protected]
    Address 7.7.7.7
    IPv6Address 2001:fe::af
    ORPort 9999
    DataDirectory /var/lib/tor
    
    # Exit relay configuration
    # Exit relays handle traffic exiting to the Internet.
    # This configuration uses a strict exit policy blocking mail and abuse ports.
    
    # Strict exit policy - block mail ports to prevent abuse
    ExitPolicy reject *:25
    ExitPolicy reject *:587
    ExitPolicy reject *:465
    ExitPolicy reject *:2525
    
    # Block other common abuse ports
    ExitPolicy reject *:135
    ExitPolicy reject *:139
    ExitPolicy reject *:445
    ExitPolicy reject *:1433
    ExitPolicy reject *:3306
    ExitPolicy reject *:3389
    ExitPolicy reject *:5432
    ExitPolicy reject *:5900
    
    # Allow common web ports
    ExitPolicy accept *:80
    ExitPolicy accept *:443
    
    # Allow other common safe ports
    ExitPolicy accept *:20
    ExitPolicy accept *:21
    ExitPolicy accept *:22
    ExitPolicy accept *:53
    ExitPolicy accept *:110
    ExitPolicy accept *:143
    ExitPolicy accept *:993
    ExitPolicy accept *:995
    
    # Reject everything else
    ExitPolicy reject *:*
    
    # Bandwidth limits
    BandwidthRate 10000000
    BandwidthBurst 20000000
    
    # Monthly bandwidth accounting
    AccountingMax 40000000000000
    AccountingStart month 1 00:00
    
    # Relay-only mode (disable client proxy)
    SocksPort 0
    
    # Performance and security settings
    # Disable client functionality
    ControlPort 0
    
    # Enable directory caching for better performance
    DirCache 1
    
    # Reduce memory usage (adjust based on your system)
    # MaxMemInQueues 512 MB
    
    # Logging (adjust level as needed: notice, info, warn, err)
    Log notice file /var/log/tor/notices.log
    
    # Automatically publish relay descriptor
    PublishServerDescriptor 1
    

    Things from Guard relay section apply here as well. Additionally, I suggest adding some slider/choice of Exit policy. The current one looks a bit more restrictive than Reduced Exit Policy recommended by the Tor docs. At the same time, it doesn't really explain why certain ports are blocked and others unblocked. I would imagine some users would appreciate more fine grained control from the most restrictive (only accept 53, 80, 443) to least restrictive (the default Reduced Exit Policy, doesn't really make sense to run exits entirely unrestricted imo).

    Bridge

    # Generated Tor Relay Configuration
    # Generated by: Tor Relay Configuration Tool at incognet.io
    #
    # IMPORTANT: Review Tor's official documentation and check local laws
    # before deploying this configuration in production.
    #
    
    Nickname test
    ContactInfo [email protected]
    Address 7.7.7.7
    IPv6Address 2001:fe::af
    ORPort 9999
    DataDirectory /var/lib/tor
    
    # Bridge relay configuration
    # Bridges are unlisted relays that help censored users connect
    BridgeRelay 1
    ExitPolicy reject *:*
    
    # Bandwidth limits
    BandwidthRate 10000000
    BandwidthBurst 20000000
    
    # Monthly bandwidth accounting
    AccountingMax 40000000000000
    AccountingStart month 1 00:00
    
    # Relay-only mode (disable client proxy)
    SocksPort 0
    
    # Performance and security settings
    # Disable client functionality
    ControlPort 0
    
    # Enable directory caching for better performance
    DirCache 1
    
    # Reduce memory usage (adjust based on your system)
    # MaxMemInQueues 512 MB
    
    # Logging (adjust level as needed: notice, info, warn, err)
    Log notice file /var/log/tor/notices.log
    
    # Automatically publish relay descriptor
    PublishServerDescriptor 1
    

    What kind of bridge is it supposed to be?
    Assuming it's obfs4, it lacks the ServerTransportPlugin obfs4 exec /usr/bin/obfs4proxy option (and part about installing obfs4proxy binary itself). You can read the official Tor docs to see how a config for obfs4 bridge should look like.

    Additionally, it would be nice to see WebTunnel bridge setup too. It is not as easy to set up as snowflake or obfs4 (requires obtaining TLS certificate and exposing it on port 443), but it's been reported it works much better as some countries started blocking "unknown" traffic which obfs4 mimics.

    Other notes

    • The link to Nyx source (https://gitlab.torproject.org/tpo/core/nyx) is invalid. Not sure if it is still (or ever was on Torproject's gitlab), but the current one lives on Github: https://github.com/torproject/nyx/tree/master .

    • ...
      // Initialize on page load
      document.addEventListener('DOMContentLoaded', function() {
      updateRelayFields();
      
      // [UPDATE] Auto-scroll to generated configuration after form submission
          
      // Disable monthly quota if daily quota is set and vice versa
      const dailyQuota = document.getElementById('daily_quota');
      const monthlyQuota = document.getElementById('monthly_quota');
      ...
      

      It's interesting to see comments about updates in script source code ;)

      • I think I would feel safer if the config generation was done client-side by JavaScript entirely. I know a lot of relays are public anyways but I don't see any reason to not do it on client-side. Currently the site sends all option (including email contact and IP address) to the backend where in theory it could be stored. It should be no problem for AI to create the generation logic on the frontend.
    • Some fields are explained, some aren't. It would be nice to add more explanations for all presented options (and other options they may wanna use). It would make the tool more useful.

    • Overall, pretty disappointed. I hope it's an alpha-tool that's not meant for public. Currently some options seem to be hallucinated, outdated or incorrectly described. Not something I would expect from a host who charges big money in the name of free speech and privacy.

    Vibe coding. Will re-review it. Thanks for the feedback!

    Thanked by 1oloke
  • Will your coming DNS product be for domains not registered with Incognet as well?

  • MannDudeMannDude Patron Provider, Veteran
    edited December 2025

    @flytheflag said:
    Will your coming DNS product be for domains not registered with Incognet as well?

    Possibly, BUT DNS is a hard sell. We're not doing anything that you can't get for free already from dns.he.net, Cloudflare, etc.

    Originally we didn't even offer DNS hosting because we just assumed those buying domains already had a favorite DNS provider. Turns out it was the opposite, many expected the domain to come with DNS hosting.

    First we just offered free "DNS Only" DirectAdmin accounts.

    Then we began to offer what we're doing now.

    New DNS cluster is in production already, just need to switch over to it. It's just a 4 POP anycast setup + 2 unicast NS in NYC from two different DDoS protection networks. Should be resilient enough of a setup but not going to even try to pretend it's better than anything else other than our first two DNS setups. It's just 4x BuyVM POPs using our ASN / IPs + Royale Hosting as a 2nd provider and Sucura for a 3rd. Unlikely that it'd all be down at once, at least. My main concern with it was just getting things off our own network (one NS would be fine, but not all) and spreading things out for redundancy.

    Thanked by 2iriska JohnnySac
  • @MannDude said: DNS is a hard sell. We're not doing anything that you can't get for free already from dns.he.net, Cloudflare, etc

    Simply not being Cloudflare or Hurricane is what makes it attractive. This isn't about tech specs. It's about having choice and the option to get away from the herd.

  • @MannDude said:
    Getting around to working on the storage stuff.

    10TB HDD box, 8vCPU and 16GB RAM. 5Gbps port cap. Not bad.

    No guarantee we'll actually offer any storage servers long term but I've got a big box online. Let me see what I have leftover after doing things like setting up some crypto nodes (We run https://xmr.gd - But I want to run some LTC, ZCash and other nodes too).

    # ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## #
    #              Yet-Another-Bench-Script              #
    #                     v2025-04-20                    #
    # https://github.com/masonr/yet-another-bench-script #
    # ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## #
    
    Sat Dec 13 12:33:54 PM GMT 2025
    
    Basic System Information:
    ---------------------------------
    Uptime     : 0 days, 0 hours, 4 minutes
    Processor  : Intel(R) Xeon(R) CPU E5-2650 v4 @ 2.20GHz
    CPU cores  : 8 @ 2199.996 MHz
    AES-NI     : ✔ Enabled
    VM-x/AMD-V : ✔ Enabled
    RAM        : 15.6 GiB
    Swap       : 4.0 GiB
    Disk       : 9.6 TiB
    Distro     : Debian GNU/Linux 13 (trixie)
    Kernel     : 6.17.12-x64v3-xanmod1
    VM Type    : KVM
    IPv4/IPv6  : ✔ Online / ✔ Online
    
    IPv6 Network Information:
    ---------------------------------
    ISP        : IncogNet LLC
    ASN        : AS40663 IncogNet LLC
    Host       : IncogNET LLC
    Location   : Sofia, Sofia-Capital (22)
    Country    : Bulgaria
    
    fio Disk Speed Tests (Mixed R/W 50/50) (Partition /dev/vda3):
    ---------------------------------
    Block Size | 4k            (IOPS) | 64k           (IOPS)
      ------   | ---            ----  | ----           ---- 
    Read       | 74.63 MB/s   (18.6k) | 959.03 MB/s  (14.9k)
    Write      | 74.83 MB/s   (18.7k) | 964.07 MB/s  (15.0k)
    Total      | 149.47 MB/s  (37.3k) | 1.92 GB/s    (30.0k)
               |                      |                     
    Block Size | 512k          (IOPS) | 1m            (IOPS)
      ------   | ---            ----  | ----           ---- 
    Read       | 1.80 GB/s     (3.5k) | 1.31 GB/s     (1.2k)
    Write      | 1.90 GB/s     (3.7k) | 1.39 GB/s     (1.3k)
    Total      | 3.70 GB/s     (7.2k) | 2.70 GB/s     (2.6k)
    
    iperf3 Network Speed Tests (IPv4):
    ---------------------------------
    Provider        | Location (Link)           | Send Speed      | Recv Speed      | Ping           
    -----           | -----                     | ----            | ----            | ----           
    Clouvider       | London, UK (10G)          | 5.06 Gbits/sec  | 2.06 Gbits/sec  | 35.1 ms        
    Eranium         | Amsterdam, NL (100G)      | 5.31 Gbits/sec  | 4.33 Gbits/sec  | 31.3 ms        
    Uztelecom       | Tashkent, UZ (10G)        | 5.01 Gbits/sec  | 1.47 Gbits/sec  | 103 ms         
    Leaseweb        | Singapore, SG (10G)       | 3.43 Gbits/sec  | 488 Mbits/sec   | 164 ms         
    Clouvider       | Los Angeles, CA, US (10G) | 1.03 Gbits/sec  | 338 Mbits/sec   | 169 ms         
    Leaseweb        | NYC, NY, US (10G)         | 4.93 Gbits/sec  | 1.10 Gbits/sec  | 113 ms         
    Edgoo           | Sao Paulo, BR (1G)        | 3.72 Gbits/sec  | 769 Mbits/sec   | 221 ms         
    
    iperf3 Network Speed Tests (IPv6):
    ---------------------------------
    Provider        | Location (Link)           | Send Speed      | Recv Speed      | Ping           
    -----           | -----                     | ----            | ----            | ----           
    Clouvider       | London, UK (10G)          | 4.84 Gbits/sec  | 2.40 Gbits/sec  | 34.8 ms        
    Eranium         | Amsterdam, NL (100G)      | 5.35 Gbits/sec  | 4.26 Gbits/sec  | 31.3 ms        
    Uztelecom       | Tashkent, UZ (10G)        | 4.98 Gbits/sec  | 1.44 Gbits/sec  | 103 ms         
    Leaseweb        | Singapore, SG (10G)       | 3.04 Gbits/sec  | 1.47 Gbits/sec  | 164 ms         
    Clouvider       | Los Angeles, CA, US (10G) | 927 Mbits/sec   | 762 Mbits/sec   | 169 ms         
    Leaseweb        | NYC, NY, US (10G)         | 4.70 Gbits/sec  | 2.24 Gbits/sec  | 113 ms         
    Edgoo           | Sao Paulo, BR (1G)        | busy            | 659 Mbits/sec   | 221 ms         
    
    Geekbench 6 Benchmark Test:
    ---------------------------------
    Test            | Value                         
                    |                               
    Single Core     | 803                           
    Multi Core      | 3511                          
    Full Test       | https://browser.geekbench.com/v6/cpu/15548189
    
    YABS completed in 16 min 59 sec
    
    

    Any idea which location the storage plans (if made available) will be in?

  • MannDudeMannDude Patron Provider, Veteran

    @ServerBachelor said:

    @MannDude said:
    Getting around to working on the storage stuff.

    10TB HDD box, 8vCPU and 16GB RAM. 5Gbps port cap. Not bad.

    No guarantee we'll actually offer any storage servers long term but I've got a big box online. Let me see what I have leftover after doing things like setting up some crypto nodes (We run https://xmr.gd - But I want to run some LTC, ZCash and other nodes too).

    # ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## #
    #              Yet-Another-Bench-Script              #
    #                     v2025-04-20                    #
    # https://github.com/masonr/yet-another-bench-script #
    # ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## #
    
    Sat Dec 13 12:33:54 PM GMT 2025
    
    Basic System Information:
    ---------------------------------
    Uptime     : 0 days, 0 hours, 4 minutes
    Processor  : Intel(R) Xeon(R) CPU E5-2650 v4 @ 2.20GHz
    CPU cores  : 8 @ 2199.996 MHz
    AES-NI     : ✔ Enabled
    VM-x/AMD-V : ✔ Enabled
    RAM        : 15.6 GiB
    Swap       : 4.0 GiB
    Disk       : 9.6 TiB
    Distro     : Debian GNU/Linux 13 (trixie)
    Kernel     : 6.17.12-x64v3-xanmod1
    VM Type    : KVM
    IPv4/IPv6  : ✔ Online / ✔ Online
    
    IPv6 Network Information:
    ---------------------------------
    ISP        : IncogNet LLC
    ASN        : AS40663 IncogNet LLC
    Host       : IncogNET LLC
    Location   : Sofia, Sofia-Capital (22)
    Country    : Bulgaria
    
    fio Disk Speed Tests (Mixed R/W 50/50) (Partition /dev/vda3):
    ---------------------------------
    Block Size | 4k            (IOPS) | 64k           (IOPS)
      ------   | ---            ----  | ----           ---- 
    Read       | 74.63 MB/s   (18.6k) | 959.03 MB/s  (14.9k)
    Write      | 74.83 MB/s   (18.7k) | 964.07 MB/s  (15.0k)
    Total      | 149.47 MB/s  (37.3k) | 1.92 GB/s    (30.0k)
               |                      |                     
    Block Size | 512k          (IOPS) | 1m            (IOPS)
      ------   | ---            ----  | ----           ---- 
    Read       | 1.80 GB/s     (3.5k) | 1.31 GB/s     (1.2k)
    Write      | 1.90 GB/s     (3.7k) | 1.39 GB/s     (1.3k)
    Total      | 3.70 GB/s     (7.2k) | 2.70 GB/s     (2.6k)
    
    iperf3 Network Speed Tests (IPv4):
    ---------------------------------
    Provider        | Location (Link)           | Send Speed      | Recv Speed      | Ping           
    -----           | -----                     | ----            | ----            | ----           
    Clouvider       | London, UK (10G)          | 5.06 Gbits/sec  | 2.06 Gbits/sec  | 35.1 ms        
    Eranium         | Amsterdam, NL (100G)      | 5.31 Gbits/sec  | 4.33 Gbits/sec  | 31.3 ms        
    Uztelecom       | Tashkent, UZ (10G)        | 5.01 Gbits/sec  | 1.47 Gbits/sec  | 103 ms         
    Leaseweb        | Singapore, SG (10G)       | 3.43 Gbits/sec  | 488 Mbits/sec   | 164 ms         
    Clouvider       | Los Angeles, CA, US (10G) | 1.03 Gbits/sec  | 338 Mbits/sec   | 169 ms         
    Leaseweb        | NYC, NY, US (10G)         | 4.93 Gbits/sec  | 1.10 Gbits/sec  | 113 ms         
    Edgoo           | Sao Paulo, BR (1G)        | 3.72 Gbits/sec  | 769 Mbits/sec   | 221 ms         
    
    iperf3 Network Speed Tests (IPv6):
    ---------------------------------
    Provider        | Location (Link)           | Send Speed      | Recv Speed      | Ping           
    -----           | -----                     | ----            | ----            | ----           
    Clouvider       | London, UK (10G)          | 4.84 Gbits/sec  | 2.40 Gbits/sec  | 34.8 ms        
    Eranium         | Amsterdam, NL (100G)      | 5.35 Gbits/sec  | 4.26 Gbits/sec  | 31.3 ms        
    Uztelecom       | Tashkent, UZ (10G)        | 4.98 Gbits/sec  | 1.44 Gbits/sec  | 103 ms         
    Leaseweb        | Singapore, SG (10G)       | 3.04 Gbits/sec  | 1.47 Gbits/sec  | 164 ms         
    Clouvider       | Los Angeles, CA, US (10G) | 927 Mbits/sec   | 762 Mbits/sec   | 169 ms         
    Leaseweb        | NYC, NY, US (10G)         | 4.70 Gbits/sec  | 2.24 Gbits/sec  | 113 ms         
    Edgoo           | Sao Paulo, BR (1G)        | busy            | 659 Mbits/sec   | 221 ms         
    
    Geekbench 6 Benchmark Test:
    ---------------------------------
    Test            | Value                         
                    |                               
    Single Core     | 803                           
    Multi Core      | 3511                          
    Full Test       | https://browser.geekbench.com/v6/cpu/15548189
    
    YABS completed in 16 min 59 sec
    
    

    Any idea which location the storage plans (if made available) will be in?

    No real plan for them yet.

    I like to keep hardware as consistent as possible between locations and so far only have big storage in Bulgaria and in Kansas City. Actually have had a storage server racked in KC for a few months now, just haven't spun it up... But it was never meant to be used for public service.

    Thanked by 1ServerBachelor
  • edited December 2025

    @MannDude said:

    @ServerBachelor said:

    @MannDude said:
    Getting around to working on the storage stuff.

    10TB HDD box, 8vCPU and 16GB RAM. 5Gbps port cap. Not bad.

    No guarantee we'll actually offer any storage servers long term but I've got a big box online. Let me see what I have leftover after doing things like setting up some crypto nodes (We run https://xmr.gd - But I want to run some LTC, ZCash and other nodes too).

    # ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## #
    #              Yet-Another-Bench-Script              #
    #                     v2025-04-20                    #
    # https://github.com/masonr/yet-another-bench-script #
    # ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## #
    
    Sat Dec 13 12:33:54 PM GMT 2025
    
    Basic System Information:
    ---------------------------------
    Uptime     : 0 days, 0 hours, 4 minutes
    Processor  : Intel(R) Xeon(R) CPU E5-2650 v4 @ 2.20GHz
    CPU cores  : 8 @ 2199.996 MHz
    AES-NI     : ✔ Enabled
    VM-x/AMD-V : ✔ Enabled
    RAM        : 15.6 GiB
    Swap       : 4.0 GiB
    Disk       : 9.6 TiB
    Distro     : Debian GNU/Linux 13 (trixie)
    Kernel     : 6.17.12-x64v3-xanmod1
    VM Type    : KVM
    IPv4/IPv6  : ✔ Online / ✔ Online
    
    IPv6 Network Information:
    ---------------------------------
    ISP        : IncogNet LLC
    ASN        : AS40663 IncogNet LLC
    Host       : IncogNET LLC
    Location   : Sofia, Sofia-Capital (22)
    Country    : Bulgaria
    
    fio Disk Speed Tests (Mixed R/W 50/50) (Partition /dev/vda3):
    ---------------------------------
    Block Size | 4k            (IOPS) | 64k           (IOPS)
      ------   | ---            ----  | ----           ---- 
    Read       | 74.63 MB/s   (18.6k) | 959.03 MB/s  (14.9k)
    Write      | 74.83 MB/s   (18.7k) | 964.07 MB/s  (15.0k)
    Total      | 149.47 MB/s  (37.3k) | 1.92 GB/s    (30.0k)
               |                      |                     
    Block Size | 512k          (IOPS) | 1m            (IOPS)
      ------   | ---            ----  | ----           ---- 
    Read       | 1.80 GB/s     (3.5k) | 1.31 GB/s     (1.2k)
    Write      | 1.90 GB/s     (3.7k) | 1.39 GB/s     (1.3k)
    Total      | 3.70 GB/s     (7.2k) | 2.70 GB/s     (2.6k)
    
    iperf3 Network Speed Tests (IPv4):
    ---------------------------------
    Provider        | Location (Link)           | Send Speed      | Recv Speed      | Ping           
    -----           | -----                     | ----            | ----            | ----           
    Clouvider       | London, UK (10G)          | 5.06 Gbits/sec  | 2.06 Gbits/sec  | 35.1 ms        
    Eranium         | Amsterdam, NL (100G)      | 5.31 Gbits/sec  | 4.33 Gbits/sec  | 31.3 ms        
    Uztelecom       | Tashkent, UZ (10G)        | 5.01 Gbits/sec  | 1.47 Gbits/sec  | 103 ms         
    Leaseweb        | Singapore, SG (10G)       | 3.43 Gbits/sec  | 488 Mbits/sec   | 164 ms         
    Clouvider       | Los Angeles, CA, US (10G) | 1.03 Gbits/sec  | 338 Mbits/sec   | 169 ms         
    Leaseweb        | NYC, NY, US (10G)         | 4.93 Gbits/sec  | 1.10 Gbits/sec  | 113 ms         
    Edgoo           | Sao Paulo, BR (1G)        | 3.72 Gbits/sec  | 769 Mbits/sec   | 221 ms         
    
    iperf3 Network Speed Tests (IPv6):
    ---------------------------------
    Provider        | Location (Link)           | Send Speed      | Recv Speed      | Ping           
    -----           | -----                     | ----            | ----            | ----           
    Clouvider       | London, UK (10G)          | 4.84 Gbits/sec  | 2.40 Gbits/sec  | 34.8 ms        
    Eranium         | Amsterdam, NL (100G)      | 5.35 Gbits/sec  | 4.26 Gbits/sec  | 31.3 ms        
    Uztelecom       | Tashkent, UZ (10G)        | 4.98 Gbits/sec  | 1.44 Gbits/sec  | 103 ms         
    Leaseweb        | Singapore, SG (10G)       | 3.04 Gbits/sec  | 1.47 Gbits/sec  | 164 ms         
    Clouvider       | Los Angeles, CA, US (10G) | 927 Mbits/sec   | 762 Mbits/sec   | 169 ms         
    Leaseweb        | NYC, NY, US (10G)         | 4.70 Gbits/sec  | 2.24 Gbits/sec  | 113 ms         
    Edgoo           | Sao Paulo, BR (1G)        | busy            | 659 Mbits/sec   | 221 ms         
    
    Geekbench 6 Benchmark Test:
    ---------------------------------
    Test            | Value                         
                    |                               
    Single Core     | 803                           
    Multi Core      | 3511                          
    Full Test       | https://browser.geekbench.com/v6/cpu/15548189
    
    YABS completed in 16 min 59 sec
    
    

    Any idea which location the storage plans (if made available) will be in?

    No real plan for them yet.

    I like to keep hardware as consistent as possible between locations and so far only have big storage in Bulgaria and in Kansas City. Actually have had a storage server racked in KC for a few months now, just haven't spun it up... But it was never meant to be used for public service.

    Fair enough.

    In case it affects your decision regarding whether to do the storage plans or not, I would be happy with an HDD of even just 100 GB (with SSD for the operating system ofc), as long as the price was reasonable.

    I know storage is usually more, but if 1+ TB feels gratuitous, I'm sure there's a market for plans like that at a comparable price to the existing NVMe VPSes.

    Edit:

    I do regret cancelling my 2024 BF server with 30 GB SSD + 300 GB HDD in Liberty Lake. But I had wanted to change my IPv4 address and didn't think that was possible. Oh well. :(

  • MannDudeMannDude Patron Provider, Veteran
    edited December 2025

    Still a hidden product, at least until I get some more documentation written and KB updated... but if anyone was interested in the DNS product:

    https://portal.incognet.io/store/dns-hosting/incogdns-premium

    Use code: HCZN8M7XT4 for 100% off the first year. Will renew at $5/yr.

    As I said before: Is it better than Cloudflare? dns.he.net? Your domain registrar's included DNS? Probably not... honestly.

    But it's there if you'd like to use it.

    • DNSSEC works. Automatic key generation and management, click-to-check DNSSEC status, Real-time DS records for registrar integration, Support for all standard algorithms.
    • Unlimited records per zone (unless I have reason to limit it...)
    • Setup is fairly common. First two NS are anycast. It's just 4 POPs (Frantech). Third NS is in NYC, DDoS protected. Fourth NS, also in NYC, DDoS protected from a different provider than the other one. Ideally, a relatively resilient setup that balances some basic performance for US/EU queries with some redundancies in place. This will more than likely expand and become a much better product as time moves forward.
    • A, AAAA, CNAME, MX, TXT, SRV, CAA, NS, TLSA, SOA records only at the moment
    • Import Zone Option ( merge, replace, append ... existing records preserved when merging )
    • Export Zone option (to BIND/RFC1035 format)
    • Still need to make some UI tweaks and do some documentation for the KB.
    • This is also the same DNS system used for new domain name purchases .
    • Old domain registrations using the old DNS system have been automatically ported over to the new system and DNS cluster without service impact. This new DNS manager is more lightweight and easier to use than the old system, and this new system introduces features that the old DNS cluster did not support such as DNSSEC. The old nameservers work on the new DNS cluster, though we may swap them to the new NS hostnames ourselves for domains registered with us using the old nameservers sometime in the next year. Won't have any impact on your service.
  • @MannDude said:
    Still a hidden product, at least until I get some more documentation written and KB updated... but if anyone was interested in the DNS product:

    https://portal.incognet.io/store/dns-hosting/incogdns-premium

    Use code: HCZN8M7XT4 for 100% off the first year. Will renew at $5/yr.

    As I said before: Is it better than Cloudflare? dns.he.net? Your domain registrar's included DNS? Probably not... honestly.

    But it's there if you'd like to use it.

    • DNSSEC works. Automatic key generation and management, click-to-check DNSSEC status, Real-time DS records for registrar integration, Support for all standard algorithms.
    • Unlimited records per zone (unless I have reason to limit it...)
    • Setup is fairly common. First two NS are anycast. It's just 4 POPs (Frantech). Third NS is in NYC, DDoS protected. Fourth NS, also in NYC, DDoS protected from a different provider than the other one. Ideally, a relatively resilient setup that balances some basic performance for US/EU queries with some redundancies in place. This will more than likely expand and become a much better product as time moves forward.
    • A, AAAA, CNAME, MX, TXT, SRV, CAA, NS, TLSA, SOA records only at the moment
    • Import Zone Option ( merge, replace, append ... existing records preserved when merging )
    • Export Zone option (to BIND/RFC1035 format)
    • Still need to make some UI tweaks and do some documentation for the KB.
    • This is also the same DNS system used for new domain name purchases .
    • Old domain registrations using the old DNS system have been automatically ported over to the new system and DNS cluster without service impact. This new DNS manager is more lightweight and easier to use than the old system, and this new system introduces features that the old DNS cluster did not support such as DNSSEC. The old nameservers work on the new DNS cluster, though we may swap them to the new NS hostnames ourselves for domains registered with us using the old nameservers sometime in the next year. Won't have any impact on your service.

    Is there any possibility to create custom nameservers? (vanity)

  • plumbergplumberg Veteran, Megathread Squad

    @MannDude said:
    Still a hidden product, at least until I get some more documentation written and KB updated... but if anyone was interested in the DNS product:

    https://portal.incognet.io/store/dns-hosting/incogdns-premium

    Use code: HCZN8M7XT4 for 100% off the first year. Will renew at $5/yr.

    As I said before: Is it better than Cloudflare? dns.he.net? Your domain registrar's included DNS? Probably not... honestly.

    But it's there if you'd like to use it.

    • DNSSEC works. Automatic key generation and management, click-to-check DNSSEC status, Real-time DS records for registrar integration, Support for all standard algorithms.
    • Unlimited records per zone (unless I have reason to limit it...)
    • Setup is fairly common. First two NS are anycast. It's just 4 POPs (Frantech). Third NS is in NYC, DDoS protected. Fourth NS, also in NYC, DDoS protected from a different provider than the other one. Ideally, a relatively resilient setup that balances some basic performance for US/EU queries with some redundancies in place. This will more than likely expand and become a much better product as time moves forward.
    • A, AAAA, CNAME, MX, TXT, SRV, CAA, NS, TLSA, SOA records only at the moment
    • Import Zone Option ( merge, replace, append ... existing records preserved when merging )
    • Export Zone option (to BIND/RFC1035 format)
    • Still need to make some UI tweaks and do some documentation for the KB.
    • This is also the same DNS system used for new domain name purchases .
    • Old domain registrations using the old DNS system have been automatically ported over to the new system and DNS cluster without service impact. This new DNS manager is more lightweight and easier to use than the old system, and this new system introduces features that the old DNS cluster did not support such as DNSSEC. The old nameservers work on the new DNS cluster, though we may swap them to the new NS hostnames ourselves for domains registered with us using the old nameservers sometime in the next year. Won't have any impact on your service.

    Kool

    Limited to one domain only?

  • MannDudeMannDude Patron Provider, Veteran

    @COLBYLICIOUS said:

    @MannDude said:
    Still a hidden product, at least until I get some more documentation written and KB updated... but if anyone was interested in the DNS product:

    https://portal.incognet.io/store/dns-hosting/incogdns-premium

    Use code: HCZN8M7XT4 for 100% off the first year. Will renew at $5/yr.

    As I said before: Is it better than Cloudflare? dns.he.net? Your domain registrar's included DNS? Probably not... honestly.

    But it's there if you'd like to use it.

    • DNSSEC works. Automatic key generation and management, click-to-check DNSSEC status, Real-time DS records for registrar integration, Support for all standard algorithms.
    • Unlimited records per zone (unless I have reason to limit it...)
    • Setup is fairly common. First two NS are anycast. It's just 4 POPs (Frantech). Third NS is in NYC, DDoS protected. Fourth NS, also in NYC, DDoS protected from a different provider than the other one. Ideally, a relatively resilient setup that balances some basic performance for US/EU queries with some redundancies in place. This will more than likely expand and become a much better product as time moves forward.
    • A, AAAA, CNAME, MX, TXT, SRV, CAA, NS, TLSA, SOA records only at the moment
    • Import Zone Option ( merge, replace, append ... existing records preserved when merging )
    • Export Zone option (to BIND/RFC1035 format)
    • Still need to make some UI tweaks and do some documentation for the KB.
    • This is also the same DNS system used for new domain name purchases .
    • Old domain registrations using the old DNS system have been automatically ported over to the new system and DNS cluster without service impact. This new DNS manager is more lightweight and easier to use than the old system, and this new system introduces features that the old DNS cluster did not support such as DNSSEC. The old nameservers work on the new DNS cluster, though we may swap them to the new NS hostnames ourselves for domains registered with us using the old nameservers sometime in the next year. Won't have any impact on your service.

    Is there any possibility to create custom nameservers? (vanity)

    Not yet. Could probably do this manually, however.

    @plumberg said:

    @MannDude said:
    Still a hidden product, at least until I get some more documentation written and KB updated... but if anyone was interested in the DNS product:

    https://portal.incognet.io/store/dns-hosting/incogdns-premium

    Use code: HCZN8M7XT4 for 100% off the first year. Will renew at $5/yr.

    As I said before: Is it better than Cloudflare? dns.he.net? Your domain registrar's included DNS? Probably not... honestly.

    But it's there if you'd like to use it.

    • DNSSEC works. Automatic key generation and management, click-to-check DNSSEC status, Real-time DS records for registrar integration, Support for all standard algorithms.
    • Unlimited records per zone (unless I have reason to limit it...)
    • Setup is fairly common. First two NS are anycast. It's just 4 POPs (Frantech). Third NS is in NYC, DDoS protected. Fourth NS, also in NYC, DDoS protected from a different provider than the other one. Ideally, a relatively resilient setup that balances some basic performance for US/EU queries with some redundancies in place. This will more than likely expand and become a much better product as time moves forward.
    • A, AAAA, CNAME, MX, TXT, SRV, CAA, NS, TLSA, SOA records only at the moment
    • Import Zone Option ( merge, replace, append ... existing records preserved when merging )
    • Export Zone option (to BIND/RFC1035 format)
    • Still need to make some UI tweaks and do some documentation for the KB.
    • This is also the same DNS system used for new domain name purchases .
    • Old domain registrations using the old DNS system have been automatically ported over to the new system and DNS cluster without service impact. This new DNS manager is more lightweight and easier to use than the old system, and this new system introduces features that the old DNS cluster did not support such as DNSSEC. The old nameservers work on the new DNS cluster, though we may swap them to the new NS hostnames ourselves for domains registered with us using the old nameservers sometime in the next year. Won't have any impact on your service.

    Kool

    Limited to one domain only?

    For the time being, yes. It's more of an add-on to our existing domain service than anything, but wanted to give the option for one-off use for domains not registered through us.

    Thanked by 1plumberg
  • JohnFilch123JohnFilch123 Member
    edited December 2025

    Would you consider making a toggle switch or something to limit resolving to a particular geo region? Like US only or EU only?

    Also, any chance to have auto failover?

  • I see the client portal makeover is finally live

    Thanked by 1MannDude
  • tentortentor Member, Host Rep

    @JohnFilch123 said:
    Would you consider making a toggle switch or something to limit resolving to a particular geo region? Like US only or EU only?

    I wonder what's the use case?

    Thanked by 1stxsh
  • @tentor said: I wonder what's the use case?

    Data control.

  • tentortentor Member, Host Rep

    @JohnFilch123 said:

    @tentor said: I wonder what's the use case?

    Data control.

    Not sure if it helps much given popularity of both VPNs and Tor network.

    Why not use geoblocking at the web server, what benefit do you expect from offloading it to DNS?

  • @tentor said: Why not use geoblocking at the web server, what benefit do you expect from offloading it to DNS?

    We are talking about different things I think. I am talking about having my dns records stored in a particular geo region.

    Thanked by 1tentor
  • @grayblanket said:
    I am not sure about the experience of others, but I have given up some months ago with Incognet, given trouble with the service and no clarity on ticket response.

    Basically, from what I could understand, the ticket system is on the basis that you create a ticket and wait for them to reply. If you follow up, it will go back to the end of the queue. And there is no way to tell when they will reply.

    I now have a few idling VMs that have been paid up for years. Anyone wants them, please contact me.

    I still have these VMs, if anyone is interested. A few people contacted me, but ultimately there were no takers. I only ask for those interested to make me an offer which they consider to be fair.

    Thanked by 1oloke
  • MannDudeMannDude Patron Provider, Veteran
    edited December 2025

    @grayblanket said:

    @grayblanket said:
    I am not sure about the experience of others, but I have given up some months ago with Incognet, given trouble with the service and no clarity on ticket response.

    Basically, from what I could understand, the ticket system is on the basis that you create a ticket and wait for them to reply. If you follow up, it will go back to the end of the queue. And there is no way to tell when they will reply.

    I now have a few idling VMs that have been paid up for years. Anyone wants them, please contact me.

    I still have these VMs, if anyone is interested. A few people contacted me, but ultimately there were no takers. I only ask for those interested to make me an offer which they consider to be fair.

    I'll buy them back from you and just give you a prorated refund for whatever unusued time there is. 🤷

    Less legacy VMs to eventually migrate to new hardware.

  • @MannDude Great, I have created a ticket about this.

  • MannDudeMannDude Patron Provider, Veteran

    @grayblanket said:
    @MannDude Great, I have created a ticket about this.

    On mobile, read your ticket but will respond when back to my desk. Give me a few hours and I'll get you sorted out.

  • @MannDude said: a hidden product, at least until I get some more documentation written and KB updated... but if anyone was interested in the DNS product

    Love it. Have you considered any sort of bundling offers? For example, easyDNS includes basic mail hosting in their DNS products. (They require DNS hosting and mail hosting to be tied to the same domain name.)

    Thanked by 1MannDude
  • Any plans for VPS restock in the Netherlands?

    Thanked by 1MannDude
  • @MannDude

    Hi there, I recently bought a plan from Incognet. I had one ticket initially asking a question about domain registration that was answered quite promptly but I had another billing question that has not been answered since Dec 7 so getting close to a month. The first time I followed up on the ticket which probably put it back to the end of the queue but I created another ticket with priority high and also no reply for a week. Ticket number 1222J30C0

    I've been very happy with the services themselves but I would not use this for any production sensitive stuff given this experience - I did see the reviews about slow ticket response time on Trustpilot and here and was hoping things had changed given some of the things MannDude was saying here but that looks not to be the case.

    It is frustrating to have to sign up for a LowEndTalk account to communicate with the provider, or in some cases I guess people who gave poor reviews on TrustPilot - there is no other way to contact other than the ticketing system.

    This is a really unique service as I love the fact that it's privacy centric and the service itself seems to great. I understand that it's probably hard being a one man shop and running things. Really hoping that Incognet can solve these ticketing problems in the future so I can give a full recommendation!

  • MannDudeMannDude Patron Provider, Veteran

    @e9b0e426 said:
    @MannDude

    Hi there, I recently bought a plan from Incognet. I had one ticket initially asking a question about domain registration that was answered quite promptly but I had another billing question that has not been answered since Dec 7 so getting close to a month. The first time I followed up on the ticket which probably put it back to the end of the queue but I created another ticket with priority high and also no reply for a week. Ticket number 1222J30C0

    I've been very happy with the services themselves but I would not use this for any production sensitive stuff given this experience - I did see the reviews about slow ticket response time on Trustpilot and here and was hoping things had changed given some of the things MannDude was saying here but that looks not to be the case.

    It is frustrating to have to sign up for a LowEndTalk account to communicate with the provider, or in some cases I guess people who gave poor reviews on TrustPilot - there is no other way to contact other than the ticketing system.

    This is a really unique service as I love the fact that it's privacy centric and the service itself seems to great. I understand that it's probably hard being a one man shop and running things. Really hoping that Incognet can solve these ticketing problems in the future so I can give a full recommendation!

    Sorry, I had read the original ticket before but hadn't yet responded. Sales related requests always get lower priority compared to actual support or service impacting items. (Though most service impacting items that are wide will wake me up via a slew of alerts and get immediate action 99% of the time).

    I'll answer your ticket, which is an inquiry about a custom VPS plan shortly. We don't generally do custom stuff but since you've had to wait a long time I'll accommodate you.

    We're not a one man show but it is mostly me + part time help, but many things still require my review / response. After the New Year we'll be caught back up again.

    Thanked by 1e9b0e426
  • MannDudeMannDude Patron Provider, Veteran
    edited December 2025

    @Turbo_Pascal said:

    @MannDude said: a hidden product, at least until I get some more documentation written and KB updated... but if anyone was interested in the DNS product

    Love it. Have you considered any sort of bundling offers? For example, easyDNS includes basic mail hosting in their DNS products. (They require DNS hosting and mail hosting to be tied to the same domain name.)

    Haven't given it much of a thought. Still have MyPrivateInbox on the backburner but seeing how unrealistic of expectations many of the mail customers are, based on reading LET threads/discussion in regards to NameCrane and MXRoute, I'm not sure I want to dive into that market. "Why does it take 20 seconds for it to arrive to GMail? This is unacceptable!" "Why does it only include XXGB of storage? I can get 500GB of Stroage for $2/yr from the other guys!!!" "what do you mean I can't send unsolicited prescription pill telegram links to 5,000 scraped email addresses at once? I thought you guys were 'pro free speech'!!!?" Etc. :)

    Still, maybe. But based on the conversations regarding the other two guys it seems like a support heavy service with low reward.

    Service was ready to launch last Black Friday but the winds shifted and was bad timing to try to launch. Additionally, we knew at the time we'd be migrating datacenters in the Netherlands (where the service was planned to launch) and thought it'd be in poor taste to launch the service knowing that in a few months we'd be disrupting it for migration. We kept VPS plans out of stock for several months in that POP for that same reason, just to not disrupt any new customers. Turns out it was the right call since the DC migration was an awful experience and the biggest clusterfuck ever and the service disruption lasted much much longer than we had ever anticipated or planned for.

    @ServerBachelor said:
    Any plans for VPS restock in the Netherlands?

    Yes! I think we're still on track for new hardware in the coming week(s). I'll have to check back in on that. Then EU will be stocked up pretty well.

Sign In or Register to comment.