DNS Zone question

Just a quickie...
I'm playing around with a Mac Mini Server and testing out different methods of setting up. I've noticed that when using setup assistant, if I specify that the DNS Server is the OSX Server's IP then the DNS Service is automatically configured.
It creates a zone called macserver.testserver.private. I was expecting the zone to be called testserver.private containing an A record for macserver.testserver.private. That doesn't seem right to me!
Is there any logical reason behind this?

Yes, there is a reason; you've got a zone of testserver.private containing the host macserver. It's common practice to have a domain and TLD; your domain is "testserver" and the intentionally bogus TLD is "private".
Regardless, what you likely want is a registered domain or subdomain (so that you never collide with another real domain or with one of the added domains), and you'll want to set up DNS for your particular requirements rather than the default install. I'd get out of the private TLD.
There are many differing set-up requirements and a gazillions options within DNS, and here are some [DNS set-up instructions|http://labs.hoffmanlabs.com/node/1436]. These presume use of Server Admin to configure DNS, which is compatible with but a more detailed and flexible alternative to Server Preferences.

Similar Messages

Another DNS Zone Question! :)

I have several geographic sites all with their own leopard servers (ten or so). Each are open directory masters managing public ip subnets. We do have an external dns server and all of our servers have registered names that are part of the same domain....
My question is this... when setting up dns on each server, do I need to create zones, or can I just make the dns forward to our external name server. I am worried that having more that one ns authoritative for the same domain will cause problems with our isp dns server? I have one server running just fine without zones... just forwarders ... and all is running smoothly, ical, wiki's, mcx, mobile accounts, etc...
Looking forward to finding out whether having zones at other locations and authoritative dns servers is a bad thing or not.
Thanks.

As long as the external DNS server has all of the info you need, there's no need to set up duplicate zones on your servers; as you note, it could even cause problems if the info got out of sync. In fact, you don't even need to act as a forwarder, you could just turn off DNS service and configure all your computers (servers & clients) to use your ISP's DNS servers.
In your situation, I see two reasons you might want to run DNS service: in case your internet link goes down (losing access to DNS tends to make it hard to find servers, even if they're on the same LAN), or if the public DNS servers don't have the reverse DNS (IP number -> domain name) entries you need. If you're worried about the first, you could set your servers as secondaries (aka slaves) for the relevant zones, in which case they'll download the zone files from the master and automatically keep in sync. If the second is an issue, you're probably best off bugging your ISP -- since the reverse records are tied to your IP numbers, and those're "owned by" the ISP, they're generally in charge of the reverse DNS no matter who's hosting your forward DNS zones.

Question about DNS zones

Here's my problem..
I have an internal webserver that has an external address. Clients on my internal network (the same as the webserver) can't access the internal server using its external address. I got around this in a Windows enviornment (there are multiple buildings with different environments) by creating a primary DNS zone with the external address of the server, and an A Host pointing to the internal address.
I'm having some trouble getting this setup on Lion server, and rather than breaking DNS again, I figured I'd ask around first. Like I said, I tried adding a new zone, and did something that broke DNS. I had to manually edit the configuration file to remove the new zone. The FQDN is different from the name of the Mac server.
Basically the Mac server is school.com, and I need school.google.com to point internally. These obviously aren't the real addresses, but it illustrates what I need to accomplish.
Does this make sense? Is it possible with Lion Server?
Thanks

If you want to access the webserver internally as school.google.com you cannot and should not try to create a google.com zone. If your website has your own private domain e.g. www.myschool.edu then as you (presumably) own and control that domain then you can run what is typicially called a 'split-horizon' DNS setup.
You could have a second domain name just for the website which still needs to be owned by you, this would let you use say domain.local as the main internal Active Directory domain and a second dmoain like myschool.edu for the website.
With a spit-horizon setup you need two DNS servers, one would be used just internally, the other would be used just externally. So anyone outside your network i.e. on the Internet would use the external DNS server (often your ISP), and anyone on your LAN uses the internal one. The internal one would map www.myschool.com to your internal LAN IP address of your webserver, the external DNS server would map the same www.myschool.edu to your internet routers address. Your router would then have to setup a NAT port mapping rule to forward the HTTP traffic to your internal webservers IP address. You can still have multiple websites hosted internally and be accessible externally but all of them must run on a single internal webserver as the NAT port mapping can only map to a single IP address per protocol (port number).

External DNS zone on Internal DNS servers

We currently have a 2 domain forest with DNS running on all domain controllers. All domain controllers are 2012 or 2012 R2 and our Domain and forest functional level is set at 2008 R2 due to the existence of an exchange 2003 server which wont be retired
for several months. We have 2 DNS servers in the root domain and 4 DNS servers in the child domain. This is a centralized DNS setup. Our parent domain is DOMAIN.LOCAL and the child domain is XX.DOMAIN.LOCAL. Externally, our DNS is MYDOMAIN.com. we
do not have a public facing DNS server and our DNS records are hosted by a 3rd party
We want to add the MYDOMAIN.COM DNS zone internally (AD Integrated) since we have several instances where applications do not really work well with the XX.DOMAIN.LOCAL DNS. We want this zone to host several DNS records for internal resolution
only since we do not have any public facing applications or web servers such as SharePoint etc.
My question(s) is this?
How is the best way to do this and how will it affect the zones we currently have in place.
Is it as simple as creating a new forward lookup zone, adding static records?
How do we (or do we) handle delegation?
Any information or suggestions to get me started would be greatly appreciated.
Russ

Hi,
I’m not quite understand your question, do you want to create a new primary DNS zone on your current DNS server? If so, you
just need to create a new primary, you can create the additional primary DNS zone.
The related KB:
Configuring a new primary server
http://technet.microsoft.com/en-us/library/cc776365(v=ws.10).aspx
Hope this helps.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Different SBA DNS SRV entry for the same dns zone?

Hello,
I got here a testlab with one enterprise pool and one sba deployed. The Branch Site got also an DNS Server installed. Both are using the same dns zone "test.com".
Of course now i got different server for the same SRV Record _sipinternaltls._tcp.test.com - one for autodiscovery in the enterprise pool and one for the sba. Also I want to add the second one as failover srv + the DNS Server in the Enterprise Pool should
be used as a Forwarder.
Now I got some issues how to deploy several entries on two different dns server for the same zone.
1.) If I add manually the same zone + DNS SRV entries on the SBA the dns is somehow not resolving/forwarding the entries on the other dns server in ee to other servers which are not on my SBA dns.
2.) If I only pinpoint the SRV entries for _sipinternaltls._tcp.test.com (one for sba and failover for ee site) the dns won't resolve the second a record to the enterprise pool.
What is the Best Practise for DNS SBA? Always point to the enterprise pool and, therefore, no other configuration is needed?
Regards DrWho

