: Create nameserver for a specific domain My domain name and dedicated hosting are with different providers. I wanted to create a own nameserver for my domain name. I created 2 host object from
My domain name and dedicated hosting are with different providers. I wanted to create a own nameserver for my domain name. I created 2 host object from domain registrar control panel.
1. ns.mydomain.com (IP of dedicated server)
2. ns2.mydomain.com (IP of dedicated server)
The same domain name in which I have created host object need to be hosted in my hosting. So I have assigned ns.mydomain.com, ns2.mydomain.com for the domain mydomain.com's name servers.
I hope this is correct... If not please correct me.
Then in my dedicated server (with PLESK control panel), I have enable the DNS service and created 2 A and other entries as follow records.
*.webmail.mydomain.com. CNAME mydomain.com.
192.168.100.219 / 24 PTR mydomain.com.
ftp.mydomain.com. CNAME mydomain.com.
mail.mydomain.com. A 192.168.100.219
ns.mydomain.com. A 83.138.xxx.xxx (PUBLIC IP OF THE SERVER)
ns2.mydomain.com. A 83.138.xxx.xxx (PUBLIC IP OF THE SERVER)
mydomain.com. NS mydomain.com.
mydomain.com. A 83.138.xxx.xxx (PUBLIC IP OF THE SERVER)
mydomain.com. MX (10) mail.mydomain.com.
mydomain.com. TXT v=spf1 +a +mx -all
webmail.mydomain.com. A 192.168.100.219 mydomain.com. NS ns.mydomain.com. mydomain.com. NS ns2.mydomain.com.
I followed these guide : help.godaddy.com/article/198
Is the above setting correct? Would I be able to use these name servers?
More posts by @Reiling115
2 Comments
Sorted by latest first Latest Oldest Best
Non-routable IP for mail.* and webmail.* seems as mistake
Can you see zone content from ns?
Primary and secondary zones for the same domain on one daemon
(BIND?) may be big headache, AFAIK
dig is your best friend on debug. Common form of it's call is
dig @server name type
where
@server is IP of your ns.mydomain.com.
name is mydomain.com.
type is AXFR|SOA etc
Better (fast) answer I can give you only with small piece of real data: IP of primary NS and domain-name, otherwise we'll continue "remote administration"
PS - I know nothing about plesk, but both PTR and A in one zone for me (as for hostmaster) is big bug
Almost perfect !
But you should have this:
mydomain.com. NS ns.mydomain.com.
mydomain.com. NS ns2.mydomain.com.
The rest is OK (Be sure that the SOA line exist on the configuration files)
#OnLinuxMachine > dig soa mydomain.com
If you need mydomain.com to work, you should add this
mydomain.com. A 83.138.xxx.xxx (PUBLIC IP OF THE SERVER)
Also, if you don't need to manage the subdomain mydomain.com:
To have MX records for it like emailaddress@www.domain.com
To have hosts like hostabc.www.mydomain.com
You can remove theses:
mydomain.com. NS ns.mydomain.com. mydomain.com. NS ns2.mydomain.com.
Terms of Use Create Support ticket Your support tickets Stock Market News! © vmapp.org2024 All Rights reserved.