Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Attention: The Community will be in read-only mode on 12/14/2017 from 12:00 am pacific to 11:30 am.

During this time you will only be able to see content. Other interactions such as posting, replying to questions, or marking content as helpful will be disabled for few hours.

We apologize for the inconvenience while we perform important updates to the Community.

Bronze

MeetingPlace and Dynamic DNS

Guys,

im trying to setup MeetingPlace in an effort to gain some experience. I do not have a static public IP but i do use Dynamic DNS for some other apps and VPN. I have already installed MP and ive associated the system with a DYNDNS hostname.

When i try the url externally (wrt my network) i get to the admin centre (50% there im thinking). If i schedule a meeting, it adds extra stings to the orginial hostname and im reaching an error stating that the administration centre does not understand that part of the url. Of course basically it does not know how to resolve the entire url and im almost certain if i add this new url with the added strings, it will work.

My question is, the url string will never be constant and my lack of understanding with respect to web design/understanding leads me to ask, how is this normally acheived? How can i have MP accessible over the Internet with the constantly changing url?

thanks

1 REPLY
Super Bronze

Re: MeetingPlace and Dynamic DNS

Hi

DNS only resolves the 'host' part of the URL. A URL may be like so:

http://www.cisco.com/stuff/etc/boring.asp?user=john&meeting=1234&sessionid=12348uuefjhsdfhsdj

So in that example, http:// denotes the protocol (may be http, https, ftp etc), www.cisco.com is the host (well, www is the host/server, and cisco.com is the domain), and then the /stuff/etc/boring.asp is the path to the web page on the www server/host computer you want to access. Anything after the ? is a parameter that is passed to the page, and & seperates multiple parameters.

So if you have your www.cisco.com (or meetingplace.yourdomain.dyndns.org, whatever you have set up) working consistently, then your DNS is OK. If you can ping meetingplace.yourdomain.dyndns.org and see your correct IP address returned, DNS is OK.

The stuff after the host part of the URL is going to be different for each Meeting, and that is normal.

Regards

Aaron

Please rate helpful posts...

Aaron Please remember to rate helpful posts to identify useful responses, and mark 'Answered' if appropriate!
228
Views
0
Helpful
1
Replies
CreatePlease to create content