DNS Settings

A

Anarchy

Verified User
Joined
Mar 8, 2010
Messages
6
Hi all I have 2 domains and they are:

www.hababam.biz & www.hababam.org

I am using custom name servers , I have a reseller account with direct admin and my registrar is mydomain.com

now both sites are online but there is something wrong with DNS, this issue was present for a long time but when setupping hababam.org dns I remembered it again:



http://www.intodns.com/hababam.org
http://www.intodns.com/hababam.biz

now instead of the IP address why do I have these

NS records from your nameservers NS records got from your nameservers listed at the parent NS are:

ns1.hababam.biz.hababam.biz [] (NO GLUE) [TTL=14400]
ns2.hababam.biz.hababam.biz [] (NO GLUE) [TTL=14400]

... I dont know how it became ns1.domain.com.domain.com , I find it stupid and dont know what caused it but is there a way to fix it ?

Maybe the settings I made are wrong :

http://e.imagehost.org/0788/hmbiz.jpg
http://e.imagehost.org/0626/hmorg.jpg

I have 2 types of ns , I recently edited hababam.biz as I saw from internet ... maybe both are false ... would be glad if you can lead me to the correct settings.

and also the red parts :

Missing nameservers reported by parent FAIL: The following nameservers are listed at your nameservers as nameservers for your domain, but are not listed at the parent nameservers (see RFC2181 5.4.1). You need to make sure that these nameservers are working.If they are not working ok, you may have problems!
ns1.hababam.biz.hababam.biz
ns2.hababam.biz.hababam.biz

======================================

Error Missing nameservers reported by your nameservers ERROR: One or more of the nameservers listed at the parent servers are not listed as NS records at your nameservers. The problem NS records are:
NS1.hababam.biz
NS2.hababam.biz
This is listed as an ERROR because there are some cases where nasty problems can occur (if the TTLs vary from the NS records at the root servers and the NS records point to your own domain, for example).

How can I get rid of these errors :(
 
Regarding the hababam.biz zone: it's quite a common error. BIND requires you to specify any full hostname with a final ".", otherwise the $ORIGIN variable (which is the domain in your case) will be added as a suffix. Just modify your NS records to ns1.hababam.biz. and ns2.hababam.biz. (with the final dot) and don't forget to add the two A records for ns1 and ns2 wihtin the same zone.

Regarding the hababam.org zone: you have specified two IP addresses in a NS record, and that's not RFC compliant. Use ns1.hababam.org. and ns2.hababam.org. then add two A records for ns1 and ns2, just like in the hababam.biz zone.
 
Thanks a lot , all done now lets see when intodns.com comes back how will the results be :)
 
thanks all looks neat now :) and a final question how can I fix the MX for hababam.biz ? I entered the value 1586449534.pamx1.hotmail.com which was given by live.com and dont know why it isnt working now ...
 
The nameserver seems correctly configured, you may want to check at MS side.
Unfortunately I've not been able to check myself that their MTAs have your domain mailboxes because their MTAs are crap.
 
I already had a support ticket in MS about this and now as my DNS stuff is correct I replied them with still not working ... lets see what will come back.
 
I fixed also "." was missing after the MX value ... my god why put a dot after everything ? cant Direct Admin think of it itself ?
 
You are right, I missed that.
Well, it's quite simple: because you have the choice whether to use full hostnames or just the local part of the zone domain.

If there wasn't any dot at the end, you would be forced to use the whole hostname every time, for example:
Code: 
@ IN NS ns1.domain.ext
@ IN MX mail.domain.ext
list.domain.ext IN MX mail.otherdomain.ext
ns1.domain.ext 1.2.3.4
www.domain.ext IN A 1.2.3.4
mail.domain.ext IN A 1.2.3.4

With the dot you have the choice:
Code: 
$ORIGIN domain.ext ;this is the default for a zone named "domain.ext"
@ IN NS ns1
@ IN MX mail
list IN MX mail.otherdomain.ext.
ns1 1.2.3.4
www IN A 1.2.3.4
mail IN A 1.2.3.4
Isn't that better? :)
Of course DA doesn't know if you are willing to use an entry as a full hostname or not, so it can't put a dot or not for you.

(if someone is wondering why I use @ instead of an empty field, it's because that's the correct way: an empty field COPIES the last field and can easily lead to errors; most people think that an empty field means $ORIGIN and that's just plain wrong)
 
Last edited:
You must log in or register to reply here.
Back
Top