Web Hosting Talk







View Full Version : Domain viewing.


Benith
02-26-2005, 01:45 PM
I just registered my domain name last night, and when I checked it this morning I couldn't go to the address, but I had asked other people on my buddy list if they could go to the site, they said they could.
I'm not sure what's going on with my computer, I've cleared my: history, cache, cookies and temp internet files. and it still doesn't work. Anyone have any ideas?

Dave Zan
02-26-2005, 03:01 PM
Your ISP might not be updating more often than others do. I'd say
wait a little longer.

Also use dnsreport.com and see what it says.

Benith
02-26-2005, 03:08 PM
I get the following warnings:

NS:
Nameservers on separate class C's
WARNING: All of your nameservers (listed at the parent nameservers) are in the same Class C (technically, /24) address space, which means that they are probably at the same physical location. Your nameservers should be at geographically dispersed locations. You should not have all of your nameservers at the same location. RFC2182 3.1 goes into more detail about secondary nameserver location.


SOA:
SOA REFRESH value
WARNING: Your SOA REFRESH interval is : 14400 seconds. This seems a bit high. You should consider decreasing this value to about 3600-7200 seconds. RFC1912 2.2 recommends a value between 1200 to 43200 seconds (20 minutes to 12 hours, with the longer time periods used for very slow Internet connections; 12 hours seems very high to us), and if you are using DNS NOTIFY the refresh value is not as important (RIPE recommends 86400 seconds if using DNS NOTIFY). This value determines how often secondary/slave nameservers check with the master for updates. A value that is too high will cause DNS changes to be in limbo for a long time.

SOA EXPIRE value
WARNING: Your SOA EXPIRE time is : 3600000 seconds. This seems a bit high. You should consider decreasing this value to about 1209600 to 2419200 seconds (2 to 4 weeks). RFC1912 recommends 2-4 weeks. This is how long a secondary/slave nameserver will wait before considering its DNS data stale if it can't reach the primary nameserver.


MX:
Multiple MX records
WARNING: You only have 1 MX record. If your primary mail server is down or unreachable, there is a chance that mail may have troubles reaching you.



Mail:
SPF Record
Your domain does not have an SPF record. This means that spammers can easily send out E-mail that looks like it came from your domain, which can make your domain look bad (if the recipient thinks you really sent it), and can cost you money (when people complain to you, rather than the spammer). You may want to add an SPF record ASAP, as 01 Oct 2004 was the target date for domains to have SPF records in place (Hotmail, for example, started checking SPF records on 01 Oct 2004).

Dave Zan
02-26-2005, 06:50 PM
I'd still say simply wait. Worse comes to worse, contact your ISP,
your hosting provider, then your registrar in said order.

Bashar
02-28-2005, 03:03 AM
try Start -> Run -> command
ipconfig /flushdns

if not then you'd have to wait for your ISP cached DNS to be refreshed.