Odd DNS txt record ...
 
Notifications
Clear all

Odd DNS txt record naming problem

8 Posts
3 Users
0 Reactions
2,492 Views
Posts: 27
Topic starter
(@newtothis)
Eminent Member
Joined: 7 years ago

Has anyone encountered an issue with trying to add a TXT DKIM DNS record for google._domainkey? It seems the "google._domainkey" name will not be accepted in SolidCP DNS Zone Editor because of the . (full stop / period), yet if I add it directly into the DNS Manager it is accepted, BUT, it does not get reflected in SolidCP.

I have used SolidCP on another server and it accepted the google._domainkey txt record name without issue. In fact, I was copying the DNS data from one server instance to the next when I discovered the issue. What is going on? I need to add all of my GSuite mail server websites to this new server and this will cause a major headache if I can't work out the answer.

7 Replies
Posts: 1964
Admin
(@m-tiggelaar)
Noble Member
Joined: 9 years ago

Hello,

On my own environment i tried google._domainkey which worked alright for me with solidcp and MS DNS 2012+ provider.

Do you have any error in audit log or even log that could give any further information?

Regards,

Marco

Reply
Posts: 27
Topic starter
(@newtothis)
Eminent Member
Joined: 7 years ago

Hi Marco

Thanks for your reply. I checked the Audit Log as you said and there was nothing there at all. I then checked the Event Viewer and it simply said that the record was added:

The DNS server wrote version 2017112701 of zone #####.com to file ####.com.dns.

And then after checking DNS Manager, the TXT record is there in a sub directory of the Forward Lookup Zone called "_domainkey"  with a Name of "google", so it has split it.

The record does not show in the DNS of the space in SolidCP. Is this simply a setting that I need to change so it doesn't get split and moved into a subdirectory of the Forward Lookup Zone and then SolidCP will see it? I am using MS Server 2016 with Management Console 3.0

Reply
Posts: 27
Topic starter
(@newtothis)
Eminent Member
Joined: 7 years ago

I also accessed Event Viewer via SolidCP (previously I did it via Server Management) but SolidCP gave this message:

The description for Event ID '3150' in Source 'Microsoft-Windows-DNS-Server-Service' cannot be found. The local computer may not have the necessary registry information or message DLL files to display the message, or you may not have permission to access them. The following information is part of the event:'2017112702', 'nnnn.com', 'nnnn.com.dns'

Do I need to worry about SolidCP not getting access to Event Viewer? If so, how would I set the permission for it.

Reply
Posts: 1456
Admin
(@trobinson)
Noble Member
Joined: 9 years ago

Hello,

 

It creating a subdirectory for _domainkey is normal. This is how Microsoft DNS handles 3rd level dns entries.

 

We have checked and it appears to be fine on 2012r2 and 2016 using SolidCP 1.3.0.

 

Can you send screen shots of the issue and see if you can replicate it on a different domain?

 

Kind Regards,

 

Trevor Robinson

Reply
Page 1 / 2
Share: