A records with external ip not working properly
; cPanel first:11.48.4.2 (update_time):1451215779 Cpanel::ZoneFile::VERSION:1.3 hostname:cpanel.PLACEHOLDER.ro latest:11.52.1.3
; Zone file for PLACEHOLDER.ro
$TTL 14400
PLACEHOLDER.ro. 14400 IN SOA ns5.PLACEHOLDER.ro. office.PLACEHOLDER.ro. (
2015122701 ;Serial Number
86400 ;refresh
7200 ;retry
3600000 ;expire
86400 ;minimum
)
PLACEHOLDER.ro. 14400 IN NS ns5.PLACEHOLDER.ro.
PLACEHOLDER.ro. 14400 IN NS ns6.PLACEHOLDER.ro.
PLACEHOLDER.ro. 14400 IN A number.number.135.107
localhost 14400 IN A 127.0.0.1
PLACEHOLDER.ro. 14400 IN MX 0 PLACEHOLDER.ro.
mail 14400 IN CNAME PLACEHOLDER.ro.
www 14400 IN CNAME PLACEHOLDER.ro.
ftp 14400 IN CNAME PLACEHOLDER.ro.
PLACEHOLDER.ro. 14400 IN TXT "v=spf1 +a +mx +ip4:number.number.135.100 +ip4:number.number.135.194 ~all"
cpanel 14400 IN A number.number.135.107
webdisk 14400 IN A number.number.135.107
whm 14400 IN A number.number.135.107
webmail 14400 IN A number.number.135.107
autoconfig 14400 IN A number.number.135.107
autodiscover 14400 IN A number.number.135.107
_autodiscover._tcp 14400 IN SRV 0 0 443 cpanelemaildiscovery.cpanel.net.
default._domainkey 14400 IN TXT "v=DKIM1; k=rsa; p=blablasomethingsomething;"
cpcalendars 14400 IN A number.number.135.107
_caldav._tcp 14400 IN SRV 0 0 2079 cpanel.PLACEHOLDER.ro.
_caldavs._tcp 14400 IN SRV 0 0 2080 cpanel.PLACEHOLDER.ro.
_carddav._tcp 14400 IN SRV 0 0 2079 cpanel.PLACEHOLDER.ro.
_carddavs._tcp 14400 IN SRV 0 0 2080 cpanel.PLACEHOLDER.ro.
_caldav._tcp 14400 IN TXT path=/
_caldavs._tcp 14400 IN TXT path=/
_carddav._tcp 14400 IN TXT path=/
_carddavs._tcp 14400 IN TXT path=/
cpcontacts 14400 IN A number.number.135.107
mc 14400 IN A external.ip.82.231
ts 14400 IN A number.number.135.31
furien 14400 IN A external.ip.242.200
dr 14400 IN A external.ip.116.30
lux 14400 IN CNAME mccp.dns.me.
bgp 14400 IN A number.number.135.107
www.bgp 14400 IN A number.number.135.107
autoconfig.bgp 14400 IN A number.number.135.107
webdisk.bgp 14400 IN A number.number.135.107
cpcalendars.bgp 14400 IN A number.number.135.107
autodiscover.bgp 14400 IN A number.number.135.107
_autodiscover._tcp.bgp 14400 IN SRV 0 0 443 cpanelemaildiscovery.cpanel.net.
_caldav._tcp.bgp 14400 IN SRV 0 0 2079 cpanel.PLACEHOLDER.ro.
_caldavs._tcp.bgp 14400 IN SRV 0 0 2080 cpanel.PLACEHOLDER.ro.
_carddav._tcp.bgp 14400 IN SRV 0 0 2079 cpanel.PLACEHOLDER.ro.
_carddavs._tcp.bgp 14400 IN SRV 0 0 2080 cpanel.PLACEHOLDER.ro.
_caldav._tcp.bgp 14400 IN TXT path=/
_caldavs._tcp.bgp 14400 IN TXT path=/
_carddav._tcp.bgp 14400 IN TXT path=/
_carddavs._tcp.bgp 14400 IN TXT path=/
cpcontacts.bgp 14400 IN A number.number.135.107
default._domainkey.bgp 14400 IN TXT "v=DKIM1; k=rsa; p=somethingsomething\;
bgp 14400 IN TXT "v=spf1 +a +mx +ip4:number.number.135.100 ~all"
this is my zone files. range of ip on server is from number.number.135.100 to number.number .135.194 . all the A records made with the internal ip's seem to work properly. but if i use a external ip. like the mc A record. or the furien A record . the A record sometimes works. sometimes it does not. for example the dr A record worked yesterday. but today. if i do a ping to the DNS . i get : ping dr.placeholder.ro Ping request could not find host dr.placeholder.ro. Please check the name and try again. P.S. placeholder is not may actual DNS :P . if its needed . i will provide it. Anyone sees something in the zone files that may determine the A zone to work from time to time ?
-
Hello :) Have you checked to make sure the domain name is using valid name servers? You can use a website such as IntoDNS or the "dig" command to verify your name servers are configured properly. Thank you. 0 -
hmmm....the primary nameserver is correct. but i had some extra nameservers that i don't use anymore. I removed them. will test in 48 hours if the A record work properly now. 0 -
Did not fix it. Strange problem. If i use the same external ip on my other domains. It works just fine. For now i moved my nameservers for the domain in question to couldflare. And use them for the A records. Will do more test next year :D 0 -
Feel free to let us know if the issue continues after additional testing. Thank you. 0
Please sign in to leave a comment.
Comments
4 comments