I played a little bit around. Problem was that I can not add the pinpoint dns srv entries via gui. Aditionally the tutorials did not work as my DNS server for SBA is not on a domain controller. In the end I did this:
sbafe -> fqdn of my sba
eefe -> fqdn of my frontend of enterprise pool
dnscmd . /zoneadd _sipinternaltls._tcp.test.com. /primary /file _sipinternaltls._tcp.test.com.dns
dnscmd . /recordadd _sipinternaltls._tcp.test.com. @ SRV 0 0 5061 sbafe.test.com.
dnscmd . /recordadd _sipinternaltls._tcp.test.com. @ SRV 10 0 5061 eefe.test.com.
dnscmd . /zoneadd sbafe.test.com. /primary /file sbafe.test.com.dns
dnscmd . /recordadd sip.sbafe.test.com. @ A 192.168.10.220
dnscmd . /zoneadd eefe.test.com. /primary /file eefe.test.com.dns
dnscmd . /recordadd sip.eefe.test.com. @ A 192.168.0.40
Question is if that is a good best proctise or should the dns server within a zone contain the same records (Primary/Backup). The Client will then always hit the FE of the EE Pool first.
Also its quite a lot of work to setup.

DNS Zone for Mail

Following on from my first question which the nice Mr Camelot answered for me
I have a server which has a DNS zone of companyname.net.
Internal mail has been setup using Mail Exchanger set to mail.companyname.net.
I have checked changeip -checkhostname and there are no issues.
The public DNS records have been set to make mail.companyname.com the MX record, and an A record for mail.companyname.com has been setup pointing to the static IP.
As I see it I have two options I can move forward with (3 actually if I wipe the server and start again )
1. Try and rename the DNS zone to companyname.com and then reset the mail settings to match.
2. Setup a CNAME on the server internal DNS to point mail.companyname.com to mail.companyname.net and leave the mail settings as they are.
I am in the process of installing SL Server on a VM to test the first option to see if it is viable, but my question is are there any options I have missed, and what would you suggest I do in this circumstance?
TIA.

