View Full Version : www a record
studioinventive 05-18-2010, 06:06 AM Hello everybody, i am still struggling trying to understand what is the problem with my server domain resolution
If i make dns check with http://www.intodns.com/lemagot.net
i get this at the end
ERROR: I could not get any A records for www.lemagot.net!
(I only do a cache request, if you recently added a WWW A record, it might not show up here.)
I use Directadmin as control panel, and i think everything is fine. What i am missing?
Thank you very much for your help
Francesco
MikeDVB 05-18-2010, 06:12 AM Your site is loading just fine:
http://www.lemagot.net/ http://lemagot.net/
I wouldn't worry about the message on that particular report as long as it is all working (which it is).
httpEasy 05-18-2010, 06:17 AM There is no problem with your A records but your name servers appear to be in need for proper registration/configuration.
studioinventive 05-18-2010, 06:18 AM problem is domain doesn't work at my customer place, it is really embarassing, and so i am trying to understand what is the problem
:=)
Thanks
Francesco
httpEasy 05-18-2010, 06:20 AM If it's new it might be a propagation/caching issue. Let your customer flush their DNS.
MikeDVB 05-18-2010, 06:24 AM problem is domain doesn't work at my customer place, it is really embarassing, and so i am trying to understand what is the problem
:=)
Thanks
Francesco
If it's new it might be a propagation/caching issue. Let your customer flush their DNS.
Depending on how long ago it was configured/changed it can take up to 72 hours to propagate fully world-wide.
Generally these days it's only 2 to 10 hours or so but I still stick to the 3 day rule myself for making DNS changes.
studioinventive 05-18-2010, 06:25 AM Yes you are right, the point is he says which his customers can't see the website too, they use orange livebox in france, while i'm with neuf vodafone and everything is fine, i can't tell to every person to flush their dns, and i can't tell to change their dns, this is the real problem :=(
So i was trying to arrange the problem from outside, trying to understand why this is happening
if i make a test from host tracker
http://host-tracker.com/check_res_ajx/4901440-0/
i get 2 domains failure
while yesterday 25 !
Thanks
Francesco
InoxHost 05-18-2010, 06:25 AM Your site is not loading for me at all. I tried to ping it, however got following error message. I strongly suspect, it would be something wrong dns configuration due to which your site did not propagated properly. You need to check it properly orlese have to reconfigure dns zone once again.
C:\Documents and Settings\Administrator>tracert lemagot.net
Unable to resolve target system name lemagot.net.
C:\Documents and Settings\Administrator>
studioinventive 05-18-2010, 06:26 AM Depending on how long ago it was configured/changed it can take up to 72 hours to propagate fully world-wide.
Generally these days it's only 2 to 10 hours or so but I still stick to the 3 day rule myself for making DNS changes.
The point is that the website is online since 3 months ago, it had some downtime at the beginning, is it possibile cache lasts so long?
Thanks
studioinventive 05-18-2010, 06:28 AM Your site is not loading for me at all. I tried to ping it, however got following error message. I strongly suspect, it would be something wrong dns configuration due to which your site did not propagated properly. You need to check it properly orlese have to reconfigure dns zone once again.
what do you mean with reconfigure?
ftp A 85.234.144.189
lemagot.net. A 85.234.144.189
localhost A 127.0.0.1
mail A 85.234.144.189
pop A 85.234.144.189
smtp A 85.234.144.189
www A 85.234.144.189
www.lemagot.net. A 85.234.144.189
lemagot.net. NS ns1.studioinventive.com.
lemagot.net. NS ns2.studioinventive.com.
mail MX 10
lemagot.net. TXT "v=spf1 a mx ip4:85.234.144.189 ~all"
these are dns settings for the domain
Thank you
Francesco
httpEasy 05-18-2010, 06:44 AM Your site is not loading for me at all. I tried to ping it, however got following error message. I strongly suspect, it would be something wrong dns configuration due to which your site did not propagated properly. You need to check it properly orlese have to reconfigure dns zone once again.
It's fine for me.
The point is that the website is online since 3 months ago, it had some downtime at the beginning, is it possibile cache lasts so long?
Thanks
Nope.
And why can't you have your customers flush their DNS? Sounds kind of absurd.
studioinventive 05-18-2010, 06:48 AM And why can't you have your customers flush their DNS? Sounds kind of absurd.
You know for you and me can be easy flushing dns, but for a normal person it can be a problem
but as you can see there somebody in uk even in this post which can't ping the domain, so the problem exists :=(
Sad thing is that the server is in uk too.
Thanks
Francesco
petteyg359 05-18-2010, 10:04 AM ftp A 85.234.144.189
lemagot.net. A 85.234.144.189
localhost A 127.0.0.1
mail A 85.234.144.189
pop A 85.234.144.189
smtp A 85.234.144.189
www A 85.234.144.189
www.lemagot.net. A 85.234.144.189
lemagot.net. NS ns1.studioinventive.com.
lemagot.net. NS ns2.studioinventive.com.
mail MX 10
lemagot.net. TXT "v=spf1 a mx ip4:85.234.144.189 ~all"
Why do you have www and www.lemagot.net.? Just use the www line. Do you use Windows DNS or BIND? If you're using BIND, you can place a line at the top of the zone like $ORIGIN lemagot.net. and then remove lemagot.net. (just leave whitespace) on your NS lines, the first A line, and the TXT line.
|