I
Illyrian
Hi all!
I am a new user and my problem is that i can access different websites
using a dial up account or a cable connection without problems, but
when i try to access these sites from work which is in a lan
environment, i get an error message: We can't find "domain.com"
/dnserror.aspx?FORM=DNSAS&q=.
there is norton corporate edition loaded in the server and we use a
neutopia router.
I dont understand how come i can view some sites but i can not view
others sites but mine and i have no problem viewing these other sites
from any other location.
How do i know if the DNS in the server (windows 2000) is setup
properley?
this is what i got in a dns report :
WARN
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.
WARN
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.
WARN
Mail server host name in greeting
WARNING: One or more of your mailservers may be claiming to be a host
other than what it really is (the SMTP greeting should be a 3-digit
code, followed by a space or a dash, then the host name). This
probably won't cause any harm, but may be a technical violation of
RFC821 4.3 (and RFC2821 4.3.1
WARN
Acceptance of domain literals
WARN: One or more of your mailservers does not accept mail in the
domain literal format (user@[0.0.0.0]). Mailservers are technically
required RFC1123 5.2.17 to accept mail to domain literals for any of
its IP addresses. Not accepting domain literals can make it more
difficult to test your mailserver, and can prevent you from receiving
E-mail from people reporting problems with your mailserver. However,
it is unlikely that any problems will occur if the domain literals are
not accepted.
WARN
SOA Serial Number
WARNING: Your SOA serial number is: 200410262. That is OK, but the
recommended format (per RFC1912 2.2) is YYYYMMDDnn, where 'nn' is the
revision. For example, if you are making the 3rd change on 02 May
2000, you would use 2000050203. This number must be incremented every
time you make a DNS change.
WARN
SOA REFRESH value
WARNING: Your SOA REFRESH interval is : 600 seconds. This seems low.
You should consider increasing this value to about 3600-7200 seconds.
RFC1912 2.2 recommends a value between 1200 to 43200 seconds (20
minutes to 12 hours). A value that is too low will unncessarily
increase Internet traffic.
FAIL
SOA EXPIRE value
WARNING: Your SOA EXPIRE time is : 600 seconds. This seems very low.
You should consider increasing 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.
WARN
SOA MINIMUM TTL value
WARNING: Your SOA MINIMUM TTL is : 600 seconds. This seems low (unless
you are just about to update your DNS). You should consider increasing
this value to somewhere between 3600 and 10800. RFC2308 suggests a
value of 1-3 hours. This value used to determine the default
(technically, minimum) TTL (time-to-live) for DNS entries, but now is
used for negative caching.
THANKS A LOT FOR THE HELP
I am a new user and my problem is that i can access different websites
using a dial up account or a cable connection without problems, but
when i try to access these sites from work which is in a lan
environment, i get an error message: We can't find "domain.com"
/dnserror.aspx?FORM=DNSAS&q=.
there is norton corporate edition loaded in the server and we use a
neutopia router.
I dont understand how come i can view some sites but i can not view
others sites but mine and i have no problem viewing these other sites
from any other location.
How do i know if the DNS in the server (windows 2000) is setup
properley?
this is what i got in a dns report :
WARN
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.
WARN
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.
WARN
Mail server host name in greeting
WARNING: One or more of your mailservers may be claiming to be a host
other than what it really is (the SMTP greeting should be a 3-digit
code, followed by a space or a dash, then the host name). This
probably won't cause any harm, but may be a technical violation of
RFC821 4.3 (and RFC2821 4.3.1
WARN
Acceptance of domain literals
WARN: One or more of your mailservers does not accept mail in the
domain literal format (user@[0.0.0.0]). Mailservers are technically
required RFC1123 5.2.17 to accept mail to domain literals for any of
its IP addresses. Not accepting domain literals can make it more
difficult to test your mailserver, and can prevent you from receiving
E-mail from people reporting problems with your mailserver. However,
it is unlikely that any problems will occur if the domain literals are
not accepted.
WARN
SOA Serial Number
WARNING: Your SOA serial number is: 200410262. That is OK, but the
recommended format (per RFC1912 2.2) is YYYYMMDDnn, where 'nn' is the
revision. For example, if you are making the 3rd change on 02 May
2000, you would use 2000050203. This number must be incremented every
time you make a DNS change.
WARN
SOA REFRESH value
WARNING: Your SOA REFRESH interval is : 600 seconds. This seems low.
You should consider increasing this value to about 3600-7200 seconds.
RFC1912 2.2 recommends a value between 1200 to 43200 seconds (20
minutes to 12 hours). A value that is too low will unncessarily
increase Internet traffic.
FAIL
SOA EXPIRE value
WARNING: Your SOA EXPIRE time is : 600 seconds. This seems very low.
You should consider increasing 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.
WARN
SOA MINIMUM TTL value
WARNING: Your SOA MINIMUM TTL is : 600 seconds. This seems low (unless
you are just about to update your DNS). You should consider increasing
this value to somewhere between 3600 and 10800. RFC2308 suggests a
value of 1-3 hours. This value used to determine the default
(technically, minimum) TTL (time-to-live) for DNS entries, but now is
used for negative caching.
THANKS A LOT FOR THE HELP