Research Academy
My account Customers About Blog Careers Legal Contact Resellers
The Burp Suite User Forum was discontinued on the 1st November 2024.

Burp Suite User Forum

For support requests, go to the Support Center. To discuss with other Burp users, head to our Discord page.

SUPPORT CENTER DISCORD

Name resolution for same-named sites migrating to Cloud and existing On-Prem

Leonard | Last updated: Mar 11, 2021 07:46PM UTC

New Burp Suite Enterprise user. Couldn't find a good way to word the Subject. This solution is probably obvious to long-time users. We have sites on-prem that are being migrated to Cloud services. Both sites have the same name and there are 2 different app gateways in use, depending on where in the Cloud the sites will land, only 1 site (on-prem) has a DNS entry. With our previous web vulnerability scanning tool, we simply edited the hosts file on the scanning machines. The entire team no longer has access to, nor the knowledge required, to edit the hosts file on our brand new and beautiful BSE server. Is there a way within the application to point the scan to the application gateway so that we don't have to wait for someone (me, usually) to edit the hosts file? I see mentions of Options>Connections>Hostname Resolution but I don't see that option in our installation, just Connections>Platform Auth, Upsteam Proxy and Client TLS Certs for each Scan Configuration. Laugh if you want but any and all help much appreciated.

Uthman, PortSwigger Agent | Last updated: Mar 12, 2021 09:34AM UTC

Hi Leonard, The Options > Connections > Hostname Resolution can be found in Burp Pro. You can copy the JSON below and upload it as a scan configuration in Enterprise: { "project_options":{ "connections":{ "hostname_resolution":[ { "enabled":true, "hostname":"test123.com", "ip_address":"123.123.123.123" } ] } } } Please adjust it as appropriate.

Leonard | Last updated: Mar 12, 2021 07:27PM UTC