Im in the process of setting up a ptr relationship with my isp. As of now i have been reading into dns and bind from a book by o'Ryley. The book so far has filled in a lot of gaps and mis concepts that i had about dns and bind. However, i still have some gray areas i could use some help in.


concept of what i need to do. (correct me if im wrong)

-1- i need to buy a domain name (lets say i buy www.thisone.com).
-2- Register it.
-3- Have the domain name www.thisone.com point to my isp name servers.

--- isp side --

-1- Once it propagates over to there server they need to set ns1.thisone.com / ns2.thisone.com to the two designated ip that my name servers will run on.

Now from here on out i have a pretty good understanding of what i need to do if the above is somewhat correct so i wont trail on with that.


second in-addr.arpa

In alot of the zone files (db.thisone.com. & the db.addr files) there is this thing in-addr.arpa.

will i use the actuall in-addr.arpa in my zone files or will that have to be switched out with actually zone data my isp will have to give to me?

thanks

If you desire to have your DNS server be the authority for your domain - then yes - you will need the ns1, ns2 setup.

The in-addr-arpa is a mechanism that allows for reverse DNS lookup.
You can specify your IP's, so that when someone queries for your IP - your DNS server is configured to return your IP.

You shouldn't need anything from your ISP other that your addys for that.

Although, many ISPs do not make you authoritative for your IP space, unless you have a full class C of IP addresses (256 or more). You can still run your own DNS servers as long as you have multiple public IPs, but you won't need to do the PTR unless your ISP delegates the authority for your IP space.

Also, you should not delegate the ISP name servers as authoritative for your domain, unless you want them doing your DNS. If you are going to do it yourself, then make yourself authoritative.

Peace,
JimBass

I don't want my isp to be the authoritative so how exactly do i go about setting up my zone? i understand how to setup my name server but i know that my isp has to do something for me to run a name server. Although i could be wrong i am a beginner to dns/bind.

if i want to be the authoritative should i , after buying my domain, set the name server 1, and 2 to my ip address that i have reserved for the name server?

also no i don't have a class c or anything /big.



thanks

Your ISP has no effect on your DNS. They don't care one way or another what you do with your IP space. You don't have to create PTR records, all you need is the basic name resolution service of BIND. You should have your DNS servers up and running before you register the site. Some registers check that the DNS server you specify actually exists. Some don't care one way or another. Just have the DNS boxes running, with or without your domain name already created. Then create the zone by adding it to /etc/bind/named.conf and put the ns1 and ns2 as well as A and MX records in the zonefile. All that is covered in the excellent DNS and BIND book you mentioned you have read, so I am sure you can handle that part of it. Good luck, and if you get stuck, post back.

Peace,
JimBass

In FC do i have to also make changes to host and hosts.conf?

if i do do i just have to show the zones and map the ip-address?

thanks for all your help so far

Hosts and hosts.conf have nothing to do with DNS, those are just for knowing the names of hosts on the LAN, a mini-DNS, sort of. The only files you need for DNS are the named.conf file, and then the zonefile, which you name in named.conf. I usually make the zonefile name the same as the zone, IE if I were doing DNS for linuxquestions.org, I would tell named.conf to look for info about that zone in a file named "linuxquestions.org".

Yes, all you need is to list your zones in named.conf, and have the zonefiles with all the IP info, and you should be good. Set then zones up like they are in the book, you do need Start of Authority, MX, TTL and all of those things to get it to work.

You're very welcome for the help!

Peace,
JimBass

**sorry was using wrong option with them.

I have just changed the dns host with godaddy.

as it stands now i try to pull up the domain and get the dns server failed.

i think however, this could be because i just made the change.

will keep you posted.

Hi!

I have a problem with my DNS server, can somebody help me?! I have using FC2 with one public IP, my isp provided me, my primary nameserver is that and secondary ns2 is my isp-s ns! My DNS server is working correctly if I using it for my lan so I connect the other machines to that server and on clients using my public IP as dns server. So everything is OK. after I registered a domain name and when I point to my namserver1 on GoDaddy "ns.mydomain.com" whitch is on my server with public IP and nameserver 2 "ns.myisp.com" Godaddy says that ns1 is incorrectly. And I don`t know why! I must use my isp like ns2 because I can`t get second public address but I think that my primary ns must be working.

When I running "nslookup" command from dos promt it says

211.212.213.214
mydomain.com

but I think it is because my isp add a new zone file for my domain and ip. Like on stand alone dns servers whitch hosting only one sites and thats it.....!

So it isn`t working like nameserver whitch can be access from world!

Please somebody tell me what is the problem with my config files? Or what can I do to work my FC box?

Sorry for my english!

My Parameters:

"hosts"
----------------------------------------------------------------------------------------
127.0.0.1 localhost.localdomain localhost
211.212.213.214 ns.mydomain.com ns (only example)



"resolve.conf"
----------------------------------------------------------------------------------------
domain mydomain.com
nameserver 211.212.213.214



"named.conf"
----------------------------------------------------------------------------------------
// generated by named-bootconf.pl

options {
directory "/var/named";
/*
* If there is a firewall between you and nameservers you want
* to talk to, you might need to uncomment the query-source
* directive below. Previous versions of BIND always asked
* questions using port 53, but BIND 8.1 uses an unprivileged
* port by default.
*/
query-source address * port 53;

};

//
// a caching only nameserver config
//
controls {
inet 127.0.0.1 allow { any; } keys { rndckey; };
};

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

zone "localhost" IN {
type master;
file "localhost.zone";
allow-update { none; };
};

zone "0.0.127.in-addr.arpa" IN {
type master;
file "named.local";
allow-update { none; };
};


zone "mydomain.com" IN {
type master;
file "mydomain.com.hosts";
allow-update { none; };
};

include "/etc/rndc.key";


"mydomain.com.hosts"
------------------------------------------------------------------
$ttl 86400
mydomain.com. IN SOA ns.mydomain.com. root.mydomain.com. (
2003062822
28800
14400
3600000
86400 )

IN A 211.212.213.214

IN NS ns.mydomain.com.
IN NS ns.myisp.com.

ns IN A 211.212.213.214
www IN A 211.212.213.214
-------------------------------------------------------------------