Jump to content

Search the Community

Showing results for tags 'dns'.



More search options

  • 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 10 results

  1. 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
  2. Allow resolution of local devices by hostnames. Shouldnt be a need for a seperate DNS server.
  3. 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
  4. 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!
  5. 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
  6. 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.
  7. 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
  8. 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. :(
  9. 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.
  10. 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...