What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general. You are invited to get involved by asking and answering questions!

Learn more

PRTG Network Monitor

Intuitive to Use. Easy to manage.
300.000 administrators have chosen PRTG to monitor their network. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free Download

Top Tags


View all Tags

DNS wildcards in channel definition

Votes:

0

Your Vote:

Up

Down


Want this feature implemented, too? Please upvote by clicking Thumbs up!

(Posts as a reply won't be published in this feature request thread. Read Me!)


User Story

As a PRTG User, I want to use wildcards for DNS names configured in custom channel definition for flow configuration.

Details of User Story

Currently wildcard are allowed to use with IP addresses configured in custom channel definitions and only full DNS names are resolved. It will be good to have possibility to use wildcards in DNS names to allow aggregate traffic flows for part of domain. For example:

"#100:AmazonAWS SourceIP[*.compute.amazonaws.com]"

will aggregate traffic from any subdomain hosts (IPs).

Currently using * with DNS name is just ignored in channel configuration.

Acceptance criteria

Allow using wildcards with DNS name configured for fields SourceIP and DestinationIP to allow aggregate traffic in same domain.

Status

Open

add-feature dnsname prtg-kbtracker wildcard

Created on Nov 17, 2020 1:25:17 PM by  BartekTLX (0) 1

Last change on Dec 2, 2021 9:08:16 AM by  Maike Guba [Paessler Support]



Replies

Nobody has replied yet

Why not be the first?

Please log in or register to enter your reply.


Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.