So you have a zone for a host mail.example.net within your network, and valid external DNS services with an A record and MX at mail.example.com within your external DNS services, and you're wondering about rebuilding this all?
It'd be far easier to just enable mail.companyname.com as a virtual host within the mail server configuration.
Personally, I'd look to remove the use of the internal example.net MX for the mail server, and use the external path. You can set up the MX for the internal network to resolve to mail.example.com, for instance. With that (and with a firewall that knows how to reflect" outbound traffic for the WAN IP address, or - somewhat uglier - adding a DNS A record for the mail.example.com within your internal zone), the configuration is the same for all hosts, whether internal desktops or mobile devices.
Note that the companyname.com and companyname.net domains are real and registered domains. The domains example.com, example.net and example.org are RFC-reserved for documentation and for these sorts of postings.

DNS zones for Mail virtual host

Hello,
We have a split DNS server hosting mail for company.com. So we have a DNS zone called company.com with the appropriate records (A, MX).
We now need in the same box to host mail for another domain, company.org. Do we have to create a separate DNS zone for company.org with another A record for the server?
Regards
Kostas

If you're going strictly for mail and with no other network services are associated, then Camelot is quite correct and you can use an MX, and enable virtual hosting within the mail server.
If you're doing "other stuff" with that domain, then you'll need the zone.
Given the usual fondness for, well, "incomplete" questions and for server configurations and networks that, um, "evolve", then the answer I'd use is "yes"; add the zone. (If for no other reason than somebody's eventually going to want a web server with the domain, or...)
I'm not a big fan of split-horizon though I can and do use it for specific cases. I prefer to partition "inside" from "outside", and that avoids this quagmire.
And FWIW, "example.com", "example.org" and "example.net" are RFC-reserved domain names available for posting obfuscated examples and questions, for documentation, and related use. "company.com" and "company.org" are real and registered domains.

Changing DNS zone names after the fact

Over 3 months ago we started setting up our server network. After discussions with administration it was determined (at the time) that we would use and register a domain name with a .net extension. So we set up a primary server with this extension and had it registered with our ISP. We subsequently added 7 other servers to the mix and as they were installed they grabbed their names from the DNS zone we had setup *.net in our DNS zone in our primary nameserver system. It was all well the tests worked we had it all going and are moving our 130 machines (including about 60 users) over next few months (and have moved about 10 users and other machines so far.
My question is this. Back in beginning a *.org was the other option but we had problems with it and our ISP (could have been some error on our part) so we went with *.net for our domain and got that registered. Now all of a sudden as our management is wanting to move the organizational website (we are not doing that) to another service that service is tying to convince them we should have not used *.net but *.org.
The person in charge of us is strongly asking if we can go back and setup with *.org but as I understand it I cannot go in and delete my *.net DNS zone and then rename all the servers with a .org extension but as we understand it from lynda.com and other sources it appears that we probably would have to go back and reset all the machines back up by reinstalling them after I changed the first primary nameserver. And then register the new name and wait for it to propagate?
Are we wrong? Can we just go in and turn off the DNS in server admin and then change the zone name(s) to *.org and the host names of each server from *.net to *.org and restart DNS and find all to be well? As much as we can tell it appears that we would have to restart from scratch as all the documents and lynda.com imply we should have had our final domain name set and registered before we started to install and setup the primary and secondary servers?
I see some examples where it is said to make such changes something needs to be done with ipconfig and not the GUI in server admin. But again I am not sure that this will work with our primary nameserver and the 7 servers under it?
Any feedback or help about this would be appreciated. It is our preference to stay with *.net and not have to do major work as we are starting user and network migration to the new servers and hate to have have such a major setback just because one person and the web design service they want to use does not like *.net. to us it appears the horse is long out of the barn and when this was approved last fall we have gone to far to easily go back. But if it is easier to go back than we think then we are willing to try to change.
Thanks
russ

foilpan wrote:
first, what are these servers doing? are they all web servers, OD masters, simple file servers? depending on their roles, changing their names can be more or less of a problem.
The first server we set (the name server) does incoming mail, is the DNS server for local net and such. Then there is the outgoing mail server (one of 7) a web server (another of 7) and then the rest are mostly file servers for our setup.
second, work out that political stuff before making any changes. if everything's working fine as is, make a strong case for leaving things alone. if possible, estimate support costs for changing everything and troubleshooting, then see if management can justify it.
Sort of my feeling. We thought we had it all worked out but then they decided to abandon the old web site (managed by someone else but associated with the old mail/network somewhat) and have a new Web design company do it and this company complained about us having chose a .net for what reason I do not know so the administrator somehow was persuaded and had no idea of the can of worms she had opened up by changing her mind. If it is too much of a hassle and it appears so in terms of delays to move rest of organization over then I hope we can convince them.
are all these servers public facing or behind a firewall?
They are behind a firewall on a high speed cable modem ISP service (firewall is local ASTARO machine).
also, why not setup another dns zone for .org and point to the same hosts? that would allow you to use either .net or .org, for the most part. again, that depends on what these servers are doing.
We suggested that but the administrator did not like having two names we have a lot of users (volunteers and such) who are not really too savvy (the nature of free and partime help I guess) and she feels they will be confused by two extensions for network, mail and web. It sure does not bother me (I have about 8 email addresses for example now .
post more details without the political background and what the end result should be, and we'll be able to add more here.
Ok basically we want to know with the following:
1) main nameserver (the first server that provides the DNS zone for local *.net and serves the incoming mail)
2) A second outgoing SMTP server to split load and do outgoing work...
3) A third webserver doing all the web services (blog, wicki, and such)
4) 4 file servers that are going to provide a local file server for our 4 main departments
5) A final test server we are testing other things with-- so total of 8 servers.
6) 8 Users out of 60 now on the network with their personal desktops or laptop machines, and a few printers and other devices all on new network.
There are a total of 130 macs and pc's in our organization that will all eventually be on this new network with the above.
Basically we are wondering if the main (first) DNS and incoming mail sever, and the 7 other (web, SMTP out, and file server machines) will have to be set back up from reinstall if we are to make the change from the *.net zone we have now to a *.org one?
Any other details that would be of help?
Thanks
Russ
2) second

