Domains Must Allow the Setting of Nameservers (NS DNS Records)

[Mike Whitby <m.whitby@…>]

All domains are created by default with ns.domain.com, so if I created test.com the nameservers would automatically get set to ns1.test.com and ns2.test.com - this is usually not the case and as such the root servers disagree with the IspCP DNS server, creating stealth nameservers.

Its not a huge issue, but the panel should let you specify the nameservers that are in use for the domain. cPanel uses a default reseller-specific setting - this would be handy, as usually each reseller would have their own nameserver hostnames for cosmetic reasons.

[Alex Joe <voxar@…>]

I had many troubles with delegation domain from another provider. I agree with Mike but it isn't all. NS record must specify existing name server and second existing name server with different IP address. I propose change part of bind:

$TTL 12H
$ORIGIN {DMN_NAME}.
@               IN              SOA             ns1.{BASE_DOMAIN_FOR RESELLER_OR_ISPCP}. postmaster.{DMN_NAME}. (
; dmn [{DMN_NAME}] timestamp entry BEGIN.
                {TIMESTAMP}     ; Serial
; dmn [{DMN_NAME}] timestamp entry END.
                8H              ; Refresh
                15M             ; Retry
                4W              ; Expire
                3H              ; Minimum TTL
)
                IN              NS              ns1.{BASE_DOMAIN_FOR RESELLER_OR_ISPCP}.
                IN              NS              ns2.{BASE_DOMAIN_FOR RESELLER_OR_ISPCP}.
                IN              MX      10      mail.{DMN_NAME}.

{DMN_NAME}.     IN              A               {DMN_IP}
www             IN              A               {DMN_IP}
{DMN_NAME}.     IN              TXT             "v=spf1 a mx ip4:{DMN_IP} ~all"
localhost       IN              A               127.0.0.1
mail            IN              A               {DMN_IP}
ns1             IN              A               {BASE_SERVER_IP_FOR BASE_DOMAIN}
ns2             IN              A               {SECONDARY_DNS_IP_FOR_BASE_DOMAIN}
; CNAME for mail transfer
imap            IN              CNAME           mail
pop             IN              CNAME           mail
pop3            IN              CNAME           mail
relay           IN              CNAME           mail
smtp            IN              CNAME           mail
; CNAME for web transfer
ftp             IN              CNAME           www
; sub [{SUB_NAME}] entry BEGIN.
; sub [{SUB_NAME}] entry END.

It's agreeable format NS records with another domain's providers and RFC 1035 section 5 , RFC 1034 section 3.6.1. ( see  http://tools.ietf.org/html/rfc1035 and  http://tools.ietf.org/html/rfc1034 ).

Best regards

Alex Joe

[isp-control.ru]

In /etc/ispcp/bind/parts/db_e.tpl on str NS

IN NS ns1.youhost.com. IN NS ns2.youhost.com.

and comment this: # ns1 IN A {BASE_SERVER_IP} # ns2 IN A {SECONDARY_DNS_IP}

[benedikt]

This should be configurable in every reseller's account. A reseller should have the possibility to set his (his domains vendor's) ns domain names or inherits the admin's.

[benedikt]

because this is a not a bug, but a feature, we move it to 1.1.0.