Research Academy
My account Customers About Blog Careers Legal Contact Resellers

Burp Suite User Forum

Create new post

Burp Collaborator DNS Configuration

Ryan | Last updated: Jul 07, 2017 06:50PM UTC

Hi, I'm currently experiencing issues configuring DNS settings on a Burp Collaborator server I have deployed on a cloud instance. The server is within a sub-domain of my companies domain. Within the documentation it mentions that you have to configure your domain so that DNS for the domain is delegated to your collaborator server. Little confused about this. Does anyone have a solid foundation on the configuration of Burp Collaborator that could help me out? Note: Posted this as an answer to another post by accident. Apologies for the confusion. Thanks, Ryan

PortSwigger Agent | Last updated: Jul 10, 2017 07:36AM UTC

Hi Ryan, Thanks for getting in touch. The best introduction to deploying a private collaborator is here: - https://portswigger.net/burp/help/collaborator_deploying.html The DNS configuration is somewhat different to how you'd configure DNS for a web server. The collaborator server is a DNS server itself. Instead of configuring an A record, you need to configure an NS record. The content of an NS record must be a DNS name, not an IP address. You can get an idea by looking at the configuration of the public collaborator. Your configuration will be slightly simpler, as I presume you'll only have one collaborator server. bc. user@labs:~$ dig burpcollaborator.net ns @a.gtld-servers.net ... ;; AUTHORITY SECTION: burpcollaborator.net. 172800 IN NS burpcollaborator1.portswigger.net. burpcollaborator.net. 172800 IN NS burpcollaborator2.portswigger.net. ;; ADDITIONAL SECTION: burpcollaborator1.portswigger.net. 172800 IN A 52.16.21.24 burpcollaborator2.portswigger.net. 172800 IN A 52.16.107.92 ... Please let us know if you need any further assistance.

You must be an existing, logged-in customer to reply to a thread. Please email us for additional support.