Case sensitive and DNS

Hello,

I have put an png image, easier to explain :)

Short description: DNS records are case INsensitive.

There is "one/two/three" bugs in the screenshot, I think all are more or less linked:

• first dns records aren't detected anymore.
• second the link to update the dns record doesn't work.

No in the screenshot bug in the DNS zone.

• in the SOA record we can't name a server with Upper case, got this error:

Error "Primary DNS server" must contain a fully qualified domain name and end with a final dot.

Example: dns1.example.com.

Regards.

(from redmine: issue id 4884, created on 2016-06-15, closed on 2016-06-17)

• Relations:
  • copied_to #4888 (closed)
• Changesets:
  • Revision 3a97c755 by Swaelens Jonathan on 2016-06-16T21:16:15.000Z:

Fixes #4884 Modify DNS error message to specify that we must use lowercase for domain name

• Revision b139a1b5 by Swaelens Jonathan on 2016-06-16T21:16:32.000Z:

Fixes #4884 Modify DNS error message to specify that we must use lowercase for domain name

• Custom Fields:
  • Bug in version: 1.0.13
• Uploads:
  • Top lower case, Bottom only first upper case.
  • 0001-Fixes-4884-Modify-DNS-error-message-to-specify-that-.patch

cedric Noname wrote:

Hello,

Hello,

I have put an png image, easier to explain :)

Short description: DNS records are case INsensitive. If my memory is good, "google.com" or "gOOgle.com" are the same

There is "one/two/three" bugs in the screenshot, I think all are more or less linked:

• first dns records aren't detected anymore. What would you exactly say with "aren't detected" because I can create a record, save it, reopen my zone and edit it.
• second the link to update the dns record doesn't work. You mean the link to launch argonaut directy from the primary dns server ? Do you have a worked argonaut setup ?

No in the screenshot bug in the DNS zone.

• in the SOA record we can't name a server with Upper case, got this error:

Error "Primary DNS server" must contain a fully qualified domain name and end with a final dot.

Example: dns1.example.com.

Maybe we must modify the message to force the use of only lowercase character ?

Regards.

(from redmine: written on 2016-06-16)

Here a patch to modify the message so that we know that we must use lowercase only for domain name.

(from redmine: written on 2016-06-16)

Swaelens Jonathan wrote:

cedric Noname wrote:

Hello,

Hello,

I have put an png image, easier to explain :)

Short description: DNS records are case INsensitive. If my memory is good, "google.com" or "gOOgle.com" are the same

Yes DNS records are case Insensitive that mean google.com Google.com gOOgle.com are the same

I would be more precise with the screenshot. On the top of the picture I have made a dns zone, put some dns records (A, NS, Cname records etc...) On the bottom picture it's EXACTLY the same dns zone, the only thing I have done is putting a upper case in the server name. (rename google to Google for example), and you can see that DNS records aren't been see anymore.

There is "one/two/three" bugs in the screenshot, I think all are more or less linked:

• first dns records aren't detected anymore. What would you exactly say with "aren't detected" because I can create a record, save it, reopen my zone and edit it.
• second the link to update the dns record doesn't work.

You mean the link to launch argonaut directy from the primary dns server ? Do you have a worked argonaut setup ?

The screenshot is split in two part (top/bottom), the link to update the argonaut server working perfectly (top picture). but when I rename the server name with an upper case, that same link doesn't work anymore.

No in the screenshot bug in the DNS zone.

• in the SOA record we can't name a server with Upper case, got this error:

Error "Primary DNS server" must contain a fully qualified domain name and end with a final dot.

Example: dns1.example.com.

Maybe we must modify the message to force the use of only lowercase character ? I have seen your patch. And force the use of only lowercase character is "bad". The better repair would be, that every entry will be recorded with case INsensitive property (A == a) instead of case sentitive property (A != a)

For the moment if I name a server like "Google". And i make a dns zone with your patch only allowing lower case. The link for the argonaut server will don't work.

I hope, I'm been clear ;-D

Regards.

(from redmine: written on 2016-06-16)

cedric Noname wrote:

Swaelens Jonathan wrote:

cedric Noname wrote:

Hello,

Hello,

I have put an png image, easier to explain :)

Short description: DNS records are case INsensitive. If my memory is good, "google.com" or "gOOgle.com" are the same

Yes DNS records are case Insensitive that mean google.com Google.com gOOgle.com are the same

I would be more precise with the screenshot. On the top of the picture I have made a dns zone, put some dns records (A, NS, Cname records etc...) On the bottom picture it's EXACTLY the same dns zone, the only thing I have done is putting a upper case in the server name. (rename google to Google for example), and you can see that DNS records aren't been see anymore.

Ah yes I had not notice it before.

There is "one/two/three" bugs in the screenshot, I think all are more or less linked:

• first dns records aren't detected anymore. What would you exactly say with "aren't detected" because I can create a record, save it, reopen my zone and edit it.
• second the link to update the dns record doesn't work.

You mean the link to launch argonaut directy from the primary dns server ? Do you have a worked argonaut setup ?

The screenshot is split in two part (top/bottom), the link to update the argonaut server working perfectly (top picture). but when I rename the server name with an upper case, that same link doesn't work anymore.

No in the screenshot bug in the DNS zone.

• in the SOA record we can't name a server with Upper case, got this error:

Error "Primary DNS server" must contain a fully qualified domain name and end with a final dot.

Example: dns1.example.com.

Maybe we must modify the message to force the use of only lowercase character ? I have seen your patch. And force the use of only lowercase character is "bad". The better repair would be, that every entry will be recorded with case INsensitive property (A == a) instead of case sentitive property (A != a)

For the moment if I name a server like "Google". And i make a dns zone with your patch only allowing lower case. The link for the argonaut server will don't work.

I hope, I'm been clear ;-D Yes ^^, I must see with Benoit what would be easier.

Regards.

(from redmine: written on 2016-06-16)

hello,

my proposal is we fixe that in two times:

• first we commit the patch here because it simple and reflect the reality.
• second we open a new ticket linked to this for the UPPERCASE scenario and see what the RFC and bind says :)

Cheers

(from redmine: written on 2016-06-16)

Edit -> Message transfered to #4888 (closed)

Regards.

(from redmine: written on 2016-06-16)

hello,

please remove your comment from this bug and transfert it to #4888 (closed) for further discussion :) i will close this one as its only for the error message who is wrong

Cheers

(from redmine: written on 2016-06-16)

closed

added Fixed label