[Nik]

Hello, aim constnqalty havign this DNS isssue.
Can you plz explan it to me and helpo me resolve it?
Thank you.

The hostname (superhost.gr) resolves to 108.162.198.168. It should
resolve to 84.200.17.58. Please be sure that the contents of
/etc/hosts are configured correctly, and also that there is a
correct 'A' entry for the domain in the zone file.

Some or all of these problems can be caused by /etc/resolv.conf
being setup incorrectly. Please check that file if you believe
everything else is correct.

You may be able to automatically correct this problem by using the
'Add an A entry for your hostname' option under 'Dns Functions' in
your Web Host Manager.

[couttsj]

superhost.gr lists
nina.ns.cloudflare.com [173.245.58.136]
art.ns.cloudflare.com [173.245.59.102]
as NameServers.
Either of those replies with
[108.162.198.168]
[108.162.199.168]

J.A. Coutts

[Nik]

Yes i have my domain cloudflare enabled.

it dint understand the last part though where you say:

Either of those replies with
[108.162.198.168]
[108.162.199.168]

[couttsj]

cloudflare.com is the Nameserver registered with the top level domain servers as the host for the domain superhost.gr. Those 2 servers are the ones providing the answer to the rest of the DNS servers around the world. In order to change the answer provided, the address at those servers must be changed.

J.A. Coutts

[Nik]

So, basically the message tells me that the dns resolve is being done by CloudFlare servers and not by the local superhost.gr namesevers being.

ns1.superhost.gr
ns2.superhost.gr


Is this what it tells me?
And if yes, can i just ignore it?

[couttsj]

Originally Posted by Nik

So, basically the message tells me that the dns resolve is being done by CloudFlare servers and not by the local superhost.gr namesevers being.

When you register a domain, you supply the Nameservers that you want to host the domain. The root servers do not know where the domain resides. They only know where the Host servers are, and which ones are hosting the domain in question. If you query the authoritative DNS server directly, it will respond without using recursion, because it is authoritative. However, all other DNS servers must use recursion.When the root servers are queried for superhost.gr, they will not provide an answer, but will direct you to one of the following:
estia.ics.forth.gr
grdns-de.denic.de
gr-m.ics.forth.gr
gr-at.ics.forth.gr
gr-br.ics.forth.gr
gr-ix.ics.forth.gr
gr-us.ics.forth.gr
grdns.ics.forth.gr
Querying any one of those will also not provide an answer, but will direct you to:
art.ns.cloudflare.com
nina.ns.cloudflare.com
which are the authoritative servers. Querying either of these finally gets you the answer:
108.162.199.168
108.162.198.168

If you are the only one needing to access your domain using your own DNS servers (which I gather are not registered as Nameservers), then yes you don't need to worry about it. But if you want anyone else to find your domain, then you you need to correct the answers that cloudflare.com are providing, or register your own DNS servers and correct your domain registration to point to them.

J.A. Coutts

[Nik]

First thank you for the detail info:

I also want to ask you a bit more please to clear thing out:

1. WHM and SolusVM need to make use of the same hostname ?
For example i have set WHM to make use of the hostname 'nikos.superhost.gr' and SolusVM has hostname 'superhost.gr'

Is this correct or will it provide DNS issues?

2. "If you are the only one needing to access your domain using your own DNS servers (which I gather are not registered as Nameservers), then yes you don't need to worry about it. But if you want anyone else to find your domain, then you you need to correct the answers that cloudflare.com are providing, or register your own DNS servers and correct your domain registration to point to them."

My registered dns servers are respectively:

ns1.superhost.gr
ns2.superhost.gr

Then i decided to CloudFlare my domain so i add it as domain tmy cloudflare.com account.

That why the authoritative server are:

art.ns.cloudflare.com
nina.ns.cloudflare.com

and not my registered dns servers.

Are you saying that i need to alter my DNS settings to point to ns*.superhost.gr and not CloudFlares'
Please analyze that a bit more, what will be more correct and why?

Thank you.

[couttsj]

