Confused with DNS

C

CheGuevara

Verified User
Joined
Nov 23, 2009
Messages
26
Hi everyone,
I am using DirectAdmin for the first time with a new server (was a command line man before :) ). And I seem to be puzzled by a DNS problem. So say my domain is example.com and then i want to have nameservers nsa.example.com and nsb.example.com. So I create the host entries on godaddy, I create the domain example.com on directadmin, I create ns records for nsa and nsb and I create nsa and nsb A records. So I thought that would do it. Apperentely it don't. Now I have working, but non existing hame servers :confused: example.com resolves fine, but the nameserver don't resolve according to nslookup or dns report. So some of my users can't change their ns records to the my ones, because their domain register panel says the ns servers don't exist.

What am I missing here??

Thank you very much
 
yes, I am aware of that. May be I didn't explain clearly. The nameservers ARE registered with the registar, and they do work, but they don't resolve, as in nslookup, even though the A records are there.
 
You dont need A records for them to work. Once they are registered at the registrar they are added to the root dns servers and when they resolve there then they work. I never use A records on my own dns servers.
 
thanks, but unfortunately thats not really a solution. RFC states that they must have A records. It also messes up dns report. And even worse some registars seem them as invalid and don't allow customers to use those ns servers.
 
I confirm that the A records don't show:
Code: 
safeandsoundhost.com.	172800	IN	NS	nsa.safeandsoundhost.com.
safeandsoundhost.com.	172800	IN	NS	nsb.safeandsoundhost.com.
nsa.safeandsoundhost.com. 172800 IN	A	91.194.40.21
nsb.safeandsoundhost.com. 172800 IN	A	91.194.40.70
;; Received 106 bytes from 192.41.162.30#53(L.GTLD-SERVERS.NET) in 120 ms

safeandsoundhost.com.	14400	IN	A	91.194.40.21
safeandsoundhost.com.	14400	IN	NS	nsb.safeandsounhost.com.
safeandsoundhost.com.	14400	IN	NS	nsa.safeandsounhost.com.
;; Received 106 bytes from 91.194.40.70#53(nsb.safeandsoundhost.com) in 84 ms

Both A records should follow within the additional records from your nameserver, but they aren't there.

Check that your zone file contains them (being a command line man you shouldn't have problems with that), if they aren't add them, change the serial number and reload named.
 
It seems that something is not stable.

Records are good in your screenshot.

I've tried recursive (dig +trace +additional) queries to resolve nsa and nsb and they worked correctly, answers were given directly by *.gtld-servers.net nameservers as additional data.

I refreshed my local nameserver cache and tried to resolve nsa... ok. nsb... SERVFAIL.
I refreshed again, retried, nsa... SERVFAIL. nsb... ok.
I refreshed again, retried, nsa... ok. nsb... ok.

It seems that your nameservers are just failing randomly, maybe because of a broken binary, broken libraries or not enough memory. It may also be a network packet loss/corruption matter.

Run "tcpdump -vvv port 53" and "tail -f /var/log/syslog" (or whatever logfile your system uses for named) then try those queries a bunch of time, always clearing the local cache (or use an online DNS tester) and see what happens.
 
Spelling mistakes ruin lives :)
If you look very carefully again at the ns records it says .safeandsouNHost.com there's no d in between. Turned out my /etc/hosts was wrong as well. And the hostname. *sigh* Thanks a lot for your help guys and sorry for wasting your time.
 
You must log in or register to reply here.
Back
Top