DNS Nameserver not functioning.

E

EpicSoftworks

New member
Joined
Dec 22, 2014
Messages
4
I've setup my own VPS and running into some DNS issues. I'm aware that these are basic knowledge issues hence I seek some help here.

I've got the standard situation going on where I've got 2 nameservers, each with their respective IP's. However. Whenever I make a lookup for my domain on intodns.com it reports that my nameservers did not return any NS records.

take a look here.

In DirectAdmin i've set the nameservers in the reseller section to the IP's i added to the VPS via the registrar. The nameservers themselves seem to be resolving correctly according the intodns.com tool? When going for the domain itself it seems to stop due to not being able to resolve.

On the domain I've setup the following:
ns1.epicsoftworks.nl. A 37.97.128.250
ns2.epicsoftworks.nl. A 77.72.150.172

epicsoftworks.nl. NS ns1.epicsoftworks.nl.
epicsoftworks.nl. NS ns2.epicsoftworks.nl.

Is there something wrong here that I'm overlooking? I tried searching this forum first but didn't found anything similair to my situation.
 
Make sure your firewall is open on port 53 tcp and udp. I cannot get any results from it.
 
scsi said:
Make sure your firewall is open on port 53 tcp and udp. I cannot get any results from it.
Click to expand...

It should be open. The website itself is up and running. That's the wierd part. It has been up for months already. It not functioning in the way that it seems to fail when checking with inspection tools. Are there any references or complete guides I could check to see if I set this up the right way?
 
Yes. I've fixed the issue this morning. I've had a faulty setup. I've made nameservers on my DirectAdmin. These nameservers gave out the wrong values to where the website's should be. How did I fix this? I've transfered the DNS as a whole to my Registrar. I've never intended to setup the nameservers on DirectAdmin the first place, however my little knowledge back in when i started with the VPS told me it was the way to go.

Now, my registrar does all the DNS work and it points to my VPS like

Registrar -> VPS -> website
instead of
Registrar -> Nameserver on VPS -> VPS -> website

I guess thats the best I can describe the problem. My websites remained online due to the DNS records being cached by other servers. I didn't knew however that records can remain in this cache for months? My problem is something that was present for months in my setup yet my websites remained online via a GLUE record. I still don't know how, but it happened. Can anybody confirm something like this can happen, or am I just talking funny and the problem should've lied elsewhere?
 
DNS propagation is max 48h as RFC standard, so the problem may be started 2 days before you noticed it actually.

The faulty setup sound strange, DA manage DNS automatically so its about impossible to set the wrong IP and give wrong value.

My personal opinion is that is better to have DNS on the DA server for mange them all in one place, but it's up to you :)

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