Hi, we’re running a serverless API using Amazon Lambda, and 4D seems to fail on the DNS lookup as it returns multiple IP addesses A dig gives you api.universalcodes.msupply.org.nz. 25 IN A 52.84.207.226 api.universalcodes.msupply.org.nz. 25 IN A 52.84.207.186 api.universalcodes.msupply.org.nz. 25 IN A 52.84.207.19 api.universalcodes.msupply.org.nz. 25 IN A 52.84.207.198 api.universalcodes.msupply.org.nz. 25 IN A 52.84.207.164 api.universalcodes.msupply.org.nz. 25 IN A 52.84.207.224 api.universalcodes.msupply.org.nz. 25 IN A 52.84.207.57 api.universalcodes.msupply.org.nz. 25 IN A 52.84.207.209
A simple browser query works fine https://api.universalcodes.msupply.org.nz/v1/items?name=amo&exact=false <https://api.universalcodes.msupply.org.nz/v1/items?name=amo&exact=false> but not from 4D Any ideas appreciated. Cheers, Craig --------------------- Sustainable Solutions Kathmandu, Nepal & Auckland, New Zealand Nepal: +977 1 5548021 New Zealand: +64 9 9506778 cr...@sussol.net skype://craigdrown http://www.sussol.net http://www.msupply.org.nz ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **********************************************************************
