Project

General

Profile

Actions
Copy link

Feature #9504

closed

Include hostname being updated in Dynamic DNS notifications

Added by robi robi over 5 years ago. Updated about 1 year ago.

Status:
Resolved
Priority:
Normal
Assignee:
Jim Pingle
Category:
Dynamic DNS
Target version:
2.7.1
Start date:
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
23.09
Release Notes:

Description

We have multiple Dynamic DNSes set up for multiple interfaces. Several WANs, each with several Dynamic DNS entries. Whenever an update happens, we get as many e-mails as many entries are set up for the sane interface, all with the following same text:

Notifications in this message: 1
================================

14:03:46 DynDNS updated IP Address on WAN2 (igb0) to 1.2.3.4

It would be nice for the information to be more detailed, to include in the notification text the hostname which the update has happened for.
The user can't tell from this, what hostnames were affected by the update. This can be confusing in situations when there are multiple hostnames on multiple interfaces.

Actions
Copy link
 #1

Updated by Jim Pingle over 5 years ago

The text could be a little more descriptive, perhaps.

The messages are already grouped. If multiple messages fire close enough together, they are collected into a single e-mail. These must be delayed just enough to trigger multiple messages.

Actions
Copy link
 #2

Updated by robi robi over 5 years ago

Perhaps???

On WAN1 we have 7 different hostnames, on WAN2 we have 3 different hostnames. Sometimes we need to change a couple of hostnames from one interface to another, it's hard to tell from 7 consecutive e-mails, all containing the same text, which were the affected hostnames...

Actions
Copy link
 #3

Updated by Jim Pingle over 5 years ago

  • Category set to Dynamic DNS

I was agreeing with you, the attitude is unnecessary.

Actions
Copy link
 #4

Updated by robi robi over 5 years ago

OK sorry, didn't intend to be rude.

Actions
Copy link
 #5

Updated by Jim Pingle about 1 year ago

  • Tracker changed from Bug to Feature
  • Subject changed from Multiple Dynamic DNS update notifications for the same interface, not differentiated by the hostname to Include hostname being updated in Dynamic DNS notifications
  • Assignee set to Jim Pingle
  • Target version set to 2.8.0
  • Start date deleted (05/07/2019)
  • Plus Target Version set to 23.09
Actions
Copy link
 #6

Updated by Jim Pingle about 1 year ago

  • Status changed from New to Feedback
  • % Done changed from 0 to 100
Actions
Copy link
 #7

Updated by Jim Pingle about 1 year ago

It's worth noting that this only applies to traditional Dynamic DNS instances (Services > Dynamic DNS, Dynamic DNS Clients tab), RFC 2136 clients already included the hostname in their notification messages.

Actions
Copy link
 #8

Updated by Jim Pingle about 1 year ago

  • Status changed from Feedback to Resolved

This has been working really well. Only issue is that HE.net tunnel broker updates print the tunnel ID instead of an FQDN since it doesn't work by hostname, but it's still handy to know so it's not worth changing.

Actions
Copy link
 #9

Updated by Jim Pingle about 1 year ago

  • Target version changed from 2.8.0 to 2.7.1
Actions
Copy link

Also available in: Atom PDF