How to setup multiple DNS zones in a single domain

We have a small charter school running a Mac Open Directory network on a single subnet with a single registered FQDN for its internal domain. We are about to open a second school within a wing of the same building which will also be on a Mac Open Directory domain, but since it is legally a separate school (just administered by the same staff) it needs to be on it's own subnet and have its own LDAP directory.
Is there a way to program DNS between the two schools so that DNS traffic can be routed between them without breaking the DNS and Open Directory/Kerberos realms of either? Both schools will share the same internal domain name. Is it as simple as creating two primary DNS zones on each other's nameservers, both using the same domain name but each having its own designated nameserver for that particular subnet?
For instance, the existing school is running DNS on server1.example.com within the 10.39.54.0/23 subnet. The second school will be running DNS on server2.example.com within the 10.39.56.0/23 subnet. Would I then simply create two primary zones within each subnet, one referring to its own with itself as the nameserver and one within the neighbor subnet referencing that subnet's server as the designated nameserver.
Or would I do this with each schools DNS servers searching through its own subnet as its primary zone with the neighbor zone being added as a secondary zone?
Thanks!

You have two options.
Use a DNS server with a single internal domain example.com and have (as you said) server1.example.com
If the two subnets are on separate networks either via a router or VLAN, then you could run a separate DHCP server on each and advertise the appropriate DNS server for that subnet.
Otherwise you could have a single DNS server and either single DHCP advertising that single DNS server and have both server1 and server2 in the single DNS zone, or a DHCP server in each subnet but still pointing to the same single DNS server.
Each of these two servers would be an Open Directory Master
Note: in DNS terminology a DNS 'zone' is the same thing as a Domain Name.
The second option which if you want to keep the two 'schools' completely separate is to do the following
Use a DNS server per subnet
Use a DHCP server per subnet
Use a different domain name per school e.g. school1.com and school2.com
Create a server record on each as appropriate e.g. server1.school1.com and server2.school2.com
You cannot have a single DNS server have two identical zones e.g. example.com and example.com as they are of course the same thing.
If the two schools will merge officially at some point it might be better to use the same domain name, if they are going to fully split then definiately it is going to be better to use two different domain names.

Hosting Multiple DNS Zones on different servers How To?

