Can anybody make any sense out of this? (it involves lack of DNS)

[James Lampert <jamesl@xxxxxxxxxxxxxxxxx>]

We have a customer who wants us to interface with Google Calendar, and 
when I finally get something (HTTPAPI-based) kind-of sort-of ready for 
alpha-test, HTTPAPI doesn't connect, and when I look at the relevant 
logs, I see that it's complaining about lack of DNS, and I quickly find 
out that they have no DNS entries at all, and therefore can't resolve to 
the web service. We let them know where things stand.

Today, we get this back from the customer, as an explanation for why DNS 
is not set up, and to me, it makes no sense whatsoever (note that I've 
censored the system name):

> Any web requests going external from the <system name censored> 
> system go out through our Web applications Firewall , therefore DNS 
> requests aren't handled by our <system name censored> system 
> directly. This way the requests themselves are logged and can be 
> monitored, and the <system name censored> system never has to talk to
> the Internet itself. It's for reasons of security, and 
> accountability.

Can anybody here make any sense out of this? Or what it has to do with 
not having any DNS addresses set?

(My own response to this was that unless HTTPAPI at least *thinks* it's
resolving the URL for the Google Calendar web services, in such a way 
that the requests and responses get through, it's "game over.")

--
JHHL
-----------------------------------------------------------------------
This is the FTPAPI mailing list.  To unsubscribe, please go to:
http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------