Quote:
|
First question: is it possible to make a server behind the firewall (let's say internal network 192.168.0.200) as the name server for the domain? I assume I'd point it to my firewall and route port 53 to 192.168.0.200. Is this correct?
|
Yes that is correct, you map the public IPs port 53 (both udp tcp) to the LAN address of the nameserver.
Quote:
|
I create a slave zone for example.com, put in 2.2.2.2 in the master ip, and it should be able to pull the dns records from the primary dns server. Is all this correct?
|
Not quite. First you get the master set up perfectly, with the correct records. Then you make a change just in the named.conf file on the slave. You don't create the zone on the slave or put any records in it. You just tell it where to look for the masters, and BIND does all the work itself. The zone entry in the named.conf on the slave should work like this -
Code:
zone "example.com" in {
type slave;
file "example.com";
masters {2.2.2.2;};
};
Quote:
|
I assume I want ns1.example.com set as the name server with my registrar, but if the host ns1 is defined on that dns...my brain hurts.
|
All you do initially is set the registrar to look at your public IP for the nameserver. Once it is looking there, then you can change the records from looking at address 2.2.2.2 to looking at ns1.example.com. You should define A records for ns1.example.com and ns2 if you want to call it that, or you can use the public name of the secondary server, which is fine even if it is ns1.othersite.net. First do it by address, then by name. You're right, you'd never get the site if you just told the registrar to look for ns1, it has to be done by numeric address initially.
Peace,
JimBass
