dns Cloudflare 1.1.1.1 with problems with the following addresses
apps.na.collabserv.com
mail.notes.na.collabserv.com
ping mail.notes.na.collabserv.com
PING e10012.cd.akamaiedge.net (23.12.125.138): 56 data bytes
64 bytes from 23.12.125.138: icmp_seq = 0 ttl = 47 time = 213.106 ms
64 bytes from 23.12.125.138: icmp_seq = 1 ttl = 47 time = 213.008 ms
ping apps.na.collabserv.com
PING e10012.cd.akamaiedge.net (23.12.125.138): 56 data bytes
64 bytes from 23.12.125.138: icmp_seq = 0 ttl = 47 time = 213.096 ms
64 bytes from 23.12.125.138: icmp_seq = 1 ttl = 47 time = 212.845 ms
With dns google 8.8.8.8 all addresses work and respond to ping … I know it’s an HCL Verse mail farm
With 1.1.1.1 the address 96.17.26.207 that is from the same Verse farm does not respond
dns Cloudflare with problems with the following addresses
apps.na.collabserv.com
mail.notes.na.collabserv.com
that point to the next ip 96.17.26.207 … with google dns if it works
Which problems?
They both resolve just fine for me
nslookup apps.na.collabserv.com 1.1.1.1
Server: one.one.one.one
Address: 1.1.1.1
Non-authoritative answer:
Name: e10012.cd.akamaiedge.net
Address: 23.37.41.235
Aliases: apps.na.collabserv.com
waa-cac1-cd.ibmsmartcloud.com.edgekey.net
nslookup mail.notes.na.collabserv.com 1.1.1.1
Server: one.one.one.one
Address: 1.1.1.1
Non-authoritative answer:
Name: e10012.cd.akamaiedge.net
Address: 23.37.41.235
Aliases: mail.notes.na.collabserv.com
waa-cac1-cd.ibmsmartcloud.com.edgekey.netWith 1.1.1.1
MacBook-Pro-de-Danny:~ danny$ ping apps.na.collabserv.com
PING e10012.cd.akamaiedge.net (96.17.26.207): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
^C
— e10012.cd.akamaiedge.net ping statistics —
3 packets transmitted, 0 packets received, 100.0% packet loss
MacBook-Pro-de-Danny:~ danny$
MacBook-Pro-de-Danny:~ danny$
MacBook-Pro-de-Danny:~ danny$ ping mail.notes.na.collabserv.com
PING e10012.cd.akamaiedge.net (96.17.26.207): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
Thats ping, not a DNS lookup.
Please post the output of these four commands
nslookup apps.na.collabserv.com 1.1.1.1
nslookup mail.notes.na.collabserv.com 1.1.1.1
nslookup e10012.cd.akamaiedge.net 1.1.1.1
nslookup e10012.cd.akamaiedge.net 8.8.8.8MacBook-Pro-de-Danny:~ danny$ nslookup apps.na.collabserv.com 1.1.1.1
Server: 1.1.1.1
Address: 1.1.1.1#53
Non-authoritative answer:
apps.na.collabserv.com canonical name = waa-cac1-cd.ibmsmartcloud.com.edgekey.net.
waa-cac1-cd.ibmsmartcloud.com.edgekey.net canonical name = e10012.cd.akamaiedge.net.
Name: e10012.cd.akamaiedge.net
Address: 23.12.125.138
MacBook-Pro-de-Danny:~ danny$ nslookup mail.notes.na.collabserv.com 1.1.1.1
Server: 1.1.1.1
Address: 1.1.1.1#53
Non-authoritative answer:
mail.notes.na.collabserv.com canonical name = waa-cac1-cd.ibmsmartcloud.com.edgekey.net.
waa-cac1-cd.ibmsmartcloud.com.edgekey.net canonical name = e10012.cd.akamaiedge.net.
Name: e10012.cd.akamaiedge.net
Address: 23.12.125.138
MacBook-Pro-de-Danny:~ danny$ nslookup e10012.cd.akamaiedge.net 1.1.1.1
Server: 1.1.1.1
Address: 1.1.1.1#53
Non-authoritative answer:
Name: e10012.cd.akamaiedge.net
Address: 23.12.125.138
MacBook-Pro-de-Danny:~ danny$ nslookup e10012.cd.akamaiedge.net 8.8.8.8
Server: 8.8.8.8
Address: 8.8.8.8#53
Non-authoritative answer:
Name: e10012.cd.akamaiedge.net
Address: 96.17.89.135
It is a server farm in the HCL Cloud sometimes 1.1.1.1 sends to the following address
96.17.26.207
and when that happens the mail doesn’t work
The two hosts do resolve correctly to e10012.cd.akamaiedge.net.
However e10012.cd.akamaiedge.net resolves differently on Google’s DNS compared to Cloudflare’s. The former returns 96.17.89.135 whereas the latter 23.12.125.138.
That being an Akamai host I presume you simply get a different IP address because Cloudflare does not support ECS and hence are not routed to the closest machine but the default.
It should still be the correct machine though.
Where 96.17.26.207 comes from is a different question. Check your hosts file.
It is an ip that the ping returns to me when I point to the mentioned addresses … it is the ping that I uploaded at the beginning of the post
MacBook-Pro-de-Danny:~ danny$ ping apps.na.collabserv.com
MacBook-Pro-de-Danny:~ danny$ ping mail.notes.na.collabserv.com
The host file is clean the machine is formatted
Well, as evident from your earlier posting it is not Cloudflare which returns that address. So you are probably using another resolver, which again resolves the address to a third one.
All three addresses are Akamai addresses, so I guess it is not completely off.
Not sure what to say, then your DNS settings are not working 
It is evident from your own output that Cloudflare resolves to the 23 address.
Whats the output of
nslookup apps.na.collabserv.com 1.1.1.1
nslookup apps.na.collabserv.comMacBook-Pro-de-Danny:~ danny$ nslookup apps.na.collabserv.com 1.1.1.1
Server: 1.1.1.1
Address: 1.1.1.1#53
Non-authoritative answer:
apps.na.collabserv.com canonical name = waa-cac1-cd.ibmsmartcloud.com.edgekey.net.
waa-cac1-cd.ibmsmartcloud.com.edgekey.net canonical name = e10012.cd.akamaiedge.net.
Name: e10012.cd.akamaiedge.net
Address: 23.12.125.138
MacBook-Pro-de-Danny:~ danny$ nslookup apps.na.collabserv.com
Server: 1.1.1.1
Address: 1.1.1.1#53
Non-authoritative answer:
apps.na.collabserv.com canonical name = waa-cac1-cd.ibmsmartcloud.com.edgekey.net.
waa-cac1-cd.ibmsmartcloud.com.edgekey.net canonical name = e10012.cd.akamaiedge.net.
Name: e10012.cd.akamaiedge.net
Address: 23.12.125.138
Sometimes it responds to the addresses that give problems
Yes, your system does appear to use Cloudflare, however the IP resolution still works. If ping resolves to something else, that would usually be a hosts file but you ruled that out too.
I am afraid at this point the issue is not Cloudflare related any more and you might want to ask over at StackExchange.