Hello, I have an issue that I would like one of the experts to help out with.
I am currently facing an issue with DNS. I currently need to be able to ping certain machines on my internal domain by their external IP address.
Example: machineA.domain.local has IP address 192.168.1.10 but from the inside of my network I would need to be able to ping machineA.domain.local and have it resolve to my EXTERNAL IP ADDRESS.
Now as far as I know using a split DNS would solve this issue. Herein lies my issue.
My DNS works half the time. Sometimes I will ping machineA.domain.local and it will resolve the internal address and sometimes it would resolve the public IP address (which I set manually in my split DNS)
Now, my reasoning for this is because there are multiple entries with the same machine name on the same domain controller that resolve to different IP addresses. So when I ping machineA.domain.local the reply will be a "confused" reply.
Here is what I tried to do to correct the issue. I created another Windows Server 2008 R2 machine with only the DNS role installed. I then removed the split DNS from my domain controller and added the zone "zone.domain.com" with the A record "machineA.domain.com"
I did not join the domain with the new machine as I did not believe it to be necessary.
The machines on the inside still cannot ping "machineA.domain.com", nor can my new server successfully ping "machineA.domain.local". It can resolve "machineA.domain.com" but I am fairly certain this is because I added it in
the DNS zone.
I tried to go a little further and tried to connect to the domain controller DNS via the MMC snap in on my new server. I get an error telling me that the access is denied.
In order to attempt to fix that I added the computer in the properties of the DNS in the security tab. I also added the newly created server to the DNS admins group.
Nothing works I am not sure what I am doing incorrect but I would need to know how I can do the following
A) Successfully (if possible) have 2 different zones on the same domain
example: internal.domain.local and external.domain.com
I would need to know how to be able to successfully ping the machines I need to ping that resolves to the external IP address from the inside without having the internal A record in the DNS zone interfere.
I would also need to know how I could connect to the domain controllers DNS via another computer (the new server) without having the access is denied error.
Once again, I tried to use a split DNS on the same server which yielded mixed results. I cannot have the machines replying randomly or go down because 2 DNS zones are on the same machine.
Thank you hope to get an answer ASAP!

Anyone have any ideas on this?

How to change DNS zone, or how to host email outside of BC

I have BC from Creative Cloud Suite, so I have the cheapest possible plan for BC. Meaning I don't get any email hosting. So I was looking to host email outside of BC. I looked it up on google to see if it could be done (I'm really new with all this hosting stuff!), and I found that if you change the DNS zone and MX records to certain things you could. I had to delete the MX record I had set up prior to finding out BC won't host my email, and I went to set up an Advance DNS Records.. But I'm not sure what to do! There's a lot of information I'm not sure about, and I don't know what goes where!
I'd like to have godaddy host my email, and what I found is that I need to change my DNS zone to: mailstore1.secureserver.net and change MX records to 0 smtp.secureserver.net 10 mailstore1.secureserver.net
I may end up finding somewhere else to host email at a later point, but right now I just want to try to figure out how to do this so I'll be able to in the future. Any and all help is appreciated! Thank you

Hi
All you need to do is go to Admin > Site Settings > Site Domains and activate your new domain. You’ll have to enter an MX record for e-mail to be setup, which will be provided by godaddy.
Here’s a similar article on the same topic:
http://forums.adobe.com/message/4997019#4997019
Let me know how it goes

DNS record is not dynamically created in DNS Zone, when joining to DNS domain

hi
in my test lab i have deployed two virtual machines (both are windows server 2008 R2 enterprise).
on vm1 i have installed just DNS role (without Active directory) and created a primary non-ADintegrated zone.
on this DNS zone, i have enabled dynamic update set to
non-secure & secure .
now in my vm2 (as a DNS client) , i set the ip address of this DNS server as preferred DNS server and then in system properties, on the primary DNS suffix field, i entered the name of my DNS domain (mydomain.lab)& rebooted VM2, but the a record of this
client (vm2) is not registered (created ) in mydomain.lab zone.
i respect the record be created like the situations which we join a client to AD domain

Hi John ,
When registering DNS record ,client will send a SOA query to find the primary server of the zone .Then send register message to the server .
We can use nslookup to find the problem :
Open Command Prompt
type nslookup
type set type=soa
type zone name
1. If there is positive response ,check the name of
primary name server and the IP address of the server .
Its name should be vm1.mydomain.lab .If not ,edit the SOA record in the zone .
If no IP address ,edit NS record in the zone .
2. If there is no response ,check the SOA record in the zone .
We can manually delete and recreate the records to ensure there are right SOA and NS records .
Here is the guide for using nslookup :
Nslookup :
https://technet.microsoft.com/en-us/library/cc940085.aspx
Best Regards,
Leo
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Hi Leo, thanks for reply.
i did all steps you mentioned but still no result.
i put an screenshot of my desktop here , everything is shown here:

