DNS requests are crashing my router
apple Verified ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Hello
My ISPs DNS server is replying to requests that originate from my LAN! This keeps crashing my router. Ive attached some of the log files from my router to show you what i mean. Does anyone know if this is something wrong with my DNS settings on the server please?
194.72.0.98 is my USPs DNS server and 81.136.xxx.xxx is my fixed WAN address.
Thanks for your time
Warren
Thu 2009-11-26 15:06:52 UDP flood From 194.72.0.98 port:53 To 81.136.xxx.xxx port:1471 droped
Thu 2009-11-26 15:06:52 UDP flood From 194.72.0.98 port:53 To 81.136.xxx.xxx port:1472 droped
Thu 2009-11-26 15:06:53 UDP flood From 194.72.0.98 port:53 To 81.136.xxx.xxx port:1473 droped
Thu 2009-11-26 15:19:19 UDP flood From 194.72.0.98 port:53 To 81.136.xxx.xxx port:2003 droped
Thu 2009-11-26 15:19:20 UDP flood From 194.72.0.98 port:53 To 81.136.xxx.xxx port:2005 droped
Thu 2009-11-26 15:19:20 UDP flood From 194.72.0.98 port:53 To 81.136.xxx.xxx port:2006 droped
Thu 2009-11-26 15:19:21 UDP flood From 194.72.0.98 port:53 To 81.136.xxx.xxx port:2007 droped
Thu 2009-11-26 15:19:21 UDP flood From 194.72.0.98 port:53 To 81.136.xxx.xxx port:2008 droped
Thu 2009-11-26 15:19:21 UDP flood From 194.72.0.98 port:53 To 81.136.xxx.xxx port:2009 droped
Thu 2009-11-26 15:19:21 UDP flood From 194.72.0.98 port:53 To 81.136.xxx.xxx port:2010 droped
Thu 2009-11-26 15:19:24 UDP flood From 194.72.0.98 port:53 To 81.136.xxx.xxx port:2011 droped
Thu 2009-11-26 15:19:26 UDP flood From 194.72.0.98 port:53 To 81.136.xxx.xxx port:2012 droped
Thu 2009-11-26 15:19:26 UDP flood From 194.72.0.98 port:53 To 81.136.xxx.xxx port:2013 droped
Thu 2009-11-26 15:19:27 UDP flood From 194.72.0.98 port:53 To 81.136.xxx.xxx port:2014 droped
5 replies
Sign in or join Beachball Help to reply.
- 0
Apple Support Community member ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Does anyone know if this is something wrong with my DNS settings on the server please?
There's no way to tell from the information available.
Clearly this looks like one (or more) internal clients are using your ISP's DNS server for name resolution.
Whether that's 'right' or not depends on your network setup. Do you expect your clients to use your ISP's DNS server? Do you have an internal DNS server that you want/expect the clients to use?
If you are expecting to use an internal DNS server then you need to check each of your internal systems to see which one(s) are configured to use your ISP's server rather than your own.
It's also possible that your network configuration is wrong and that your own DNS server is generating this traffic, but that's the next step once you work out whether the traffic is expected/desired or not.
- 0
Apple Support Community member ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Thanks Camelot.
This has only started in the last few days and is not expected. There is a new mac in the studio as of last week and ill check that is using the internal server for DNS - it should be as the server handles DHCP.
The DNS Server is only setup with a single Primary Zone containing a single machine record for the server itself and obviously the reverse mapping.
In the settings ive added the router ip address in the forwarder IP addresses and one of our ISP DNS server addresses - 194.72.9.34 (which sometimes appears on my log)
At the moment my Router is telling me that its using DNS servers 194.72.0.98 and 194.74.65.68. The first address is one i am having issues with!
First thing to notice is that the forward DNS i have entered is different from the ones in my router, should i change this?
Should i forward all port 53 traffic on my router to my server?
Thanks so much for your help
Warren
- 0
Apple Support Community member ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Ive just picked this log up from my DNS on the server, it seems to contain loads of host unreachable stuff - does this shed any light on my problem?
AAA/IN': 2001:503:ba3e::2:30#53
27-Nov-2009 09:04:58.799 host unreachable resolving 'ns4.dnsmadeeasy.com/A/IN': 2001:503:ba3e::2:30#53
27-Nov-2009 09:04:58.799 host unreachable resolving 'ns4.dnsmadeeasy.com/AAAA/IN': 2001:503:ba3e::2:30#53
27-Nov-2009 09:05:00.856 host unreachable resolving 'b.iana-servers.org/AAAA/IN': 2001:500:c::1#53
27-Nov-2009 09:05:00.856 host unreachable resolving 'b.iana-servers.org/AAAA/IN': 2001:500:48::1#53
27-Nov-2009 09:05:00.857 host unreachable resolving 'ns.icann.org/AAAA/IN': 2001:500:c::1#53
27-Nov-2009 09:05:00.857 host unreachable resolving 'ns.icann.org/AAAA/IN': 2001:500:48::1#53
27-Nov-2009 09:05:01.657 host unreachable resolving 'b.iana-servers.org/AAAA/IN': 2001:500:b::1#53
27-Nov-2009 09:05:01.657 host unreachable resolving 'ns.icann.org/AAAA/IN': 2001:500:b::1#53
27-Nov-2009 09:05:02.457 host unreachable resolving 'b.iana-servers.org/AAAA/IN': 2001:500:40::1#53
27-Nov-2009 09:05:02.457 host unreachable resolving 'ns.icann.org/AAAA/IN': 2001:500:40::1#53
27-Nov-2009 09:05:04.057 host unreachable resolving 'b.iana-servers.org/AAAA/IN': 2001:500:f::1#53
27-Nov-2009 09:05:04.058 host unreachable resolving 'ns.icann.org/AAAA/IN': 2001:500:f::1#53
27-Nov-2009 09:05:04.857 host unreachable resolving 'b.iana-servers.org/AAAA/IN': 2001:500:e::1#53
27-Nov-2009 09:05:04.858 host unreachable resolving 'ns.icann.org/AAAA/IN': 2001:500:e::1#53
27-Nov-2009 09:10:54.005 host unreachable resolving 'blackhole-1.iana.org/A/IN': 2001:648:2c30::1:10#53
27-Nov-2009 09:10:54.005 host unreachable resolving 'blackhole-1.iana.org/AAAA/IN': 2001:648:2c30::1:10#53
27-Nov-2009 09:10:54.006 host unreachable resolving 'blackhole-2.iana.org/A/IN': 2001:648:2c30::1:10#53
27-Nov-2009 09:10:54.006 host unreachable resolving 'blackhole-2.iana.org/AAAA/IN': 2001:648:2c30::1:10#53
27-Nov-2009 09:11:15.606 host unreachable resolving 'b.iana-servers.org/AAAA/IN': 2001:500:48::1#53
27-Nov-2009 09:11:15.606 host unreachable resolving 'ns.icann.org/AAAA/IN': 2001:500:48::1#53
27-Nov-2009 09:11:17.206 host unreachable resolving 'b.iana-servers.org/AAAA/IN': 2001:500:b::1#53
27-Nov-2009 09:11:17.206 host unreachable resolving 'b.iana-servers.org/AAAA/IN': 2001:500:40::1#53
27-Nov-2009 09:11:17.206 host unreachable resolving 'b.iana-servers.org/AAAA/IN': 2001:500:c::1#53
27-Nov-2009 09:11:17.206 host unreachable resolving 'ns.icann.org/AAAA/IN': 2001:500:b::1#53
27-Nov-2009 09:11:17.207 host unreachable resolving 'ns.icann.org/AAAA/IN': 2001:500:40::1#53
27-Nov-2009 09:11:17.207 host unreachable resolving 'ns.icann.org/AAAA/IN': 2001:500:c::1#53
27-Nov-2009 09:11:18.006 host unreachable resolving 'b.iana-servers.org/AAAA/IN': 2001:500:f::1#53
27-Nov-2009 09:11:18.007 host unreachable resolving 'b.iana-servers.org/AAAA/IN': 2001:500:e::1#53
27-Nov-2009 09:11:18.007 host unreachable resolving 'ns.icann.org/AAAA/IN': 2001:500:f::1#53
27-Nov-2009 09:11:18.007 host unreachable resolving 'ns.icann.org/AAAA/IN': 2001:500:e::1#53
27-Nov-2009 09:12:57.404 host unreachable resolving 'ns1.dynamicnetworkservices.net/AAAA/IN': 2001:503:c27::2:30#53
27-Nov-2009 09:12:57.404 host unreachable resolving 'ns1.dynamicnetworkservices.net/AAAA/IN': 2001:500:1::803f:235#53
27-Nov-2009 09:12:57.404 host unreachable resolving 'ns1.dynamicnetworkservices.net/AAAA/IN': 2001:7fd::1#53
27-Nov-2009 09:12:57.404 host unreachable resolving 'ns1.dynamicnetworkservices.net/AAAA/IN': 2001:500:3::42#53
27-Nov-2009 09:12:57.404 host unreachable resolving 'ns1.dynamicnetworkservices.net/AAAA/IN': 2001:dc3::35#53
27-Nov-2009 09:12:57.404 host unreachable resolving 'ns2.dynamicnetworkservices.net/AAAA/IN': 2001:503:c27::2:30#53
27-Nov-2009 09:12:57.404 host unreachable resolving 'ns2.dynamicnetworkservices.net/AAAA/IN': 2001:500:1::803f:235#53
27-Nov-2009 09:12:57.404 host unreachable resolving 'ns3.dynamicnetworkservices.net/AAAA/IN': 2001:503:c27::2:30#53
27-Nov-2009 09:12:57.404 host unreachable resolving 'ns3.dynamicnetworkservices.net/AAAA/IN': 2001:500:1::803f:235#53
27-Nov-2009 09:12:57.405 host unreachable resolving 'ns4.dynamicnetworkservices.net/AAAA/IN': 2001:503:c27::2:30#53
27-Nov-2009 09:12:57.405 host unreachable resolving 'ns4.dynamicnetworkservices.net/AAAA/IN': 2001:500:1::803f:235#53
27-Nov-2009 09:12:57.405 host unreachable resolving 'ns2.dynamicnetworkservices.net/AAAA/IN': 2001:7fd::1#53
27-Nov-2009 09:12:57.405 host unreachable resolving 'ns2.dynamicnetworkservices.net/AAAA/IN': 2001:500:3::42#53
27-Nov-2009 09:12:57.405 host unreachable resolving 'ns2.dynamicnetworkservices.net/AAAA/IN': 2001:dc3::35#53
27-Nov-2009 09:12:57.405 host unreachable resolving 'ns3.dynamicnetworkservices.net/AAAA/IN': 2001:7fd::1#53
27-Nov-2009 09:12:57.405 host unreachable resolving 'ns3.dynamicnetworkservices.net/AAAA/IN': 2001:500:3::42#53
27-Nov-2009 09:12:57.405 host unreachable resolving 'ns3.dynamicnetworkservices.net/AAAA/IN': 2001:dc3::35#53
27-Nov-2009 09:12:57.405 host unreachable resolving 'ns4.dynamicnetworkservices.net/AAAA/IN': 2001:7fd::1#53
27-Nov-2009 09:12:57.405 host unreachable resolving 'ns4.dynamicnetworkservices.net/AAAA/IN': 2001:500:3::42#53
27-Nov-2009 09:12:57.406 host unreachable resolving 'ns4.dynamicnetworkservices.net/AAAA/IN': 2001:dc3::35#53
27-Nov-2009 09:14:58.441 host unreachable resolving 'aznwebsr1.aznnet.com/AAAA/IN': 2001:500:2f::f#53
27-Nov-2009 09:14:58.441 host unreachable resolving 'ns2.dnsmadeeasy.com/A/IN': 2001:500:2f::f#53
27-Nov-2009 09:14:58.441 host unreachable resolving 'ns2.dnsmadeeasy.com/AAAA/IN': 2001:500:2f::f#53
27-Nov-2009 09:14:58.442 host unreachable resolving 'ns3.dnsmadeeasy.com/A/IN': 2001:500:2f::f#53
27-Nov-2009 09:14:58.442 host unreachable resolving 'ns3.dnsmadeeasy.com/AAAA/IN': 2001:500:2f::f#53
27-Nov-2009 09:14:58.442 host unreachable resolving 'ns4.dnsmadeeasy.com/A/IN': 2001:500:2f::f#53
27-Nov-2009 09:14:58.442 host unreachable resolving 'ns4.dnsmadeeasy.com/AAAA/IN': 2001:500:2f::f#53
27-Nov-2009 09:15:00.842 host unreachable resolving 'aznwebsr1.aznnet.com/AAAA/IN': 2001:503:ba3e::2:30#53
27-Nov-2009 09:15:00.843 host unreachable resolving 'ns2.dnsmadeeasy.com/A/IN': 2001:503:ba3e::2:30#53
27-Nov-2009 09:15:00.843 host unreachable resolving 'ns2.dnsmadeeasy.com/AAAA/IN': 2001:503:ba3e::2:30#53
27-Nov-2009 09:15:00.843 host unreachable resolving 'ns3.dnsmadeeasy.com/A/IN': 2001:503:ba3e::2:30#53
27-Nov-2009 09:15:00.843 host unreachable resolving 'ns3.dnsmadeeasy.com/AAAA/IN': 2001:503:ba3e::2:30#53
27-Nov-2009 09:15:00.843 host unreachable resolving 'ns4.dnsmadeeasy.com/A/IN': 2001:503:ba3e::2:30#53
27-Nov-2009 09:15:00.843 host unreachable resolving 'ns4.dnsmadeeasy.com/AAAA/IN': 2001:503:ba3e::2:30#53
27-Nov-2009 09:17:08.613 host unreachable resolving 'blackhole-1.iana.org/A/IN': 2001:648:2c30::1:10#53
27-Nov-2009 09:17:08.613 host unreachable resolving 'blackhole-1.iana.org/AAAA/IN': 2001:648:2c30::1:10#53
27-Nov-2009 09:17:08.614 host unreachable resolving 'blackhole-2.iana.org/A/IN': 2001:648:2c30::1:10#53
27-Nov-2009 09:17:08.614 host unreachable resolving 'blackhole-2.iana.org/AAAA/IN': 2001:648:2c30::1:10#53
27-Nov-2009 09:17:30.215 host unreachable resolving 'b.iana-servers.org/AAAA/IN': 2001:500:48::1#53
27-Nov-2009 09:17:30.215 host unreachable resolving 'ns.icann.org/AAAA/IN': 2001:500:48::1#53
27-Nov-2009 09:17:31.815 host unreachable resolving 'b.iana-servers.org/AAAA/IN': 2001:500:b::1#53
27-Nov-2009 09:17:31.815 host unreachable resolving 'b.iana-servers.org/AAAA/IN': 2001:500:40::1#53
27-Nov-2009 09:17:31.815 host unreachable resolving 'b.iana-servers.org/AAAA/IN': 2001:500:c::1#53
27-Nov-2009 09:17:31.815 host unreachable resolving 'ns.icann.org/AAAA/IN': 2001:500:b::1#53
27-Nov-2009 09:17:31.815 host unreachable resolving 'ns.icann.org/AAAA/IN': 2001:500:40::1#53
27-Nov-2009 09:17:31.816 host unreachable resolving 'ns.icann.org/AAAA/IN': 2001:500:c::1#53
27-Nov-2009 09:17:32.615 host unreachable resolving 'b.iana-servers.org/AAAA/IN': 2001:500:f::1#53
27-Nov-2009 09:17:32.615 host unreachable resolving 'b.iana-servers.org/AAAA/IN': 2001:500:e::1#53
27-Nov-2009 09:17:32.616 host unreachable resolving 'ns.icann.org/AAAA/IN': 2001:500:f::1#53
27-Nov-2009 09:17:32.616 host unreachable resolving 'ns.icann.org/AAAA/IN': 2001:500:e::1#53
27-Nov-2009 09:20:55.223 connection refused resolving 'secure.logmein.com/A/IN': 192.168.1.1#53
27-Nov-2009 09:20:55.223 connection refused resolving 'host-delay.logmein-gateway.com/A/IN': 192.168.1.1#53
27-Nov-2009 09:35:51.170 freezing all zones: success
27-Nov-2009 09:35:51.335 loading configuration from '/private/etc/named.conf'
27-Nov-2009 09:35:51.336 using default UDP/IPv4 port range: [49152, 65535]
27-Nov-2009 09:35:51.336 using default UDP/IPv6 port range: [49152, 65535] - 0
Apple Support Community member ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
The AAAA records indicate that your server is trying to resolve IPv6 addresses, but can't.
The easiest solution to this one is to turn off IPv6 on the DNS server - chances are you don't need it, and won't for about 10 years yet.
As for using your ISP as the forwarder, I wouldn't do that. Remove the forwarder address and let your DNS server resolve the queries directly. This will improve performance since the data will be cached locally, and eliminate the flood of queries going to your ISP's DNS server.
- 0
Apple Support Community member ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Hello and thanks again Camelot.
I cant see anywhere to turn off IPv6 on my DNS server, can you tell me where that setting is please? Im running OSX Server 10.5.7 on an Xserve (IPv6 is off in Network setting).
Where you say remove the forwarded addresses do you mean the two ISP DNS addresses i have in my 'Forwarded IP Addresses' and to just leave the router IP address in there?
Also should i forward all requests on the routers port 53 to the server?
Thanks again, your helps is invaluable as this is slightly above what i know and its helping me learn something new.
W