BIND v9 setup Name Server to point all requests for domains to ip address

Hi,

I have setup BIND v 9 on my Linux Red Hat Enterprise server and have several domain names i need to point to an IP address.
Can anyone help me with the config.
I have about 100 domain names that all requests for need to be resolved to an address on our network.


Kind Regards,

Daniel.
Daniel2040Asked:
Who is Participating?
 
RSLEConnect With a Mentor Commented:

$TTL 86400
@       IN      SOA     pri.ns.yourdomain. hostmaster.yourdomain. (
                        2008101401      ; serial
                        7200            ; refresh
                        3600            ; retry
                        691200          ; expire
                        86400 )         ; ttl
 
        IN      NS      pri.ns.yourdomain.
        IN      NS      sec.ns.yourdomain.
 
@       IN      A       81.145.63.83

Open in new window

0
 
Chris DentPowerShell DeveloperCommented:

Hi Daniel,

You mean you need it to do:

nslookup name.com
> IP Address

If so, you will have to add an A record to each zone like one of these:

name.com.  IN A  <IPAddress>
Or
@  IN A  <IPAddress>
Or
IN A <IPAddress>

Chris
0
 
RSLECommented:
Are you asking for them all to point to the same IP or just for examples of how to add each?

To point them all to the same IP, you'll first have to enter them all into your zone file (I'm guessing named.conf) but point them all to the same file.

----
zone "example.com" { type master; file "db.global"; };
zone "example.net" { type master; file "db.global"; };
zone "example.org" { type master; file "db.global"; };
...
zone "example100.com" { type master; file "db.global"; };
----

Then you need to create said file (so db.global in my example) and rather than assign the IP to a specific domain, you use the @ symbol. thus...
"@       IN        A     192.168.100.101"

obviously changing the appropriate data  :-)
0
Worried about phishing attacks?

90% of attacks start with a phish. It’s critical that IT admins and MSSPs have the right security in place to protect their end users from these phishing attacks. Check out our latest feature brief for tips and tricks to keep your employees off a hackers line!

 
Daniel2040Author Commented:
Thanks,

so all the file named.conf needs to read is:

zone "domain.com" { type master; file "db.global"; };
zone "domain.net" { type master; file "db.global"; };
zone "domain.org" { type master; file "db.global"; };


Kind Regards,

Daniel.
0
 
RSLECommented:
well there's other data in that file like the BIND config options, but the lines posted are all you need to add to the named.conf for the domains.
0
 
Daniel2040Author Commented:
is it possible to have

zone "*" { type master; file "db.global"; };



Daniel.
0
 
RSLECommented:
you can do

zone "." { type master; file "db.global"; };

and then instead of using "@" use the * for the entry in the db.global there but this will make your nameserver respond with this single answer for ANYTHING that is queried against your nameserver... probably not a good thing.
0
 
Daniel2040Author Commented:
Thanks for all your help.

Where does the 'db.global' file go?
I have put it in the same directory as 'named.conf' but when i start the service it syas cannot find 'db.global'





Regards,

Daniel.
0
 
RSLECommented:
It should be relative to the 'directory "/path/to/namedb"' option.
0
 
Daniel2040Author Commented:
Thanks,

sorry for all the questions but what do i do for the NS and SOA records?

Currently the db.global file reads:

$TTL 86400
@       IN        A     81.145.63.83



Kind regards,

Daniel.



0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.