I thought ALIAS wasn't a real record type, so the DNS server software could do whatever it wanted to do with it? I want failover for HTTPS, so I don't think there's anything like SRV that would work for that.

Probably not.  The whole point of a dynamic address update is that any (and all) prior address(es) are invalid when the record is updated with a new address.  You must use separate labels to maintain more than one dynamic destination (one label per destination).  IPv4 and IPv6 dynamic addresses can coexist under a single label because they are different RR-types.

ALIAS, CNAME, and DNAME records take a single destination only.  Multiple instances of these RR-types are forbidden.

If you’re trying to do something like load balancing or failure rollover, look at SRV records if the application or protocol you intend to use supports them.

Yes, looks like wrong data is because my fault

Is there any way to have a single name with multiple A or AAAA records pointing at different places with separate dynamic updates? I tried making two separate names with separate dynamic updates, then pointing two ALIAS records from the same name to those dynamic names, but I'm only getting a single record when I look up the ALIAS name.

Dynamic records:

Code: [Select]

uriel.mandelberg.org A 300 74.104.157.60
chusuk.mandelberg.org A 300 32.212.241.128

Static records:

Code: [Select]

test123.mandelberg.org ALIAS 300 uriel.mandelberg.org
test123.mandelberg.org ALIAS 300 chusuk.mandelberg.org


Code: [Select]

$ host test123.mandelberg.org
test123.mandelberg.org has address 32.212.241.128

Is there any way to set up a name that returns records for both addresses above, where each address can be changed separately by a different dynamic dns client?

Hi. I accidentally indicated the wrong size for the T-shirt. How to fix?

Greetings,

I am trying to setup ipv6 tunnel with UDMP?  Cant seem to quite get it working, anyone try it with the UDMP?  Care to share the settings?

Regards,

Rick

Thank you.  That worked.

The information in rWHOIS looks correct for your information.

Thank you for reply,

So, there is no chance to change these values in rwhois ?

This really worked for cloudflare for example, so maybe cloudflare or cloudflare geolocation service respective these values.

Now workaround is to disable tunnel or use hosts to force domains to use ipv4 instead of ipv6.

I have rate limiting enabled in my DNS server.  I’m getting rate limiting messages in my system logs for DNS queries that appear to be from HE’s tunnel server.  Example:

11-Sep-2021 08:23:52.542 client @0x7fcf905af6e0 66.220.18.42#26678 (DELETED-bl.snarked.net): rate limit slip NODATA response to 66.220.18.0/24 for DELETED-bl.snarked.net IN  (2d03f8d7)

I see no reason for a tunnel server to be the source of a query for any hosted domain outside of HE itself.  Is there a security hole permitting them to be open resolvers?

I have masked the actual query by deleting part of it, but left enough of it to show that it is a DNSBL entry, not a hostname query.  Why would a tunnel server be checking my private list (and furthermore, the list being checked is not an IPv4, IPv6, or a domain name list, but something else)?  66.220.18.42 is the Los Angeles tunnel server endpoint address.