I had a dynamic DNS service, Dynip (www.dynip.com) a year ago, but face that same problem when using the publish Application Server/Secure Mail Wizard. It looks to me that Microsoft weighed the trade-offs having ISA with or without IIS installed. Since the old proxy 2.0 depends on IIS, it gave me the flexibility to listen to the default address assigned to the public interface, and Dyamic DNS services worked great. It is a good inexpensive solution, including both services (DSL/Dynip) I was spending $60/mo vs. $300/mo for a business dsl with static ip support. It looks like the security value to the product had higher priority, then supporting a flexible and inexpensive application to provide hosting capabilities. I guess the work-around to utilize the Dynamic DNS Service and to host application services, would be to go back to the old wspcfg.ini/Firewall Client and not use the ISA's Publish Application Wizard. I know it works for Exchange 5.5, but I had to upgrade my service to optain static ip's for other lab senerios. JMO Dave -----Original Message----- From: Hugo Caye [mailto:Hugo@xxxxxxxxxxxxx] Sent: Tuesday, July 31, 2001 11:07 AM To: [ISAserver.org Discussion List] Subject: [isalist] Re: Publishing Rules http://www.ISAserver.org There are guys that use dynamic DNS services, like DNS2Go ( www.dns2go.com). I'm at home some days (three+ days flu) and different from some of yours, I don't have an ISA server here. But when I publish a server isn't there an option to use default address assigned to the public interface? -----Original Message----- From: Mark Strangways [mailto:strangconst@xxxxxxxx] Sent: segunda-feira, 30 de julho de 2001 20:29 To: [ISAserver.org Discussion List] Subject: [isalist] Re: Publishing Rules http://www.ISAserver.org Well, If you are using ISA Server to publish Web servers and other servers, making them available to Internet clients, you must obtain one or more static IP addresses in addition to registering your domain names. Internet users will access your internal servers by accessing these IP addresses or names. If you have registered an Internet domain name, you may decide to have your Internet service provider handle the details of how to administer the listing of your domain name in DNS for use by others on the Internet. When you publish internal servers, you must obtain static IP addresses with which to associate the domain or server name. When external clients access your web site or domain, local server, the ISP's DNS name resolution server will find the IP address associated with the requested Web site name server-usually an IP address on your ISA Server or on a perimeter network (also known as a DMZ, demilitarized zone, and screened subnet). Alternatively, you can use an internal DNS server to resolve requests from external clients. This DNS server should be published like any other published server. For more information, see Server publishing rules. I guess they could be :( perhaps you could put a router or something in front of the isa to translate dynamic ip's to static ones... What do you think ... Jim ? regards, Mark ----- Original Message ----- From: Mark Strangways To: [ISAserver.org Discussion List] Sent: Monday, July 30, 2001 7:24 PM Subject: [isalist] Re: Publishing Rules http://www.ISAserver.org Good point, there must be a solution to that . Microsoft wouldn't be THAT close minded, would they ? Regards Mark ----- Original Message ----- From: Mike To: [ISAserver.org Discussion List] Sent: Monday, July 30, 2001 7:07 PM Subject: [isalist] Publishing Rules http://www.ISAserver.org Does anyone know why Microsoft decided not to allow you to select the external interface versus the actual IP address in the publishing server rules. If you receive your IP DHCP, and the IP address changes then none of your publishing rules will work. Any work arounds? Mike CLow ------------------------------------------------------ You are currently subscribed to this ISAserver.org Discussion List as: david@xxxxxxxxxx To unsubscribe send a blank email to $subst('Email.Unsub')