Differences

This shows you the differences between two versions of the page.

--- infoblox_threat_defense:geolocation [2025/03/03 16:52] – [Testing] bstafford
+++ infoblox_threat_defense:geolocation [2026/02/25 09:47] (current) – bstafford
@@ Line 5: / Line 5: @@
   * For Infoblox, this list is mostly services Google, YouTube, SalesForce, Netskope, etc.
-  * Microosft doesn't support ECS.
+  * Microsoft doesn't support ECS.
   * Infoblox forwards the /24 when forwarding ECS data.
   * When using an Infoblox Endpoint, the public IP is the one that Infoblox Cloud sees as the source IP. i.e. the public IP that the Infoblox Endpoint is source NAT'd behind.
   * When using an External Network, the public IP is the External Network being used.
   * When using NIOS-XaaS with DFP, it is the public IP of the NIOS-XaaS POP being used.
-  * When using a DFP, the public IP used is the public IP that Infoblox has associated with that DFP. i.e. the public IP that the DFP is source NAT'd behind.
+  * When using a DFP, the public IP used is the public IP that Infoblox has associated with that DFP (called "NAT IP Address" when looking at the Server details in the Infoblox Portal). i.e. the public IP that the DFP is source NAT'd behind.
 You can check what IP the service sees by testing against Google.
-<code>dig @<IP OF DFP or local DNS server>+short TXT o-o.myaddr.l.google.com</code>
+<code>dig @<IP_OF_DFP_or_local_DNS_server> +short TXT o-o.myaddr.l.google.com</code>