On Sat, 3 Nov 2001 23:02, James wrote:
Well, if your company runs the DNS for your website on those servers and
you block outside IPs from querying from, no one on the internet will be
able to go to your website. :)
Overall, I do not think it is a big problem, unless someone is pointing
On Sat, 3 Nov 2001 23:02, James wrote:
Well, if your company runs the DNS for your website on those servers and
you block outside IPs from querying from, no one on the internet will be
able to go to your website. :)
Overall, I do not think it is a big problem, unless someone is pointing
Hello!
You can reconfigure BIND so that it only answers to requests from your
company's network only. If recursiv resolving is what you mean. I suggest
you to use D. J. Bernstein's djbdns. It's small, fast, reliable and
secure. check it out - cr.yp.to/djbdns.html
I use it myself and suggest it
You could always firewall out port 53 on your external interface.
On Sat, Nov 03, 2001 at 01:56:34PM -0500, Thedore Knab wrote:
It has recently came to my attention that anyone can use our company's nameservers.
I recently setup my home machine to use the company's nameserver to confirm
Well, if your company runs the DNS for your website on those servers and
you block outside IPs from querying from, no one on the internet will be
able to go to your website. :)
Overall, I do not think it is a big problem, unless someone is pointing
massive amounts of traffic to your DNS
James Well, if your company runs the DNS for your website on
James those servers and you block outside IPs from querying from,
James no one on the internet will be able to go to your website.
James :) [...]
I think the right way to do this in bind 8.?? is:
In named.conf
Well, it is a problem if your DNS server has zone files for lots of
internal network servers.
You could have two seperate instances of BIND (if you need an external
dns server to be answering for your domain name etc). bind each to
theiir applicable interface.
On Sat, Nov 03, 2001 at
Hello!
You can reconfigure BIND so that it only answers to requests from your
company's network only. If recursiv resolving is what you mean. I suggest
you to use D. J. Bernstein's djbdns. It's small, fast, reliable and
secure. check it out - cr.yp.to/djbdns.html
I use it myself and suggest it to
You could always firewall out port 53 on your external interface.
On Sat, Nov 03, 2001 at 01:56:34PM -0500, Thedore Knab wrote:
It has recently came to my attention that anyone can use our company's
nameservers.
I recently setup my home machine to use the company's nameserver to confirm
Well, if your company runs the DNS for your website on those servers and
you block outside IPs from querying from, no one on the internet will be
able to go to your website. :)
Overall, I do not think it is a big problem, unless someone is pointing
massive amounts of traffic to your DNS servers.
James Well, if your company runs the DNS for your website on
James those servers and you block outside IPs from querying from,
James no one on the internet will be able to go to your website.
James :) [...]
I think the right way to do this in bind 8.?? is:
In named.conf
Well, it is a problem if your DNS server has zone files for lots of
internal network servers.
You could have two seperate instances of BIND (if you need an external
dns server to be answering for your domain name etc). bind each to
theiir applicable interface.
On Sat, Nov 03, 2001 at 05:02:07PM
12 matches
Mail list logo
