Hey,
Ok. I asked this question alot, and i still cannot get an answer. I am sorry to bother you but i need some help. How do i configure DNS and BIND. I have BIND 9. Nabil, you said you could send your configurations. I know you would not want people to have it, but could you at least send me something so i can try to work with it? Thanks everyone.

Have you read the good old howto? If so which bits caused confusion, if not then have a read! I'm running Bind 8 and can send you / post my /etc/namd.conf and associated files if you want, but I would have thought the howto's examples would be more useful.

cheers

Jamie...

Hey jamie,
Thanks for replying. I actually dont want to copy someone else's configurations. I want to configure it myself actually, but i have no idea how it looks since i've never seen or done DNS or BInd b4.
1) db.cache i am getting from www.bind.com right?
2) i have to configure the /etc/named.conf and do most of the work there. In this part i have to show what the ip address that matches to the URL people type.
3) I need a db.127.0.0 for the network loopback.
4) Do i need a db.my.ip.add or not?
Ok. and i've read the how-to but it did not help me much. i have o'reillys dns and bind and thats where i got all of those. Umm, if you can send me those conf files i think they would help me . You can send them to geranimo200@yahoo.com whenever you have time . thanks alot Jamie.

OK... some answers
1) I imagine you can get your 'root hints' file from www.bind.com but I always just use dig to get the an update from my ISPs DNS.
2) named.conf doesn't contains any details of the names or IPs you are using, it just configures a few parameters like your forwarders and points to the files that do contain your DNS records.
3) yeap!
4) db.my.ip.add being a file containing a mapping from your names to your IP addresses? If this is the case then yeah, you need a file that maps names => IPs and another one that maps IPs => name for reverse lookups.

HTH - I'll send you my files when you get back home this evening.

Jamie...

Hey Jamie,
Thanks for replying again. I only have one computer and its going to be my primary and secondary name server so i dont need to map the domain names to ips right? And thanks for sending me your files.

You can't have a primary and secondary on the same machine! You don't need anything more than a primary DNS, the secondary is only for when the primary is down or busy, if its a home LAN then there's not much point, unless you have a spare machine. You still need the file mapping machine names to IPs - thats was DNS does after all. You don't have a mapping between domains's and IPs, as a domain is just a way of seperating the DNS name space hence a domain itself doesn't have an IP.

HTH

Jamie...

dilberim82,

I will post my stuff soon.
All you have to do is just replace your IP address and domain names also get red of extra domains and stuff not needed for your setup.

This is for Bind 9.1 on Redhat 7.1.

Thanks alot Nabil,
Thats what i am using and i think it would help me alot . Thanks again.

OK, this example is for A primary name server called viper.nameserver.org IP 10.0.0.1 running it's own web site nameserver.org and others as domain.com.

Under /etc
named.conf
##########
## named.conf - configuration for bind
#
# Generated automatically by bindconf, alchemist et al.

options {
directory "/var/named/";
};



zone "." {
type hint;
file "named.ca";
};


zone "0.0.127.in-addr.arpa" {
type master;
file "0.0.127.in-addr.arpa.zone";
};
zone "0.0.10.in-addr.arpa" {
type master;
file "0.0.10.in-addr.arpa.zone";
};


zone "localhost" {
type master;
file "localhost.zone";
};
zone "nameserver.org" {
type master;
file "nameserver.org.zone";
};
zone "viper" {
type master;
file "viper.zone";
};
zone "domain.com" {
type master;
file "domain.com.zone";
};
#############

Under var/named

[root@viper named]# ls
0.0.127.in-addr.arpa.zone viper.zone
0.0.10.in-addr.arpa.zone domain.com.zone named.ca
nameserver.org.zone named.local localhost.zone

[root@viper named]#

############


[root@viper named]# more 0.0.127.in-addr.arpa.zone

$TTL 86400
@ IN SOA localhost. root.localhost (
1 ; serial
28800 ; refresh
7200 ; retry
604800 ; expire
86400 ; ttk
)


@ IN NS localhost.

1 IN PTR localhost.

#################

[root@viper named]# more 0.0.10.in-addr.arpa.zone

$TTL 86400
@ IN SOA viper.nameserver.org. root.localhost (
8 ; serial
28800 ; refresh
7200 ; retry
604800 ; expire
86400 ; ttk
)


@ IN NS viper.nameserver.org.

150 IN PTR viper.nameserver.org.

#####################
[root@viper named]# more domain.com.zone

$TTL 86400
@ IN SOA @ nabil.domain.com (
6 ; serial
28800 ; refresh
7200 ; retry
604800 ; expire
86400 ; ttl
)


@ IN NS viper.nameserver.org.