Can't create DNS zones in Server Admin

Hi All,
So, I've run into this strange problem where when configuring the zone files for the DNS server in Server Admin that clicking on the + button doesn't do anything. I've re-installed Tiger Server including reformating the disk and still nothing.
Can anyone tell me where the zone file is kept. It might be better just to make my own unless anyone can tell me why the + button isn't working.
Thanks much!

Definitely better to make your own, if you know how (lots of good google-able docs on this). Using Server Admin for DNS zone files is dicey at best.
BIND config file is located at '/etc/named.conf'
Zone files live in '/var/named/.' Primary zone files are named 'myDomain.com.zone' and secondary files are named 'myDomain.com.bak'
Feel free to email me if you need some default files.
Can anyone tell me where the zone file is kept. It
might be better just to make my own unless anyone can
tell me why the + button isn't working.
iBook G4 Mac OS X (10.4.3)

Active Directory Integrated DNS Zones, replicate only to specific domain controllers

I have a customer with a fairly large Active Directory forest with many domains that they are trying to consolidate into a single domain which likely take 18 to 24 months according to their timeline. During this time, they would like all DNS zones
to be serviced directly from the new domain controllers, meaning, domain A would have replicas of domain B, C, D, E, etc. Because the environment is complex and some domain controllers in domains other than A are in a very sad state and replication problems
abound, they would like to avoid replicating all zones forest wide.
I've never done this before, or even considered it necessary, is it even possible? I don't have a ton of time for trial and error, but based on this there seems to be some hope:
https://technet.microsoft.com/en-us/library/cc753801.aspx?f=255&MSPPError=-2147217396
Is this telling me how to do what I want to do?
Thanks
J
Joseph M. Durnal MCM: Exchange 2010 MCITP: Enterprise Messaging Administrator, Exchange 2010 MCITP: Enterprise Messaging Administrator, MCITP: Enterprise Administrator

He actually didn't specify much about dynamic updates requirements for old domains, if they don't need secure dynamic updates then a primary zone would work:
The DNS Server service allows dynamic update to be enabled or disabled on a per-zone basis at each server that is configured to load
either a standard primary or directory-integrated zone.
REF: Understanding Dynamic updates
This post is provided AS IS with no warranties or guarantees, and confers no rights.
~~~
Questo post non fornisce garanzie e non conferisce diritti

DNS, site question

I am tinkering with Snow Leopard Server as a web/file/vpn server. I am not able to get it working however, and wondered if someone could help me out. I am a noob to mac as a web server, but have some experience in dns and apache hosting in the traditional manner using a web host.
I have a registered domain name, and dns hosted at dyndns.com (I have a dynamic IP at home). The domain name NS's are pointed to dyndns, and dyndns has an A record pointing to my IP. I am forwarding port 80 on my router to the OSX server.
I currently only have one domain I am working with. When going to the domain externally I am getting an error, so I am tyring to figure out how the dns and routing is handled. The install docs are not too clear on the domain name issues, such as primary name, subdomains, dns use in my type of setup ect.
What should my Primary domain name be - I was confused as to what to put here. Can it be anything? I intend on hosting several domains, does this affect what my primary should be?
Also, do I need DNS zone files set up on my OSX Server? From what I understand, adding sites adds virtual host files for apache, so i was hoping to just use dydns to get the requests to the box which can then forward to the right folder, however this doesn't seem to be working. Any help would be greatly appreciated.
Mike
Message was edited by: maiku.emon

If Dyndns are handling your DNS then there may be no requirement to run DNS on your machine at all. You may be complicating matters here by trying to do so.
That's not a gimme, though, since there are many, many ways of configuring your network. At the end of the day, though, there is no requirement in Apache to have DNS running on your server.
What should my Primary domain name be
Whatever you like. It could be your own registered domain, but it doesn't have to be. It's not like anyobe is ever going to see this anyway.
I intend on hosting several domains, does this affect what my primary should be?
Nope. Unless you're planning on running mail, too (mail is far more sensitive to DNS than web is).

DNS Zone question

Similar Messages

Maybe you are looking for