DNS Setup Problem

[SEOecho]

every thing installed fine i think
but when tried to point domains to my DNS server to start hosting them
they give DNS error when navigation them
like this one mistyproxy.com
all other domains when pointed to the DNS give me DNS error
Thank you

 

[massive]

Is there any firewall blocking UDP/TCP packets to port 53?

 

[tillo]

It's simple, you have done two very common errors:

1) since you are using two nameservers with the same domain as the domain itself, you have to specify the IP addresses of ns1.xe1.org and ns2.xe1.org at GoDaddy, otherwise it will be impossible for anyone to know where your nameservers are

2) you are missing both ns1.xe1.org and ns2.xe1.org "A" records on your nameserver, this is not always required but having a correct DNS system will make it easier to find problems in the future

 

[SEOecho]

Is there any firewall blocking UDP/TCP packets to port 53?

no its just new plane server with direct admin panel only
no firewall software or even hardware

1) since you are using two nameservers with the same domain as the domain itself, you have to specify the IP addresses of ns1.xe1.org and ns2.xe1.org at GoDaddy, otherwise it will be impossible for anyone to know where your nameservers are

didn't you watch the left bottom of the screenshoot ?
http://i30.tinypic.com/2nqsadl.jpg
name servers already created and pointed to the IP 74.63.80.82 .

 

[SEOecho]

sorry it wasn't clear in the first screen shoot
here is another one which show the current Host Summary added into my domain dashboard
http://i32.tinypic.com/2h4fggw.jpg

 

[tillo]

I can see both nameservers hostname, but not their IP address. You are right though, I checked and GoDaddy knows about them.

You just need to complete the second point of my answer to make it work: the A records in you DA server.

Your DNS system:

$ dig +trace +additional ns1.xe1.org
[...]

xe1.org.                86400   IN      NS      ns2.xe1.org.
xe1.org.                86400   IN      NS      ns1.xe1.org.
ns1.xe1.org.            86400   IN      A       74.63.80.82
ns2.xe1.org.            86400   IN      A       74.63.80.82
;; Received 93 bytes from 2001:500:e::1#53(A0.ORG.AFILIAS-NST.INFO) in 168 ms

dig: couldn't get address for 'ns1.xe1.org': not found

A correct DNS system:

$ dig +trace +additional ns1.edge.tillo.ch
[...]

tillo.ch.               3600    IN      NS      ns2.edge.tillo.ch.
tillo.ch.               3600    IN      NS      ns1.edge.tillo.ch.
ns1.edge.tillo.ch.      3600    IN      A       85.17.207.63
ns2.edge.tillo.ch.      3600    IN      A       85.17.207.160
;; Received 99 bytes from 194.146.106.10#53(F.NIC.ch) in 31 ms

ns1.edge.tillo.ch.      14400   IN      A       85.17.207.63
edge.tillo.ch.          14400   IN      NS      ns1.edge.tillo.ch.
edge.tillo.ch.          14400   IN      NS      ns2.edge.tillo.ch.
ns2.edge.tillo.ch.      14400   IN      A       85.17.207.160
;; Received 99 bytes from 85.17.207.63#53(ns1.edge.tillo.ch) in 0 ms

As you can see the A records must be in both sets of nameservers: the registrar (GoDaddy for yours, the .ch authority for mine) and the respective DA servers.

 

[SEOecho]

Thank you its working now
but when i tried to point another domain to the server it didn't work till i added the A recordes is that mean i have to add a recored to each website im going to point to my server ?
this creazy i think

 

[tillo]

Of course you have!
The "glue", or "additional" records of the registrar were added to allow the use of just one domain to solve an hostname, for both the hostname and the nameservers... but the RFC states that ALL records must be set into the nameserver to make it work. You can't escape that.

Unless of course you are talking about setting a second domain (for example xe2.org) with the same nameservers as the first one (ns1.xe1.org and ns2.xe1.org). In that case, you won't need to add the A records to neither the registrar's xe2.org zone or your xe2.org zone; the domains are different, xe1.org will be used to resolve the nameservers hostnames then the result will be used to resolve the wanted xe2.org hostname.

If this is too complicated for you, you shouldn't work with DNS yourself but give this task to a skilled operator or ask for help from a consultant.

 

[SEOecho]

thank you so much the server is alive now and all the domains pointed to the server working normally

 

[rene]

Edited - I realised a problem I need to try to fix first...

 

[rene]

Forget me... Information was irrelevant

 

[rene]

I just noticed in another post that someone mentioned the 2 IPs for the nameservers should be assigned to admin. Can anyone clarify if this is actually necessary? That could be my problem since I used 2 IPs assigned to other domains. I was under the impression that the IP assignment for nameservers is independent of assigning IPs for domain.

 

[nobaloney]

Referring to your second post above, I guess you're expecting one of us to find the error on those links you gave us; why don't you do us a favor and tell us what we're looking for?

The IP#s don't have to be assigned to any specific user; they only have to respond on the server.

I generally assign all nameserver names as virtual nameservers; just easier for me.

Jeff