Making new ns with all paramaetars to work

K

kafka

Verified User
Joined
Feb 11, 2009
Messages
6
Hello..
This is mine first post here becasue i need some more technical knowledge.

I have to register new domain that will have unique ip. I bought new ip from mine hosting provider and set it to the reseller package that would have new domain with new ip.
But the problem is that i have to put new ns. I have other domains available and i made name servers with existing domain from mine moniker account. And ns that i have made are ns1 and ns2.domainthatiown.com that have server (shared ip) and ns3 and ns4.domainthatiown.com that have uinque ip.
Next that i did was changing values in admin panel in dns administration . But i have changed only this :

ftp A 209.135.157.182
localhost A 127.0.0.1
mail A 209.135.157.182
domain.mk A 209.135.157.182
pop A 209.135.157.182
www A 209.135.157.182
domain.mk. NS ns3.domainthatiown.com.
domain.mk. NS ns4.domainthatiown.com.
mail MX 10
domain.mk. TXT "v=spf1 a mx ip4:209.135.157.182 ?all"

that ip is the unique one.
Now i checked in intodns and i have problems.
Because mine knowledge about this theme is small i need your help to tell me what i need to do more in order to have functional ns.
(mine guess is that i need to add ns as authorative one and make soa but it is only mine guess and i don't know how to do that)

thanks in advance for the sollution
 
You still need to define ns1 and ns2.domainthatiown.com with A records.

Based on what I'm seeing, this should be done in the DA control panel under DNS management, not via shell.
 
tillo said:
What I suggest is that you don't obscure your DNS data. Tell us exactly what you have and what you would like to achieve, with real domain names and addresses, so that we can analyse what's done and what's to do.
Click to expand...


you are comlitelly right.

the real factors are next one:

Name Type Value Select
ftp A 209.135.157.182
localhost A 127.0.0.1
mail A 209.135.157.182
marhost.mk. A 209.135.157.182
pop A 209.135.157.182
www A 209.135.157.182
marhost.mk. NS ns3.mar-host.com.
marhost.mk. NS ns4.mar-host.com.
mail MX 10
marhost.mk. TXT "v=spf1 a mx ip4:209.135.157.182 ?all"

i have made already nameservers on mar-host.com
they are ns1.mar-host.com and ns2.marhost.com with ip 209.135.157.214(server ip or shared ip)

and now i have made new ns that are
ns3.mar-host.com and ns4.mar-host.com with 209.135.214.182(this is unique ip)
Now i know that i need to enter few details more like soa, authoraty ns , cname and (tell me whatelse)
so i have ssh and i am owner of this server and i need to make this modifications as soon as possible. Can sombody help me??? I know that here are a lot of linux administrators that know a lot more than me and i am asking you to help me.

thanks in advance
 
Here is what I found:

- the Macedonia top level domain ".mk" doesn't have a whois server, which makes impossible to tell if the domain is registered and which authoritative nameservers are assigned

- official .mk nameservers (as listed here) don't seem to have any NS record for marhost.mk, it's possible that they are still working on it or your payment hasn't got through

Code: 
$ host -t ns marhost.mk. kitka.marnet.net.mk
Using domain server:
Name: kitka.marnet.net.mk
Address: 194.149.131.2#53
Aliases: 

Host marhost.mk. not found: 3(NXDOMAIN)

- you don't need different nameservers for every domain, you could just have used ns1-2.mar-host.com instead of creating ns3-4.mar-host.com with the new IP address; nameservers IP addresses don't have anything to do with the www/ftp/mail addresses that you want to use for the domain

Check with your .mk registrar what's wrong, it's their fault. Your nameserver is working accordingly.
 
Last edited:
Again another perfect example of why we need real information and not fake or obscured data. This would have been answered about 9 hours ago if real data had been posted.
 
Even without a whois server it's possible to check the domain registration and the nameservers. The easiest way to do it is with this version of the dig command:
Code: 
$ dig marhost.mk +trace
Today this works, so I'm presuming the problem has been resolved at the registrar.

Jeff
 
Not really... some official nameservers still don't have the record (like the mentioned kitka.marnet.net.mk). rip.psg.com has it by the way, it's probably slowly spreading to the others.

Here is the "real" official nameservers for .mk:
Code: 
mk.			172800	IN	NS	NS1.ARNES.SI.
mk.			172800	IN	NS	NS1.UNIVIE.AC.AT.
mk.			172800	IN	NS	RIP.PSG.COM.
mk.			172800	IN	NS	KITKA.MARNET.NET.mk.
;; Received 232 bytes from 192.228.79.201#53(B.ROOT-SERVERS.NET) in 178 ms
 
If the official nameservers for mk don't have the records, then you need to take that up with the mk registry.

Jeff
 
You must log in or register to reply here.
Back
Top