So who knows something about DNS?

Getting lots of errors here, as somebody pointed out: http://www.intodns.com/youthdebates.org

My site seems to be working absolutely fine though - should I be concerned? Will some people be failing to reach us?

Hi

ns1.ydns.co.uk does neither have a proper `A` nor `AAAA` record. That is: No IP addresses assigned. Your site will fail to be available of the second Nameserver `ns2.ydns.co.uk` fails to be available (e.g. due to DDoS). The other errors are a direct result of this.

Conclusion: Yes, something is pretty borked there.

some people will not be able to reach your website.

your nameservers need A records.

bucket said:

some people will not be able to reach your website.

your nameservers need A records.

Click to expand...

I, umm... don't know how to do this

I set an A record to my server's IP, but I don't know how to set A records for nameservers?

I'm a bit confused because I didn't do this. On our old server, all I ever had to do was point an A record over to the server IP. Somebody migrated the site over to the new server for me, and did all the DNS for me. Howcome it's more complex now?

Hi

Allegrif said:

I set an A record to my server's IP, but I don't know how to set A records for nameservers?

Click to expand...

You cannot. It is the job of the people providing you the name servers.

If you don't trust them to get it working and you are able to point your domain to other nameservers a solution can be using CloudFlare (DNS only, not the web acceleration thingy). They provide reliable DNS servers for you.

TimWolla said:

Hi
You cannot. It is the job of the people providing you the name servers.

If you don't trust them to get it working and you are able to point your domain to other nameservers a solution can be using CloudFlare (DNS only, not the web acceleration thingy). They provide reliable DNS servers for you.

Click to expand...

The people providing the name servers would be the registrar of the relevant domain, right? For example, our nameservers are ns1.ydns.co.uk and ns2.ydns.co.uk, so will the registrar of ydns.co.uk be the one providing the nameservers?

Another thing, we have a few sites pointing to this server, with the same nameservers, and these aren't throwing up errors on IntoDNS. For example: http://www.intodns.com/tyketalk.co.uk

However, whilst that site doesn't show any errors, some users are reporting problems accessing it and a re-direct loop since the move.

Hi

Allegrif said:

The people providing the name servers would be the registrar of the relevant domain, right? For example, our nameservers are ns1.ydns.co.uk and ns2.ydns.co.uk, so will the registrar of ydns.co.uk be the one providing the nameservers?

Click to expand...

Not necessarily. As I said: For example CloudFlare provides an external DNS solution.
Doing a whois lookup of ydns.co.uk shows that the registrant is YouthDebates. It looks like you are hosting you own DNS, using an extra domain for that. I have no idea, but it very much looks like that “somebody” had no idea what they were doing.

Allegrif said:

Another thing, we have a few sites pointing to this server, with the same nameservers, and these aren't throwing up errors on IntoDNS. For example: http://www.intodns.com/tyketalk.co.uk

Click to expand...

Apparently somebody fixed the issue, performing a look up now shows a proper A record for both nameservers. But even seeing such things happen make me want to scream. This must not happen. “Somebody” surely has no idea what they were doing.

Allegrif said:

However, whilst that site doesn't show any errors, some users are reporting problems accessing it and a re-direct loop since the move.

Click to expand...

This has nothing to do with DNS. Something’s borked in the server configuration.

I can see that now it is showing an MX record missing in your DNS. You can contact your hosting provider and they can add the mx entry for your website. That should fix the current error.