IP API restrictions - can we restrict by domain? If not then enhancement request

[Berto2002]

As so many services are now cloud-based, suppliers are not publishing specific IP addresses but domains.

Example:

IP addresses and domains for Atlassian cloud products | Atlassian Support

In the HB documentation, only IP address rules are mentioned: API Keys (hornbill.com)

But we want to use these domain entries rather than 1000s of possible IPs.

Domain	Purpose
*.atl-paas.net	All Atlassian products and services use this
*.atlassian.com	All Atlassian products and services use this
*.atlassian.net	Jira and Confluence use this
*.jira.com	Jira and Confluence use this

[SamS]

Hi @Berto2002,

You'd be relying on a reverse DNS lookup - which wouldn't be really efficient (as we'd need to do it on all inbound traffic) nor, more importantly, reliable.

IP addresses are more reliable - and also nicely listed in the example you pointed us to. That list of IP ranges can be used in the API rules (afaik).

[Steve G]

@Berto2002 Can you provide examples of vendors that no longer publish IP addresses/ranges, as Atlassian, Microsoft and Google (the 3 I've checked) all do, and Atlassian's, from your link, is a relatively small list:

Also, we don't get to see a hostname of the caller, just their IP address, so we'd then have to perform reverse DNS lookups on each call, which wouldn't be particularly efficient or reliable.

Cheers,

Steve