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

Private AWS EC2 Burp Collaborator instance issue

Bug | Last updated: Apr 08, 2020 10:30AM UTC

Hi, Maybe you have answered this question for a million times but, after hours of browsing, there is no way for me to find a decent answer regards my odd issue here. [description] I am trying to deploy a custom burp collaborator server on an ec2 instance. My domain was got from AWS and everything is managed through Route53. [issue] After lots of reading, I have this config that works only by an inch, tbh, the DNS interaction check fails completely, mostly because of the CNAME Scenario #1: 90% working Route53 config: ``` *.burpcollaborator.xyz.co A [EC2-external-IP] burpcollaborator.xyz.co NS ns1.xyz.co ns1.xyz.co A [EC2-external-IP] ``` Scenario #2: I have tried the following configs, but none of them are working which burns me a lot of debugging energy without being able to find a root cause. Config #1 xyz.co A [external_ip_ec2_aws_instance] ns1.xyz.co A [external_ip_ec2_aws_instance] burpcollaborator.xyz.co NS ns1.xyz.co Config #2 *.xyz.co A [external_ip_ec2_aws_instance] ns1.xyz.co A [external_ip_ec2_aws_instance] *.burpcollaborator.xyz.co NS ns1.xyz.co Please, but please, could you have a look and tell me, what do I do wrong here? Thank you hips, Dragos

Bug | Last updated: Apr 08, 2020 10:32AM UTC

I have spotted a typo, the config from Scenario #1 is this one: ``` *.xyz.co A [external_ip_ec2_aws_instance] ns1.xyz.co A [external_ip_ec2_aws_instance] *.burpcollaborator.xyz.co CNAME ns1.xyz.co ```

Uthman, PortSwigger Agent | Last updated: Apr 09, 2020 07:56AM UTC