Jump to content

Search the Community

Showing results for tags 'DNS'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • News & Community
    • News & Announcements
    • Feature Ideas & Improvements for DumaOS
    • Community Discussion
  • Support
    • Knowledge Base
    • Latest Firmwares
    • DumaOS on Netduma R2 Support
    • Telstra Game Optimiser Support
    • DumaOS on NETGEAR Nighthawk Support
    • DumaOS on Netduma R1 Support
    • DumaOS Mobile App Support
    • Original Netduma R1 Firmware Support
    • Call of Duty Support
    • New Games for the Geo-Filter
  • Duma Army Lounge
    • Gamer Talk
    • TechnoBabble
    • Off Topic
  • International Language Forums
    • NETDUMA Français
    • NETDUMA Español
    • NETDUMA Deutsch

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Location


Interests


DumaOS Routers Owned


TS Model


Website URL


Skype


Twitter


Discord


Steam


PlayStation Network


Xbox Live


Nintendo Switch


Battle.net


Gamer Type


Favourite Genres


Connection Speed

Found 14 results

  1. Hello all, I recently installed Pi-hole on a Raspberry Pi to use as a local DNS resolver and ad blocker. Normally, in the Pi-hole logs you will see activity broken down by local IP of device (see attachment). With the XR500 all DNS requests are coming through 192.168.1.1 which according to Pi-hole documentation, is potentially the fault of the router. Does anyone know how I can change this? Thanks!
  2. I was reading another members post and read the recommendation to try different dns servers namely cloudflare primary 1.1.1.1 and secondary 1.0.0.1 servers throughout the years even before Netduma existed for me I have always wondered if outside the router level of configuration, at the console level in the network settings do I HAVE to also input those same services within the console software???? Will there be an issue of doing them both? Is it ok?
  3. Hello, Let me begin by saying I've received my router 2 days back and had my hands on it most of my free time since then, it really does have quite a few exciting and promising features. Therefore I see a lot of potential and hopefully there is maturity at the end of the roadmap as well. My main reason for picking it was somewhat seamless VPN capability integration, also this is where I faced most of the issues, therefore this is the area I am going to focus on, especially after going through this forum and seeing that quite a few customers also rely on this functionality in their day to day operations. First, maybe some minor ideas: Power button. I could not find it, neither looking all over the device, nor in the user guide. Did I miss it? You do need to reset your router time from time and the only way to do it is either by connecting to its control panel (that is if it is responding) and doing it there, or trying to unplug it from power supply. Not sure if it's healthy. More templates of established VPN providers (maybe at least Top5?) in basic VPN Setup. It would eliminate a lot of hassle, also reduce support requests that you get around VPN, since it would be tested out, reducing problem surface for users. Especially given it is one of more complicated setups, as per your KB. Resiliency: Reconnecting to the VPN server if connection drops/session expires/etc. Not sure if it is doing it now, but it did not seem like, I need to connect to control panel to reconnect it, or even resubmit all the same details, as connection state simply says Failed. Ability to add more than one VPN server in configuration for service continuity purposes. If one becomes unavailable, it could revert to the next specified. VPN speed. I am sure you know about it, but enabling VPN bleeds native speed provided by router dramatically. Ran couple of tests, kept server the same for consistency purposes (both, VPN server and dest server of speedtest): [VPN] Speed connected with laptop to NetDuma WiFI with Hybrid VPN ON: [NATIVE] Speed connected with laptop to NetDuma WiFI with Hybrid VPN OFF: [NATIVE] Speed connected with laptop to non-Duma router WiFI on same network with no VPN: [VPN] Speed connected with laptop to non-Duma router WiFI with VPN ON via VPN provider's proprietary desktop app: As you can see, NetDuma router beats the other one (Ubiquiti) hands down, but when VPN comes into play, all this native speed advantage is wasted. Desktop VPN app is outperforming, which is disappointing for me. Now, the issues/questions: As I said, I was hoping for seamless VPN integration, with almost like fire and forget configuration, however this was not the case and had to deep dive into making it work. Problem was DNS leak, and managed to fix it only after multiple trial and error attempts, where I found the firmware and upgraded it. Interesting that such issue was still persisting at v.3 However, here came stability problem. It would run for some time, then disconnect, randomly. Not sure what might be causing this, apart from when I login to NordVPN service from another device, on that occasion it seems to drop connection on Duma as well, even if I am connecting to completely different VPN server, through desktop app on a device connected on different WAN. Is this VPN provider problem, or something is glitching on NetDuma? Logs are gone in Hybrid VPN section after upgrading firmware to the latest. It just does not show anything on that tab. Tried firefox, chrome, different devices - nothing. Not critical, but annoying when performing diagnostics. In latest firmware release notes, it says: "Added ability to use specific IPv4/IPv6 DNS in HybridVPN". I do not see such option in HybridVPN section. In Network Settings > WAN > Network > DHCP - Yes, but it was there before. Nothing in HybridVPN related to DNS. What does "Use upstream DNS" exactly mean in this configuration? Is it same as default automatic value on windows network adapter, or with some additional functionality? Asking, because prior to updating to latest firmware, when VPN would be ON, it would use ISP's DNS and would end in DNS leakage, but would at least resolve the requests, however after update, it does not resolve any requests, while on VPN, unless I manually add DNS server addresses of Nord VPN's service. Shouldn't it pick those up automatically, and if not those, then at least ISP default ones? And finally, what is the best configuration to use purely for VPN setup in the router? Maybe there are other ways to solve DNS leakage apart from adding VPN's DNS server addresses manually, or something else I missed? For convenience, I added redacted ovpn file here. Thank you for your input! lt8.nordvpn.com.udp.ovpn
  4. I seem to have lost internet access, and I believe it was my ISP, but anyway I was doing some persistent pings to an IP and eventually it came back up. But none of my PCs can resolve DNS. They are configured for DHCP so the DNS passed down to the clients is the router's IP. For whatever reason the R2 won't allow DNS lookups now. If I statically assign the same DNS servers I have the router configured to use, my PCs can get back on the internet. It just seems the R2 is just borked when it comes to DNS. I've rebooted it twice now via the menu and a hard boot by pulling power for 30 seconds. NSlookup states: *** dumaos.lan can't find google.com: Query refused. It'll accept a query for dumaos.lan and resolve though, though oddly my PC will resolve that to the gateway even if I'm pointing to Google DNS so perhaps that's not coming from DNS. Anyway it seems the router itself seems to be able to resolve external DNS... it's able to do connection benchmarks and I assume DNS is being used to resolve hosts for that purpose? I hope yall didn't statically assign IPs for that.
  5. So I want to change my DNS on my router. The thing is on the XR500 there is a primary, secondary and third DNS. I wanted to use the google DNS of 8.8.8.8 and 8.8.4.4 so what do i do about the third option? Do I leave it blank or does google have a third DNS? Sorry if this is a stupid question I'm not that great for networking lol. Thanks guys.
  6. Id like to be able to set my device dns address via dhcp rather than having the router get queried. example https://emulator.tp-link.com/C9v5_eu_webpages_new/index.html Advanced>network>internet Advanced>dhcp server if I could set it per device, I can use pihole to monitor my network better
  7. Allow resolution of local devices by hostnames. Shouldnt be a need for a seperate DNS server.
  8. This morning when I woke up my Wi-Fi network was not connected to the internet. I went to my R2 and noticed an error message on the system info that mentioned "Maximum number of DNS queries (max:150)" while in the system information I hit the "reset MAC address" button and all of a sudden the issue was resolved? Internet is once again working fine. Can someone please advise me what exactly would have caused this and how I can ensure it doesn't happen again, luckily I was home this morning so I was able to resolve the issue but my wife isn't so tech savvy and would have been without connectivity all day had I not noticed the issues before leaving for work today. current configuration: Bell Home Hub 3000 > R2 >Google Wi-Fi
  9. My internet works fine and i can browse with no problems. But as soon as I start any torrent client( tried with several and with 50% speed limitation) I get a lot of dns lookup errors while trying to browse. So downloads are going through just fine and while trying to browse the web it seems as if there's no internet connection getting dns errors. Already tried changing DNS servers to several other ones but this problem is annoying repeatable. What's the problem here? its been like this for around a week now. I haven't changes anything on my pc software wise and I haven't upgraded any firmware on router this problem just started out of nowhere. Any help would be appreciated! Running: XR500 V2.3.2.56 Windows 10 x64 all browsers tested and same problem. Even other devices on the LAN. Problem is for browsing the Web but downloads / netflix streaming remains unaffected
  10. I've been getting quite a few of these every minute and wanted to make sure something isn't amiss on my network. I do have a Pi-Hole configured with a static address and selected as my DNS server.
  11. Hi, First time posting. I got an XR450 as a gift and it is a big improvement over my old Linksys but I have this weird issue. I have Opendns for the family and when I switch DNS in the DumaOS dashboard I loose internet connection to random devices, NOT wifi. I can switch back to my ISP DNS and then it all comes back. Any ideas? Thanks
  12. Hi there! I'm having issues connecting to Windows from Mac OS 10.14.5 and CentOS 7 1810. Windows hostname lookup & ping from another Windows client - works fine. Looking up Mac and Linux hosts from Mac and Linux - works fine. Looking up any Windows host from Mac or Linux? No buenos are to be had. None anywhere. Some features work, like Microsoft Remote Desktop, but not from command line. Any ideas where to go with this? It's messing with my work. :(
  13. I have noticed a possible error with on the Xr500. I did a dns leak test whilst connected to my vpn provider and noticed a leak. I went and changed dns servers and my connection went dead, not even a reboot would restore the link. I had to start the "setup wizard" in order for the link to be established. I did not have to go through the setup completely just until i put in my pppoe credentials. It is a long time since I did a dns leak test so not too sure if it is the current firmware. I would need other members to try and change dns who have pppoe to know for sure.
  14. Not sure what is happening but I seem to see these every so often in my logs but not this many in one go! [DoS Attack: TCP/UDP Echo] from source: 1.0.0.1, port 53, Saturday, August 18, 2018 10:38:21 [DoS Attack: TCP/UDP Echo] from source: 8.8.8.8, port 53, Saturday, August 18, 2018 10:38:21 [DoS Attack: TCP/UDP Echo] from source: 1.1.1.1, port 53, Saturday, August 18, 2018 10:38:21 [DoS Attack: TCP/UDP Echo] from source: 1.1.1.1, port 53, Saturday, August 18, 2018 10:38:22 [DoS Attack: TCP/UDP Echo] from source: 1.1.1.1, port 53, Saturday, August 18, 2018 10:38:22 [DoS Attack: TCP/UDP Echo] from source: 1.1.1.1, port 53, Saturday, August 18, 2018 10:38:22 [DoS Attack: TCP/UDP Echo] from source: 1.1.1.1, port 53, Saturday, August 18, 2018 10:38:22 [DoS Attack: TCP/UDP Echo] from source: 1.1.1.1, port 53, Saturday, August 18, 2018 10:38:22 [DoS Attack: TCP/UDP Echo] from source: 1.0.0.1, port 53, Saturday, August 18, 2018 10:38:22 [DoS Attack: TCP/UDP Echo] from source: 8.8.8.8, port 53, Saturday, August 18, 2018 10:38:22 [DoS Attack: TCP/UDP Echo] from source: 8.8.8.8, port 53, Saturday, August 18, 2018 10:38:26 [DoS Attack: TCP/UDP Echo] from source: 1.1.1.1, port 53, Saturday, August 18, 2018 10:38:26 [DoS Attack: TCP/UDP Echo] from source: 1.0.0.1, port 53, Saturday, August 18, 2018 10:38:26 [DoS Attack: TCP/UDP Echo] from source: 1.1.1.1, port 53, Saturday, August 18, 2018 10:38:26 [DoS Attack: TCP/UDP Echo] from source: 8.8.8.8, port 53, Saturday, August 18, 2018 10:38:26 [DoS Attack: TCP/UDP Echo] from source: 8.8.8.8, port 53, Saturday, August 18, 2018 10:38:26 [DoS Attack: TCP/UDP Echo] from source: 1.0.0.1, port 53, Saturday, August 18, 2018 10:38:26 [DoS Attack: TCP/UDP Echo] from source: 1.0.0.1, port 53, Saturday, August 18, 2018 10:38:26 [DoS Attack: TCP/UDP Echo] from source: 1.1.1.1, port 53, Saturday, August 18, 2018 10:38:26 [DoS Attack: TCP/UDP Echo] from source: 1.1.1.1, port 53, Saturday, August 18, 2018 10:38:27 [DoS Attack: TCP/UDP Echo] from source: 8.8.8.8, port 53, Saturday, August 18, 2018 10:38:27 [DoS Attack: TCP/UDP Echo] from source: 8.8.8.8, port 53, Saturday, August 18, 2018 10:38:32 [DoS Attack: TCP/UDP Echo] from source: 8.8.8.8, port 53, Saturday, August 18, 2018 10:38:32 [DoS Attack: TCP/UDP Echo] from source: 8.8.8.8, port 53, Saturday, August 18, 2018 10:38:32 [DoS Attack: TCP/UDP Echo] from source: 1.1.1.1, port 53, Saturday, August 18, 2018 10:38:32 [DoS Attack: TCP/UDP Echo] from source: 8.8.8.8, port 53, Saturday, August 18, 2018 10:38:32 [DoS Attack: TCP/UDP Echo] from source: 1.0.0.1, port 53, Saturday, August 18, 2018 10:38:32 [DoS Attack: TCP/UDP Echo] from source: 1.1.1.1, port 53, Saturday, August 18, 2018 10:38:32 [DoS Attack: TCP/UDP Echo] from source: 1.0.0.1, port 53, Saturday, August 18, 2018 10:38:32 [DoS Attack: TCP/UDP Echo] from source: 1.1.1.1, port 53, Saturday, August 18, 2018 10:38:32 [DoS Attack: TCP/UDP Echo] from source: 1.0.0.1, port 53, Saturday, August 18, 2018 10:38:32 [DoS Attack: TCP/UDP Echo] from source: 1.1.1.1, port 53, Saturday, August 18, 2018 10:38:32 [DoS Attack: TCP/UDP Echo] from source: 1.0.0.1, port 53, Saturday, August 18, 2018 10:38:32 [DoS Attack: TCP/UDP Echo] from source: 1.1.1.1, port 53, Saturday, August 18, 2018 10:38:32 [DoS Attack: TCP/UDP Echo] from source: 8.8.8.8, port 53, Saturday, August 18, 2018 10:38:37 [DoS Attack: TCP/UDP Echo] from source: 8.8.8.8, port 53, Saturday, August 18, 2018 10:38:37 [DoS Attack: TCP/UDP Echo] from source: 1.0.0.1, port 53, Saturday, August 18, 2018 10:38:37 [DoS Attack: TCP/UDP Echo] from source: 1.1.1.1, port 53, Saturday, August 18, 2018 10:38:37 [DoS Attack: TCP/UDP Echo] from source: 1.0.0.1, port 53, Saturday, August 18, 2018 10:38:37 [DoS Attack: TCP/UDP Echo] from source: 1.1.1.1, port 53, Saturday, August 18, 2018 10:38:37 [DoS Attack: TCP/UDP Echo] from source: 1.1.1.1, port 53, Saturday, August 18, 2018 10:38:38 [DoS Attack: TCP/UDP Echo] from source: 1.1.1.1, port 53, Saturday, August 18, 2018 10:38:38 [DoS Attack: TCP/UDP Echo] from source: 8.8.8.8, port 53, Saturday, August 18, 2018 10:38:38 [DoS Attack: TCP/UDP Echo] from source: 1.0.0.1, port 53, Saturday, August 18, 2018 10:38:38 [DoS Attack: TCP/UDP Echo] from source: 1.1.1.1, port 53, Saturday, August 18, 2018 10:38:39 [DoS Attack: TCP/UDP Echo] from source: 8.8.8.8, port 53, Saturday, August 18, 2018 10:38:39 [DoS Attack: TCP/UDP Echo] from source: 1.1.1.1, port 53, Saturday, August 18, 2018 10:38:42 [DoS Attack: TCP/UDP Echo] from source: 1.1.1.1, port 53, Saturday, August 18, 2018 10:38:43 [DoS Attack: TCP/UDP Echo] from source: 8.8.8.8, port 53, Saturday, August 18, 2018 10:38:43 [DoS Attack: TCP/UDP Echo] from source: 8.8.8.8, port 53, Saturday, August 18, 2018 10:38:43 [DoS Attack: TCP/UDP Echo] from source: 1.0.0.1, port 53, Saturday, August 18, 2018 10:38:43 [DoS Attack: TCP/UDP Echo] from source: 1.0.0.1, port 53, Saturday, August 18, 2018 10:38:43 [DoS Attack: TCP/UDP Echo] from source: 1.1.1.1, port 53, Saturday, August 18, 2018 10:38:43 [DoS Attack: TCP/UDP Echo] from source: 1.0.0.1, port 53, Saturday, August 18, 2018 10:38:43 [DoS Attack: TCP/UDP Echo] from source: 8.8.8.8, port 53, Saturday, August 18, 2018 10:38:43 [DoS Attack: TCP/UDP Echo] from source: 1.1.1.1, port 53, Saturday, August 18, 2018 10:38:43 [DoS Attack: TCP/UDP Echo] from source: 8.8.8.8, port 53, Saturday, August 18, 2018 10:38:50 [DoS Attack: TCP/UDP Echo] from source: 1.0.0.1, port 53, Saturday, August 18, 2018 10:38:50 [DoS Attack: TCP/UDP Echo] from source: 1.1.1.1, port 53, Saturday, August 18, 2018 10:38:50 [DoS Attack: TCP/UDP Echo] from source: 1.1.1.1, port 53, Saturday, August 18, 2018 10:38:50 [DoS Attack: TCP/UDP Echo] from source: 1.0.0.1, port 53, Saturday, August 18, 2018 10:38:50 [DoS Attack: TCP/UDP Echo] from source: 8.8.8.8, port 53, Saturday, August 18, 2018 10:38:50 [DoS Attack: TCP/UDP Echo] from source: 1.1.1.1, port 53, Saturday, August 18, 2018 10:38:51 [DoS Attack: TCP/UDP Echo] from source: 8.8.8.8, port 53, Saturday, August 18, 2018 10:38:51 [DoS Attack: TCP/UDP Echo] from source: 8.8.8.8, port 53, Saturday, August 18, 2018 10:38:51 [DoS Attack: TCP/UDP Echo] from source: 1.0.0.1, port 53, Saturday, August 18, 2018 10:38:51 [DoS Attack: TCP/UDP Echo] from source: 1.0.0.1, port 53, Saturday, August 18, 2018 10:38:51 [DoS Attack: TCP/UDP Echo] from source: 8.8.8.8, port 53, Saturday, August 18, 2018 10:38:56 [DoS Attack: TCP/UDP Echo] from source: 8.8.8.8, port 53, Saturday, August 18, 2018 10:38:56 [DoS Attack: TCP/UDP Echo] from source: 1.1.1.1, port 53, Saturday, August 18, 2018 10:38:56 [DoS Attack: TCP/UDP Echo] from source: 8.8.8.8, port 53, Saturday, August 18, 2018 10:38:56 [DoS Attack: TCP/UDP Echo] from source: 1.0.0.1, port 53, Saturday, August 18, 2018 10:38:56 [DoS Attack: TCP/UDP Echo] from source: 1.0.0.1, port 53, Saturday, August 18, 2018 10:38:56 [DoS Attack: TCP/UDP Echo] from source: 1.1.1.1, port 53, Saturday, August 18, 2018 10:38:56 [DoS Attack: TCP/UDP Echo] from source: 1.1.1.1, port 53, Saturday, August 18, 2018 10:38:56 [DoS Attack: TCP/UDP Echo] from source: 1.0.0.1, port 53, Saturday, August 18, 2018 10:38:56 [DoS Attack: TCP/UDP Echo] from source: 1.1.1.1, port 53, Saturday, August 18, 2018 10:38:56 [DoS Attack: TCP/UDP Echo] from source: 8.8.8.8, port 53, Saturday, August 18, 2018 10:38:56 [DoS Attack: TCP/UDP Echo] from source: 1.0.0.1, port 53, Saturday, August 18, 2018 10:38:56 [DoS Attack: TCP/UDP Echo] from source: 8.8.8.8, port 53, Saturday, August 18, 2018 10:39:07 [DoS Attack: TCP/UDP Echo] from source: 8.8.8.8, port 53, Saturday, August 18, 2018 10:39:07 [DoS Attack: TCP/UDP Echo] from source: 1.0.0.1, port 53, Saturday, August 18, 2018 10:39:07 [DoS Attack: TCP/UDP Echo] from source: 1.0.0.1, port 53, Saturday, August 18, 2018 10:39:07 [DoS Attack: TCP/UDP Echo] from source: 1.1.1.1, port 53, Saturday, August 18, 2018 10:39:07 [DoS Attack: TCP/UDP Echo] from source: 1.1.1.1, port 53, Saturday, August 18, 2018 10:39:07 Anyone else noticed DoS Attack from their configured DNS servers? Seems like these was DNS responses for DNS requests that was sent from my network, my only assumption is that what ever was sending the DNS requests was not receiving the responses so kept trying and all the DNS servers was trying to send the responses back??? Cheers,
×
×
  • Create New...