CF Nameservers are giving right AND wrong IPs

My domain is weberg.de
The auth. nameservers are walt.ns.cloudflare.com + kim.ns.cloudflare.com

The NS gives me one of the following IPs.
FAIL means, the CF cache is not delivering my website.

104.21.6.18		OK
108.162.192.126	FAIL
108.162.193.148 FAIL
172.64.32.126	FAIL
172.64.33.148	FAIL
172.67.134.43	OK
173.245.58.126	FAIL
173.245.59.148	FAIL
188.114.96.7	OK
188.114.97.7	OK

What is going wrong there???

Not sure what tool you are using and / or trying to test.

104.21.6.18
172.67.134.43

Those IPs are associated with your root domain, which may or may not have a website associated with it.

A number of the IPs in your original example are of the nameservers associated with your domain. Nameservers return DNS results, they may, but are not expected to also host a website (in this case they won’t and aren’t).

Based on the info it appears your tests are not valid for what you intend to determine

Ok, you are right. Some of my scripts seems to be broken.
Sorry for wasting the time …

I’m using dig on a Linux server.

tom:~# dig +nssearch weberg.de
SOA kim.ns.cloudflare.com. dns.cloudflare.com. 2268812227 10000 2400 604800 3600 from server 108.162.192.126 in 12 ms.
SOA kim.ns.cloudflare.com. dns.cloudflare.com. 2268812227 10000 2400 604800 3600 from server 108.162.193.148 in 12 ms.
SOA kim.ns.cloudflare.com. dns.cloudflare.com. 2268812227 10000 2400 604800 3600 from server 172.64.33.148 in 12 ms.
SOA kim.ns.cloudflare.com. dns.cloudflare.com. 2268812227 10000 2400 604800 3600 from server 172.64.32.126 in 12 ms.
SOA kim.ns.cloudflare.com. dns.cloudflare.com. 2268812227 10000 2400 604800 3600 from server 173.245.59.148 in 12 ms.
SOA kim.ns.cloudflare.com. dns.cloudflare.com. 2268812227 10000 2400 604800 3600 from server 173.245.58.126 in 24 ms.

tom:~# dig -4 +noall +answer @108.162.192.126 weberg.de
weberg.de.              300     IN      A       104.21.6.18
weberg.de.              300     IN      A       172.67.134.43
tom:~# dig -4 +noall +answer @108.162.193.148 weberg.de
weberg.de.              300     IN      A       104.21.6.18
weberg.de.              300     IN      A       172.67.134.43
tom:~# dig -4 +noall +answer @172.64.32.126 weberg.de
weberg.de.              300     IN      A       104.21.6.18
weberg.de.              300     IN      A       172.67.134.43
tom:~# dig -4 +noall +answer @172.64.33.148 weberg.de
weberg.de.              300     IN      A       172.67.134.43
weberg.de.              300     IN      A       104.21.6.18
tom:~# dig -4 +noall +answer @173.245.58.126 weberg.de
weberg.de.              300     IN      A       188.114.97.7
weberg.de.              300     IN      A       188.114.96.7
tom:~# dig -4 +noall +answer @173.245.59.148 weberg.de
weberg.de.              300     IN      A       188.114.96.7
weberg.de.              300     IN      A       188.114.97.7

But, why are the 6 different nameservers (IP) giving only two of the 4 possible IPs?
That makes it different to check on changed IP.

Cloudflare is a proxy. No IP returned is the IP of the actual server. Cloudflare can and and does change the IP address advertised unless you are paying a premium for a fixed IP address on an enterprise plan or are using their BYOIP feature.

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.