Custom proxy service names: DNS gets added for me, should not

[ecv]

I recently added a hostname to my proxy, and suddenly my DNS responses changed.

To my surprise, a second DNS record had been added to my zone.

• I was not informed of the change.
• I did not expect the change.
• I had a record previously in place at that name.
• The existing record was left in place, and a new one added.
• This led to confusing behavior.

Encountered during edge.datum.net proxy odyssey; name in question was edge.datum.net.

Of note, the record added was 'edge.datum.net.' not 'edge' as I expected. We are seeming to prefer putting FQDNs in the record name field. This may be fine, but I'm not used to it, and anyway allows duplication of content under different keys.

[mattdjenkinson]

Hey @ecv, so would the correct behaviour here had been to re-use the dns record that already existed?

[bmertens-datum]

I have mixed feelings about FQDNs in the name field. It feels wrong but is much easier to read.

[ecv]

Hey @ecv, so would the correct behaviour here had been to re-use the dns record that already existed?

No, I think the correct behaviour is to simply not add a record at all.

However, I suspect I will be overruled on that. So, if we want to add records for users, we must:

1. tell them that it's happening, including what record we are going to add;
2. not add a FQDN record under any circumstances, instead using the naked subdomain;
3. abort/fail if the subdomain we're adding already exists

So, for me, that would've looked like:

1. dig 'edge.datum.net'
2. getting an answer, bailing out, not adding anything
3. report that there's a config in place

And for a raw new setup, it'd be:

1. dig 'newname.example.org'
2. get NXDOMAIN, proceed
3. add to example.org ALIAS record for newname pointing to proxy
4. report what we've done

[mattdjenkinson]

@scotwells was adding the FQDN when creating an alias for a proxy hostname a requirement? I remember there being a conversation about it but can't find it now.

@ecv would having something on this dialog to say we're going to programme a record for help?

[scotwells]

That thread was in slack. Was chatting with @bmertens-datum about this recently too. Ideally the user has some control over whether DNS records are automatically managed for an HTTP Proxy so they can opt-out if they don't want that capability.

[ecv]

@ecv would having something on this dialog to say we're going to programme a record for help?

It would help, but I'd still consider it pretty weird.

But [ ] checkbox in the dialog there for 'Create an ALIAS record in my DNS Zone' however would change it from weird to cool, cool enough that I might even not mind it defaulting to on.

[mattdjenkinson]

I don't understand how the hostname would work if it wasn't programmed in the dns zone?