Currently Being ModeratedNov 27, 2012 6:49 AM (in response to BioRich)
for a starter.
External DNS pointer = A-Record ?
If you do that for all you domains, they will point correctly to your server.
Your server resolves ONLY questions within yourdomain.xx
LAN MAP?? I think this IS the DNS database. With DNS you tell machines where to look for information. For example if you create server.yourdomain.xx the nameserver for xx gets a request to find server.yourdomain.xx.
It will point to your static IP (because you told him to, putting in a A-Record in your domain-servers DNS database.
Here it arrives and asks your mac Server...hey..where is "server" within this domain. Your DNS setup points it to your internal IP, for example.
Yes, you can direct traffic to any machine within your network putting in machine-records pointing the name of the machine to an internal IP. Routers, printers, workstations etc.
Currently Being ModeratedNov 27, 2012 8:04 AM (in response to Pierre Froelicher1)
Hi Pierre. Thanks for the reply. I read your other thread, and I'm a bit confused. DNS always seems so easy, but proves confusing.
I am using zoneedit for my primary records. Registration points to zoneedit, where I have them all pointing to my public static IP address here. Router points to my server, which should just point to itself, where Apache should take over.
Because I have mutiple machines and various directories/vhosts doing several things, I want to run a DNS in-house to serve myself. I've been running my own DNS for years, but this upgrade and the silly way Apple has again chosen to represent this, it gets confusing.
Now you say if I create server.ourdomain.xx...what do you mean by that? Nameserver for xx? I have domain1.com. So you say nameserver for com?
As for part 2, we can deal with that later, but I'm not looking for machines, but vhosts on my workstation. localtest.local isn't the name of the machine, but a vhost on that machine. I can see that using the hosts file, but I can't edit the hosts file on my iPad to point to an internal IP. That's the problem. Another hope that I have for the internal DNS, to solve those issues. But let's focus on the public domains and mail pointers.
I appreciate your help.
OK, here's some more information about my setup on the LAN (this was edited here):
place1.alpha.com // shortcut for alpha.com/place1/
place2.alpha.com // shortcut for alpha.com/place2/
mail.alpha.com // hosting email server
mail.bravo.com // hosting email server