Hello!
I installed keyweb on subdomain (admin.xxx.ru), and when i add domain in panel, domain added to dans servers with full subdomain, like ns.admin.xxx.ru. How i can change this option for what domain added to just ns.xxx.ru?
Thanks and sorry for my English. Russian forum is dead
Little BUG? in dns
Re: Little BUG? in dns
Privet Drema - you are welcome)
the behavior you've described is normal for our Keyhelp-Panel. It automatically generates common subdomains as like just right from the servername(hostname)/FQDN, to follow RFC guideline: https://ietf.org/rfc/rfc1535.txt. Same with generated subdomains of added domain-users.
If you like to use: as regular nameserver then you need to change the hostname/FQDN of the server to:
Please note: If you are about to use "xxx.ru" as hostname, you will be unable to use this domain as a normal domain. "xxx.ru" would just cover the management functions of the panel and the server itself.
In this way it might be maybe useful to use a generated hostname by your hoster (as for keyweb customers "km3XXXX.keymachine.de") or just use another domain specified for management of Servers like: "svr1.otherdomain.ru".
For an workaround:
1. add an additional domain "xxx.ru" in Keyhelp
2. Chose this Domain "xxx.ru" at the "DNS-Zone editor"
3. Change the NS-Records of the domain "xxx.ru" that currently point onto "ns.admin.xxx.ru" to "ns.xxx.ru"
4. Save the changes.
Now you are able test with "dig" if the resolution @ the server is working.
or
or
Of course you also could test it with "host", too
the behavior you've described is normal for our Keyhelp-Panel. It automatically generates common subdomains as like
Code: Select all
"ns."; "ns2."; "mail."
If you like to use:
Code: Select all
"ns.xxx.ru"
Code: Select all
"xxx.ru"
In this way it might be maybe useful to use a generated hostname by your hoster (as for keyweb customers "km3XXXX.keymachine.de") or just use another domain specified for management of Servers like: "svr1.otherdomain.ru".
For an workaround:
1. add an additional domain "xxx.ru" in Keyhelp
2. Chose this Domain "xxx.ru" at the "DNS-Zone editor"
3. Change the NS-Records of the domain "xxx.ru" that currently point onto "ns.admin.xxx.ru" to "ns.xxx.ru"
4. Save the changes.
Now you are able test with "dig" if the resolution @ the server is working.
Code: Select all
~$ dig @SERVERIP xxx.ru NS
Code: Select all
~$ dig @SERVERIP ns.xxx.ru NS
Code: Select all
~$ dig @SERVERIP xxx.ru ANY
Code: Select all
~$ host ns.xx.ru
Mit freundlichen Grüßen / Best regards
Daniel Marckardt
**************************************************************
Keyweb AG - Die Hosting Marke
Neuwerkstr. 45/46, 99084 Erfurt / Germany
https://www.keyweb.de - https://www.keyhelp.de
**************************************************************
Daniel Marckardt
**************************************************************
Keyweb AG - Die Hosting Marke
Neuwerkstr. 45/46, 99084 Erfurt / Germany
https://www.keyweb.de - https://www.keyhelp.de
**************************************************************
Re: Little BUG? in dns
Hello,
as additional info:
If you want to use ns.xxx.ru // ns2.xxx.ru as default for new created domains, you may change the setting in KeyHelp mySQL Database:
Database: keyhelp
Table: settings
Row: nameserver
This value is comma-seperated.
Accessdata for mySQL root can be found in /root/keyhelp_login_data_*
as additional info:
If you want to use ns.xxx.ru // ns2.xxx.ru as default for new created domains, you may change the setting in KeyHelp mySQL Database:
Database: keyhelp
Table: settings
Row: nameserver
This value is comma-seperated.
Accessdata for mySQL root can be found in /root/keyhelp_login_data_*
Viele Grüße,
Martin
Martin
Re: Little BUG? in dns
It's a best way, thanks!Martin wrote:Hello,
as additional info:
If you want to use ns.xxx.ru // ns2.xxx.ru as default for new created domains, you may change the setting in KeyHelp mySQL Database:
Database: keyhelp
Table: settings
Row: nameserver
This value is comma-seperated.
Accessdata for mySQL root can be found in /root/keyhelp_login_data_*