Wednesday, August 10, 2011

Article: Multiple websites: Apple Support Communities

Multiple websites: Apple Support Communities
https://discussions.apple.com/message/15824820#15824820


It's not that it's losing traction, just most of us SysAdmins run our own static DNS servers and don't have a lot of experience with DynDNS.

Looking at your DNS config I see a few things that you should change.

Your primary zone should be:

example.com

That's it. Everything after that is just aliases (CNAMES) or extensions of your zone.

You should not have a primary zone of:      server.example.com   Even though this was setup by LS, delete it.

Server is an alias of your zone.

Under the primary zone of example.com add a CNAME of "server."   Also your machine names should all resolve to your primary zone if you're only using one machine, such as an A record for server.example.com pointing to example.com, etc…

Also, in your site setup area, you have two sites setup as test.* and cameras.* of your primary zone.  Neither one of those aliases are even listed in your DNS.  If a site can't be resolved in your DNS, it will never work. A wildcard (although I have never used DynDNS and I may be wrong here) is not used in DNS.

So just like above, make sure you have two CNAME entries in your DNS under your primary zone of example.com for test and cameras (or whatever they are under the red line).

DNS is a beeyatch.

Also, I am assuming  you have a dynamic IP address on your router as this is the reason why you are using DynDNS.  For this to even work, your DynDNS settings should point to your router and then your router needs to use NAT and port forwarding for the external services to find your internal server.

And this is another can of worms all in itself.  I would check with  your service provider and see if they can offer you a static IP address - the extra $ will be worth it in the long run.

Anyone with DynDNS experience that can help Brian out?


(via Instapaper)



Brief message sent from a handheld device.

No comments: