NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
DNS port forward
Hello all
I seem to be having trouble forwarding DNS to my server.
I have setup port forwarding 53 TCP/UDP to my server IP, but when I test it I only get a responce from TCP. To test I se...
> Read my second post, it does tell you what I did to test.
I don't have an account with BuddyNS, so I assume that I can't use
their "a test service within there consol", and "UDP queries ERROR"
doesn't tell me much, either. I'm far from an authority, but my dim
impression was that UDP was used for DNS much more than TCP, so that if
UDP port forwarding was bad, hardly anything would work. (And, as I
said, "I haven't noticed any problems" around here, but I don't know how
to reproduce your test(s).)
> Although it doesn't say [...]
No, it does say. As I said, I was looking for a way to compare the
behavior of your server with that of mine from an outside-world
location. And, as I complained before, "I have also used several other
internet based DNS test services" was less than helpful.
> I changed my firmware to tomotoUSB [...] I'm thinking of ditching the
> router as this is the obvious problem [...]
You think that the _hardware_ is the problem? That wouldn't be my
first guess.
> I have setup port forwarding 53 TCP/UDP to my server IP, [...]
What is your "my server"?
> [...] when I test it [...]
How, exactly? What happens if you "test it" using the LAN IP address
of your "my server"? Using your public IP address from within your LAN?
> Just wondering if I'm missing something.
At the very least, a clear description of what you're doing.
> Model: R8000|Nighthawk X6 AC3200 Smart WIFI Router
Is that accurate? Firmware version?
Server: Debian 9 running bind (not that this is relavent)
Secondary DNS server: BuddyDNS. They have a test service within there consol. But I have also used several other internet based DNS test services.
Test results:
StatusComplete
UDP queries ERROR
TCP queries OK
AXFR queries OK
The following tests were done from a different server on the same LAN.
LAN IP UDP test: nc -vz -u local.ip.of.server 53
Response: Connection to local.ip.of.server 53 port [udp/domain] succeeded!
LAN FQDN UDP test: nc -vz -u fqdn.of.server 53
Response: Connection to fqdn.of.server 53 port [udp/domain] succeeded!
Firmware: Firmware Version V1.0.4.12_10.1.46 (up to date)
My lan tests indicate that port 53 TCP/UDP are open and active. However it appears that connections from outside my lan only connect via TCP.
However I cannot rule out that my ISP may be blocking or limiting port 53:UDP inbound requests.
Regards
Fred
I have just spoken with my Internet provider and they have confirmed that there are no blocks on my service.
Hence I beleive that the issue may be with the router given the above tests.
Regards
Fred
> Secondary DNS server: BuddyDNS. They have a test service [...]
"buddyns.com"?
> [...] I have also used several other internet based DNS test services.
If you disclosed what you actually did, then I might easily be able
to run similar tests against my D7000, which might tell us if Netgear
ever did this right. (I haven't noticed any problems, but that may
prove little.)Prerequisits:
A hosted domain (domain.tld)
Ability to assign custom domain servers to that domain.
Point the primary NS server to ns1.domain.tld along with the IP. This is your external (Internet) IP. This should be static.
Point the secondary NS server to ns2.domain.tld with the buddydns server IP you have selected.
Install Bind9 (named) on a machine on your LAN. I installed it on a debian9 server.
Setup the domain (domain.tld) on bind as a master (authoritive)
Setup delegation and domain transfer as per the instructions on buddydns.
Ensure you have port forwarding setup on your router with port 53 UDT/TCP pointing to the IP of the machine with bind on it.
You will need to ensure any firewall in operation on the machine with bind on it is allowing port 53
Note: When you change the DNS settings with your provider it can take up to 48 hours to propogate.
When you make changes on your bind server the changes take effect immediately, but can take up to 48 hours to propogate to all servers.
your hosted domain (domain.tld) is often refered to as FQDN.
Google is your friend when locating a DNS testing service.
I'm currently investigating changing the firmware to some other third party firmware to see of that will resolve the issue. And the router isn't under warranty, so if I brick it I'll simply upgrade to the X10.
Regards
Fred