Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 4 replies
  • Subscribers 2 subscribers
  • Views 2322 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

DNS Hostname definitions with multiple IPs?

BarryG
I tried setting up a "DNS Hostname" definition for xml.sa.mapquest.com

However, xml.sa.mapquest.com currently resolves to 2 IPs.
It seems though that ASL randomly chooses 1 of them every few minutes.

Is there a better way to do this? I don't really want to use static IPs for this as MapQuest says they are subject to change.

[ QUOTE ]
host xml.sa.mapquest.com

looking up host xml.sa.mapquest.com...
host name :  xml.sa.mapquest.com
address   :  64.236.110.250
address   :  205.188.243.248

[/ QUOTE ]

Thanks,
Barry


This thread was automatically locked due to age.
  • 0
    Barry,

    you run into problems since, as you said, ASL always chooses another one. If you use this defnition, e.g. in the packetfilter, ASL cannot handle it and the middleware will collapse.
    Use version 6 BETA. In the definition section, you can add more than one address for the hostname.
    /bagira
  • 0 in reply to bagira
    I didn't realize it would cause even further problems!

    6 isn't an option for our production environment, at least until it's finished.

    Thanks,
    Barry
  • 0 in reply to BarryG
    DNS hostname designed for DynDNS hostnames or other "small" installations where only one IP address is behind the hostname. It's not designed to handle hostnames which resolves to more than one IP address or which changes the IP address every few minutes.

    V6 is able to handle "big" hostnames. Basically It just adds all the IPs it ever sees to the DNS definition. Internally it's similar to a network group and so can be used wherever a network group can be used in webadmin.
    No way to do that in V5.

    Xeno