Printable View
Hi, I have been trying to set up my own DNS server, and I read in one of the Doc I got from the net
that BIND would have some problem if my network had less than 255 addresses.
And I only have I address, as that possible to use a 1.1.168.192.in.arpa (etc)?
And could I use my ISP DNS server in my domain.?
Thanks Prophet
I've got BIND 9 running at home with just a handfull of addresses. Runs like a charm.
You can set the forwarding addresses to your ISP's DNS addresses.
I'll even recommend doing that.
You should have a 1.168.192.in.addr-arpa if you have a 192.168.1.0/24 network.
That zone would contain just 1 PTR record.
SirDice: Wouldn't it be kind of pointless (outside educational purposes) to run your own DNS server on such a small network?
You have one more service running than really needed. You'd just be increasing your security vulnerabilites if you don't know how to properly and securely configure it.
I didn't get it.Quote:
You should have a 1.168.192.in.addr-arpa if you have a 192.168.1.0/24 network.
That zone would contain just 1 PTR record.
What is PTR? and why would I need a 1.168.192?
That is one of my reasosns the other is I can't find one free.Quote:
Wouldn't it be kind of pointless (outside educational purposes) to run your own DNS server on such a small network?
A PTR record is a pointer record for reverse lookup for DNS. It is used to find a host name by using an IP address. On windows 2000/XP you can use nslookup to test it. The fact that there is only one is probably because you haven't set any host records up, or if you have you didn't tell them to create a PTR record as well. So the one that is there should be the IP address of the server running DNS.
1.168.192.in.addr-arpa represents the network you are on which as sirdice has said looks to be 192.168.1.0 with a subnet mask of 255.255.255.0
Greg
Could you link the doc? I'd be interested in reading it. I've been running BIND9 systems on my home network as a caching+local authority nameserver since BIND9 has been out.Quote:
Originally posted here by profetas
Hi, I have been trying to set up my own DNS server, and I read in one of the Doc I got from the net
that BIND would have some problem if my network had less than 255 addresses.
Should be perfectly fine.Quote:
And I only have I address, as that possible to use a 1.1.168.192.in.arpa (etc)?
And could I use my ISP DNS server in my domain.?
Not at all. A caching nameserver can speed up web surfing times by lowering the latency involved in DNS lookups on successive attempts. This is why many broadband routers (ie: Linksys) provide DNS functionality in addition to DHCP and routing/NAT.Quote:
Originally posted here by phishphreek80
SirDice: Wouldn't it be kind of pointless (outside educational purposes) to run your own DNS server on such a small network?
Not really. For a caching-only nameserver you do not need to forward UDP/53. For an authoritative server, you need to, and must accept the risk, but for a small simple caching-only server, it's a non-issue. Your only worry should be hosts on your local network.Quote:
You have one more service running than really needed. You'd just be increasing your security vulnerabilites if you don't know how to properly and securely configure it.
If you need/want any help setting it up, feel free to stop by the unerror IRC and ask me for it. If I'm not AFK or absent from #lobby, I'll answer any questions you have to the best of my abilities.
chsh: good enough reasons for me. thanks :)
I am heving some problem with rndc now.
When I try to run it it says: connection refused.
and the DNS server won't start up.
I red some txt saying that it was required to add a the control reference key in the named.conf but it didn't work.
could anyone help me?
I just want to make this DNS server to run as simple as possible
Thanks
If you like, send me an email ([email protected]) with a copy of the named.conf attached (blank your IP addresses if you like). The DNS server should be started first, so if I can see a copy of your named.conf file, I'll help you troubleshoot it.Quote:
Originally posted here by profetas
I am heving some problem with rndc now.
When I try to run it it says: connection refused.
and the DNS server won't start up.
I red some txt saying that it was required to add a the control reference key in the named.conf but it didn't work.
could anyone help me?
I just want to make this DNS server to run as simple as possible
Instead of me explaining it, I found a site that does a much better job.
You can find it here:
http://www.zytrax.com/books/dns/
I use it for educational purposes but it also caches, forwards and is authoritive for a small domain for internal use at home. It includes things like www.mydomain.home, an MX record for mydomain.home and some records for all my (virtual) machines.Quote:
Originally posted here by phishphreek80
SirDice: Wouldn't it be kind of pointless (outside educational purposes) to run your own DNS server on such a small network?
Not really. This service is only available for internal clients (my own machines). It isn't accessible from the "outside".Quote:
You have one more service running than really needed. You'd just be increasing your security vulnerabilites if you don't know how to properly and securely configure it.
(and I do know how to properly configure and secure it ;) )
is there anything else that should be set up to run BIND?
because I think that all my conf files are correct, but named won't start. (when I type named it seems to work) but when I ps -aux |grem named I don't get anything nor when I check the port 53 .
I responded to your email. It was a simple syntax error from the looks of things, but we won't know until he posts or replies to me. ;)
FYI
Only NameServers who have authority over IP ranges have the ability to administer PTR records.
Personally I think it is a good Idea to run your own DNS on a small network
I have 3 myself, 2 DNS's using Treewalk http://ntcanuck.com/
and one on my Qube 2... It is a good education on DNS's
And now I have and maintain 4 external and
I maintain 6 internal DNS's in 3 locations
Customers like it because they do not have to
depend on external DNS's especially if there screwey...