@ IN MX 0 www

www IN A 10.0.0.1
ftp IN A 10.0.0.1
mail IN A 10.0.0.1
@ IN A 10.0.0.1
#######################

[root@viper named]# more nameserver.org.zone

$TTL 86400
@ IN SOA @ root.nameserver.org (
4 ; serial
28800 ; refresh
7200 ; retry
604800 ; expire
86400 ; ttl
)


@ IN NS viper.nameserver.org.

@ IN MX 0 viper

www IN A 10.0.0.1
mail IN A 10.0.0.1
ftp IN A 10.0.0.1
viper IN A 10.0.0.1
@ IN A 10.0.0.1

[root@viper named]#

####################
[root@viper named]# more localhost.zone

$TTL 86400
@ IN SOA @ root.localhost (
1 ; serial
28800 ; refresh
7200 ; retry
604800 ; expire
86400 ; ttl
)


@ IN NS localhost.


@ IN A 127.0.0.1

#############################
[root@viper named]# more named.ca
; This file holds the information on root name servers needed to
; initialize cache of Internet domain name servers
; (e.g. reference this file in the "cache . <file>"
; configuration file of BIND domain name servers).
;
; This file is made available by InterNIC registration services
; under anonymous FTP as
; file /domain/named.root
; on server FTP.RS.INTERNIC.NET
; -OR- under Gopher at RS.INTERNIC.NET
; under menu InterNIC Registration Services (NSI)
; submenu InterNIC Registration Archives
; file named.root
;
; last update: Aug 22, 1997
; related version of root zone: 1997082200
;
;
; formerly NS.INTERNIC.NET
;
. 3600000 IN NS A.ROOT-SERVERS.NET.
A.ROOT-SERVERS.NET. 3600000 A 198.41.0.4
;
; formerly NS1.ISI.EDU
;
. 3600000 NS B.ROOT-SERVERS.NET.
B.ROOT-SERVERS.NET. 3600000 A 128.9.0.107
;
; formerly C.PSI.NET
;
. 3600000 NS C.ROOT-SERVERS.NET.
C.ROOT-SERVERS.NET. 3600000 A 192.33.4.12
;
; formerly TERP.UMD.EDU
;
. 3600000 NS D.ROOT-SERVERS.NET.
; formerly TERP.UMD.EDU
;
. 3600000 NS D.ROOT-SERVERS.NET.
D.ROOT-SERVERS.NET. 3600000 A 128.8.10.90
;
; formerly NS.NASA.GOV
;
. 3600000 NS E.ROOT-SERVERS.NET.
E.ROOT-SERVERS.NET. 3600000 A 192.203.230.10
;
; formerly NS.ISC.ORG
;
. 3600000 NS F.ROOT-SERVERS.NET.
F.ROOT-SERVERS.NET. 3600000 A 192.5.5.241
;
; formerly NS.NIC.DDN.MIL
;
. 3600000 NS G.ROOT-SERVERS.NET.
G.ROOT-SERVERS.NET. 3600000 A 192.112.36.4
;
; formerly AOS.ARL.ARMY.MIL
;
. 3600000 NS H.ROOT-SERVERS.NET.
H.ROOT-SERVERS.NET. 3600000 A 128.63.2.53
;
; formerly NIC.NORDU.NET
;
. 3600000 NS I.ROOT-SERVERS.NET.
I.ROOT-SERVERS.NET. 3600000 A 192.36.148.17
;
; temporarily housed at NSI (InterNIC)
;
. 3600000 NS J.ROOT-SERVERS.NET.
J.ROOT-SERVERS.NET. 3600000 A 198.41.0.10
;
; housed in LINX, operated by RIPE NCC
;
. 3600000 NS K.ROOT-SERVERS.NET.
K.ROOT-SERVERS.NET. 3600000 A 193.0.14.129
;
; temporarily housed at ISI (IANA)
;
. 3600000 NS L.ROOT-SERVERS.NET.
L.ROOT-SERVERS.NET. 3600000 A 198.32.64.12
;
; housed in Japan, operated by WIDE
;
. 3600000 NS M.ROOT-SERVERS.NET.
M.ROOT-SERVERS.NET. 3600000 A 202.12.27.33
; End of File
[root@viper named]#
####################


[root@viper named]# more viper.zone

$TTL 86400
@ IN SOA @ root.viper (
3 ; serial
28800 ; refresh
7200 ; retry
604800 ; expire
86400 ; ttl
)


@ IN NS viper.


@ IN A 10.0.0.1
####################

dilberim82,

Did that work for you or you still have problems....

I am actually working on it right now Nabil. I'll let you know by tonight But so far it has helped me alot Thanks again