Well, possibly I did it! God it's fun to make a break through. Not so much fun before that point though.
Now I have to wait to find out if I'm right or not. I believe I now have two running DNS servers (ns1.datamantic.com and ns2.datamantic.com.) I took an old domain not in use (but live on the server in ca) and pointed it at the datamantic.com name servers where I created a new zone file for the domain which points to the new server.
So when the the dns change I made (at the registrar where the domain was registered) propagates out through the global dns system people requesting that domain should start being redirected to the new server. Could be a few hours, or could be 2 days. Probably less than a day though.
Getting that to work is the most difficult, and least interesting task out of this whole project. So I will be very happy if this all works.
I actually woke up twice during the night and checked this I was so excited. But it didn't work. :-(
Worked on it a bit this morning. Found the very helpful DNSreport.com site which provides very detailed diagnostics. Evidently my name servers were not responding.
But a ps -aux showed that they were both running. Strange.
Beat my head against the wall for a few hours and then finally happened upon the right google incantation which led me to the right example page which clued me in on the necessity of having 2 NS records (for ns1 and ns2) along with the A and MX records in my zone file. I know: D'uh!
And now it works fine. :-) And actually doesn't seem that intimidating anymore.
I still need the data center to do the reverse DNS delegation, but that is just a matter of asking for it (that only matters for sending email and I'm not there yet, so it's fine for now.)
Yay!
|
Now I have to wait to find out if I'm right or not. I believe I now have two running DNS servers (ns1.datamantic.com and ns2.datamantic.com.) I took an old domain not in use (but live on the server in ca) and pointed it at the datamantic.com name servers where I created a new zone file for the domain which points to the new server.
So when the the dns change I made (at the registrar where the domain was registered) propagates out through the global dns system people requesting that domain should start being redirected to the new server. Could be a few hours, or could be 2 days. Probably less than a day though.
Getting that to work is the most difficult, and least interesting task out of this whole project. So I will be very happy if this all works.
- jim 1-27-2006 4:47 am
I actually woke up twice during the night and checked this I was so excited. But it didn't work. :-(
Worked on it a bit this morning. Found the very helpful DNSreport.com site which provides very detailed diagnostics. Evidently my name servers were not responding.
But a ps -aux showed that they were both running. Strange.
Beat my head against the wall for a few hours and then finally happened upon the right google incantation which led me to the right example page which clued me in on the necessity of having 2 NS records (for ns1 and ns2) along with the A and MX records in my zone file. I know: D'uh!
And now it works fine. :-) And actually doesn't seem that intimidating anymore.
I still need the data center to do the reverse DNS delegation, but that is just a matter of asking for it (that only matters for sending email and I'm not there yet, so it's fine for now.)
Yay!
- jim 1-27-2006 8:36 pm