I think you are confusing what a registered NameServer is. If ns1.superhost.gr/ns2.superhost.gr were registered as Nameservers, then the root servers would know where they are. But they don't. I have to ask art.ns.cloudflare.com/nina.ns.cloudflare.com and then they respond with:
ns1.superhost.gr [84.200.17.58]
ns2.superhost.gr [84.200.17.59]
for the fully qualified server name. For the domain name itself, they return:
superhost.gr [108.162.199.168]
superhost.gr [108.162.198.168]

You need to modify the "A" record on the cloudflare.com servers for the domain name. As it stands right now, the outside world will never be able to find your domain. They can only find your DNS servers if they ask for them specifically. For more info on how DNS works, see:
http://www.yellowhead.com/DNS_How.htm

J.A. Coutts

[Nik]

Sorry for the delay to answer:

Iam noit sure i still follow.
On the deomainn resistrar i have decalred the name servers of my domian superhost.gr to be art aand nina from cloudflare.

My domain's web page is workign s you cna see by visiting http://superhost.gr

but iam receiving this error:

Reverse MX A records (PTR) ERROR: No reverse DNS (PTR) entries. The problem MX records are: 
58.17.200.84.in-addr.arpa -> no reverse (PTR) detected

Also if i switch back the namservers to (ns1.superhost.gr / ns2.superhost.gr) then the mail functionality stops working.

Iam so confused about this.
You should contact your ISP and ask him to add a PTR record for your ips

[Nik]

Here is a screenshot to display how CloudFlare DNS settings are currently are so to tell me if i di omehtign wrong.

Also i dotn seem to understqnd how WHM DNS settigns interfere with Clousflare DNS settings.

[hosting charges]

Originally Posted by Nik

Here is a screenshot to display how CloudFlare DNS settings are currently are so to tell me if i di omehtign wrong.

Also i dotn seem to understqnd how WHM DNS settigns interfere with Clousflare DNS settings.

When did you make this change? It takes 24-72 hours to reciprocated, However you may raise a support ticket to your domain provider to find out whether they support mapping domain to IP address directly.

[couttsj]

Regardless of what the screen shot says, Cloudflare is still returning different addresses for your domain. They could be using HTTP redirects at these servers, and that is why your Web page is working. You can verify this yourself by using nslookup. The initial address I used here (192.168.1.1) is just to tell nslookup to use my IPv4 router as the starting DNS.

J.A. Coutts

C:\>nslookup - 192.168.1.1
Default Server: UnKnown
Address: 192.168.1.1

> nina.ns.cloudflare.com
Server: UnKnown
Address: 192.168.1.1

Non-authoritative answer:
Name: nina.ns.cloudflare.com
Addresses: 2400:cb00:2049:1::adf5:3a88
173.245.58.136

> server 173.245.58.136
Default Server: nina.ns.cloudflare.com
Address: 173.245.58.136

> superhost.gr
Server: nina.ns.cloudflare.com
Address: 173.245.58.136

Name: superhost.gr
Addresses: 108.162.199.168
108.162.198.168

[Nik]

I'm still confused about this.

Can you please explain to me what exactly happens when hitting in the browser http://superhost.gr until thw web page can be displayed step-by-step?

also what is an authoriatve and not authoritavie answer?

[couttsj]

I said that I suspected that Cloudflare was using HTTP redirects, and I set out to try and confirm that. Doing a portscan on their server at [108.162.199.168] revealed the only open port on the first 255 ports, was port 80 (HTTP/Web). That means that it is only capable of responding to Web Browser requests. Using the IP address directly in the URL (http://[108.162.199.168]) returned a message "Error 1003: Direct IP access not allowed". That more or less confirms that it is being used to host many different Web domains, and redirect these requests to the appropriate owners. Requests for http://superhost.gr get redirected from their server to your server. I have never seen that done to that extent before, but it limits the exposure to such things as Email sending & receiving (ports 25 & 110). That means that you can't receive email sent to the A-Record for superhost.gr (which in my opinion shouldn't be allowed anyway).

But Cloudfare does respond with an MX record of dc-a19530b8.superhost.gr. Unfortunately, there is no glue record (A-Record) to tell us where that server is located.

J.A. Coutts