4 ms·
Yes, my DNS server is listed on openresolvers.org. Here's why: I've a smallish home network, 5 machines, one of them running handful of VMs, some devices (prin
by binary11 14y ago
Yes, my DNS server is listed on openresolvers.org. Here's why:
I've a smallish home network, 5 machines, one of them running handful of VMs, some devices (printer, scanner).
I wanted to have a local DNS server to name all these things, but mostly to learn about DNS and how to set up Bind.
So i installed bind on a Debian machine, set up a local domain, promptly named .fia.intra. As an added benefit, I now had a local DNS caching server too, and since my machines use this as their primary DNS server, it needs to be recursive and not just respond to queries for my internal fia.intra. network.
Now, all this is running on an internal 192.168.1.0 network, and bind is set up to only respond to queries from 192.168.1.0/24, and I'm behind an ADSL NAT gateway, so noone from outside should be able to query my internal DNS server.
I ignorantly assumed that the ADSL modem wasn't completely broken and having a moronic way of operating.
Now, I've not set a port forwarding rule in the modem that forwards port 53 to my internal DNS server, the only port forwarding rule I have is one for SSH.
However, I have this setting on the ADSL modem: http://i.imgur.com/dlL9LKV.png http://i.imgur.com/dlL9LKV.png
The ADSL modem as shipped from the ISP acts as DHCP server on the LAN side, as most modems would do, and by default the DHCP server hands out a DNS server that is my ISPs DNS server. I changed that to my internal DNS server, 192.168.1.20.
In the image you will see the DHCP server isn't even enabled, I moved that to my same Debian machine and turned it off on the ADSL modem, but didn't erase the DNS settings.
As it turns out, because of that setting the ADSL modem listens on port 53 on the WAN interface(which has a routable IP address), and forwards/reverse-NATs queries to my DNS server at 192.168.1.20.
I'd never guessed it to do that.
I did a "dig google.com @<my.public.ip>" from an EC2 instance I have, and indeed it responded nicely..
I've now changed the setting to read "Primary DNS Server= 0.0.0.0" and have verified I no longer respond to DNS queries from the WAN side.
Stuff sucks.