I think that would be a great topic, Perhaps you could cover using dynamic
(Dyndns) and Asterisk and Router setup.

H


On Thu, Feb 18, 2010 at 6:11 PM, Jim Van Meggelen <[email protected]>wrote:

> I'm hoping to learn a bit more about DNS.
>
> I get it in theoretical terms, but the devil is in the details.
>
> Let's say I have my website atwww.mycompany.com
>
> The MX record points to my email provider somehow, and that seems to be
> easy enough to set up.
>
> But how about having SIP calls to go to my PBX (which may or may not have
> a hostname)?
>
> There are a few things that I can't quite get the hang of:
>
> 1. should I give my PBX a hostname such as pbx.mycompany.com?
> 2. should I make that a zone, and run a DNS server on my PBX?
> 3. how do I getsip:[email protected] <getsip%[email protected]>  to go
> tosip:[email protected] <tosip%[email protected]>?
> 4. should I just have the main DNS handle sip requests with the IP
> address of my PBX, and forget about the zone/server pbx.mycompany.com?
> 5. should I be giving all my devices a hostname? do I allow those
> hostnames to be handled by DNS? what about NAT and security?
>
> I'm not looking for answers to all this in an email per se, but more
> asking if somebody is willing to do a talk for us that might help
> demystify all this?
>
> BTW, even though I am clearly not qualified to speak on this topic, I'm
> a pretty quick study, I have experience with both speaking and training,
> and so would be more than willing to do some of the grunt work and
> presentation work necessary to present this to the group, if that helps
> any of you who have the know-how, but perhaps aren't comfortable
> speaking to an audience.
>
>
> --
>
> --
> Jim Van Meggelen
> [email protected]
> http://www.oreillynet.com/pub/au/2177
>
> "A child is the ultimate startup, and I have three.
> This makes me rich."
>                    Guy Kawasaki
> --
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>


-- 
Henry Coleman

Reply via email to