Jump to content

Caseks-Computer-Corner


RumPuncher

Recommended Posts

This forum is supported by the 12ozProphet Shop, so go buy a shirt and help support!
This forum is brought to you by the 12ozProphet Shop.
This forum is brought to you by the 12oz Shop.

DNS Report for 12ozprophet.com

Generated by http://www.DNSreport.com at 21:19:54 GMT on 12 Dec 2005.

Category Status Test Name Information

Parent PASS Missing Direct Parent check OK. Your direct parent zone exists, which is good. Some domains (usually third or fourth level domains, such as example.co.us) do not have a direct parent zone ('co.us' in this example), which is legal but can cause confusion.

INFO NS records at parent servers Your NS records at the parent servers are:

 

ns1.easydns.com. [216.220.40.243] [TTL=172800] [CA]

ns2.easydns.com. [209.200.151.4] [TTL=172800] [uS]

remote1.easydns.com. [209.200.131.4] [TTL=172800] [uS]

remote2.easydns.com. [205.210.42.20] [TTL=172800] [CA]

remote3.easydns.com. [209.200.131.10] [TTL=172800] [uS]

 

[These were obtained from f.gtld-servers.net]

PASS Parent nameservers have your nameservers listed OK. When someone uses DNS to look up your domain, the first step (if it doesn't already know about your domain) is to go to the parent servers. If you aren't listed there, you can't be found. But you are listed there.

PASS Glue at parent nameservers OK. The parent servers have glue for your nameservers. That means they send out the IP address of your nameservers, as well as their host names.

PASS DNS servers have A records OK. All your DNS servers either have A records at the zone parent servers, or do not need them (if the DNS servers are on other TLDs). A records are required for your hostnames to ensure that other DNS servers can reach your DNS servers. Note that there will be problems if your DNS servers do not have these same A records.

NS INFO NS records at your nameservers Your NS records at your nameservers are:

 

ns2.easydns.com. [209.200.151.4] [TTL=10800]

remote1.easydns.com. [209.200.131.4] [TTL=10800]

remote2.easydns.com. [205.210.42.20] [TTL=10800]

ns1.easydns.com. [216.220.40.243] [TTL=10800]

 

PASS Mismatched glue OK. The DNS report did not detect any discrepancies between the glue provided by the parent servers and that provided by your authoritative DNS servers.

PASS No NS A records at nameservers OK. Your nameservers do include corresponding A records when asked for your NS records. This ensures that your DNS servers know the A records corresponding to all your NS records.

PASS All nameservers report identical NS records OK. The NS records at all your nameservers are identical.

PASS All nameservers respond OK. All of your nameservers listed at the parent nameservers responded.

PASS Nameserver name validity OK. All of the NS records that your nameservers report seem valid (no IPs or partial domain names).

PASS Number of nameservers OK. You have 5 nameservers. You must have at least 2 nameservers (RFC2182 section 5 recommends at least 3 nameservers), and preferably no more than 7.

PASS Lame nameservers OK. All the nameservers listed at the parent servers answer authoritatively for your domain.

PASS Missing (stealth) nameservers OK. All 4 of your nameservers (as reported by your nameservers) are also listed at the parent servers.

FAIL Missing nameservers 2 ERROR: One or more of the nameservers listed at the parent servers are not listed as NS records at your nameservers. The problem NS records are:

remote3.easydns.com.

PASS No CNAMEs for domain OK. There are no CNAMEs for 12ozprophet.com. RFC1912 2.4 and RFC2181 10.3 state that there should be no CNAMEs if an NS (or any other) record is present.

PASS No NSs with CNAMEs OK. There are no CNAMEs for your NS records. RFC1912 2.4 and RFC2181 10.3 state that there should be no CNAMEs if an NS (or any other) record is present.

PASS Nameservers on separate class C's OK. You have nameservers on different Class C (technically, /24) IP ranges. You must have nameservers at geographically and topologically dispersed locations. RFC2182 3.1 goes into more detail about secondary nameserver location.

PASS All NS IPs public OK. All of your NS records appear to use public IPs. If there were any private IPs, they would not be reachable, causing DNS delays.

INFO Nameservers versions Your nameservers have the following versions:

 

216.220.40.243: "INEGroup BindPlus v6.2 ;)"

209.200.151.4: "Um, it's the latest one."

209.200.131.4: "Um, it's the latest one."

205.210.42.20: "INEGroup BindPlus v6.2 \;)"

209.200.131.10: "Um, it's the latest one."

PASS Stealth NS record leakage Your DNS servers do not leak any stealth NS records (if any) in non-NS requests.

SOA INFO SOA record Your SOA record [TTL=10800] is:

 

Primary nameserver: ns0.easydns.com.

Hostmaster E-mail address: admin.easydns.com.

Serial #: 1132424863

Refresh: 21600

Retry: 7200

Expire: 1209600

Default TTL: 10800

 

PASS NS agreement on SOA serial # OK. All your nameservers agree that your SOA serial number is 1132424863. That means that all your nameservers are using the same data (unless you have different sets of data with the same serial number, which would be very bad)! Note that the DNS Report only checks the NS records listed at the parent servers (not any stealth servers).

WARN SOA MNAME Check WARNING: Your SOA (Start of Authority) record states that your master (primary) name server is: ns0.easydns.com.. However, that server is not listed at the parent servers as one of your NS records! This is probably legal, but you should be sure that you know what you are doing.

PASS SOA RNAME Check OK. Your SOA (Start of Authority) record states that your DNS contact E-mail address is: admin@easydns.com. (techie note: we have changed the initial '.' to an '@' for display purposes).

WARN SOA Serial Number WARNING: Your SOA serial number is: 1132424863. 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.

 

Your SOA serial appears to be the number of seconds since midnight 01 Jan 1970 when the last DNS change was made (tinydns format). That works out to be Sat Nov 19 13:27:43 2005 GMT.

PASS SOA REFRESH value OK. Your SOA REFRESH interval is : 21600 seconds. This seems normal (about 3600-7200 seconds is good if not using DNS NOTIFY; RFC1912 2.2 recommends a value between 1200 to 43200 seconds (20 minutes to 12 hours)). This value determines how often secondary/slave nameservers check with the master for updates.

PASS SOA RETRY value OK. Your SOA RETRY interval is : 7200 seconds. This seems normal (about 120-7200 seconds is good). The retry value is the amount of time your secondary/slave nameservers will wait to contact the master nameserver again if the last attempt failed.

PASS SOA EXPIRE value OK. Your SOA EXPIRE time: 1209600 seconds. This seems normal (about 1209600 to 2419200 seconds (2-4 weeks) is good). 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.

PASS SOA MINIMUM TTL value OK. Your SOA MINIMUM TTL is: 10800 seconds. This seems normal (about 3,600 to 86400 seconds or 1-24 hours is good). 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.

MX INFO MX Record Your 3 MX records are:

100 smtp2.easydns.com. [TTL=10800] IP=205.210.42.53 [TTL=3600] [CA]

5 mail.12ozprophet.com. [TTL=10800] IP=204.215.12.10 [TTL=10800] [uS]

10 smtp.easydns.com. [TTL=10800] IP=205.210.42.52 [TTL=3600] [CA]

PASS Invalid characters OK. All of your MX records appear to use valid hostnames, without any invalid characters.

PASS All MX IPs public OK. All of your MX records appear to use public IPs. If there were any private IPs, they would not be reachable, causing slight mail delays, extra resource usage, and possibly bounced mail.

PASS MX records are not CNAMEs OK. Looking up your MX record did not just return a CNAME. If an MX record query returns a CNAME, extra processing is required, and some mail servers may not be able to handle it.

PASS MX A lookups have no CNAMEs OK. There appear to be no CNAMEs returned for A records lookups from your MX records (CNAMEs are prohibited in MX records, according to RFC974, RFC1034 3.6.2, RFC1912 2.4, and RFC2181 10.3).

PASS MX is host name, not IP OK. All of your MX records are host names (as opposed to IP addresses, which are not allowed in MX records).

PASS Multiple MX records OK. You have multiple MX records. This means that if one is down or unreachable, the other(s) will be able to accept mail for you.

PASS Differing MX-A records OK. I did not detect differing IPs for your MX records (this would happen if your DNS servers return different IPs than the DNS servers that are authoritative for the hostname in your MX records).

PASS Duplicate MX records OK. You do not have any duplicate MX records (pointing to the same IP). Although technically valid, duplicate MX records can cause a lot of confusion, and waste resources.

FAIL Reverse DNS entries for MX records ERROR: The IP of one or more of your mail server(s) have no reverse DNS (PTR) entries (if you see "Timeout" below, it may mean that your DNS servers did not respond fast enough). RFC1912 2.1 says you should have a reverse DNS for all your mail servers. It is strongly urged that you have them, as many mailservers will not accept mail from mailservers with no reverse DNS entry. You can double-check using the 'Reverse DNS Lookup' tool at the DNSstuff site (it contacts your servers in real time; the reverse DNS lookups in the DNS report use our local caching DNS server). The problem MX records are:

10.12.215.204.in-addr.arpa [No reverse DNS entry (rcode: 3 ancount: 0) (check it)]

Mail PASS Connect to mail servers OK: I was able to connect to all of your mailservers.

WARN Mail server host name in greeting WARNING: One or more of your mailservers is 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 is a technical violation of RFC821 4.3 (and RFC2821 4.3.1). Note that the hostname given in the SMTP greeting should have an A record pointing back to the same server.

 

smtp2.easydns.com claims to be host carnage.easydns.com [but that host is at 205.210.42.52, not 205.210.42.53].

PASS Acceptance of NULL <> sender OK: All of your mailservers accept mail from "<>". You are required (RFC1123 5.2.9) to receive this type of mail (which includes reject/bounce messages and return receipts).

PASS Acceptance of postmaster address OK: All of your mailservers accept mail to postmaster@12ozprophet.com (as required by RFC822 6.3, RFC1123 5.2.7, and RFC2821 4.5.1).

WARN Acceptance of abuse address WARNING: One or more of your mailservers does not accept mail to abuse@12ozprophet.com. Mailservers are expected by RFC2142 to accept mail to abuse.

 

mail.12ozprophet.com's abuse response:

>>> RCPT TO:<abuse@12ozprophet.com>

<<< 450 <abuse@12ozprophet.com>: Recipient address rejected: User unknown in virtual mailbox table

 

INFO Acceptance of domain literals WARNING: 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 (mailservers at many common large domains have this problem).

 

smtp2.easydns.com's postmaster@[205.210.42.53] response:

>>> RCPT TO:<postmaster@[205.210.42.53]>

<<< 554 <postmaster@[205.210.42.53]>: Relay access denied

smtp.easydns.com's postmaster@[205.210.42.52] response:

>>> RCPT TO:<postmaster@[205.210.42.52]>

<<< 554 <postmaster@[205.210.42.52]>: Relay access denied

 

PASS Open relay test OK: All of your mailservers appear to be closed to relaying. This is not a thorough check, you can get a thorough one here.

mail.12ozprophet.com OK: 554 <Not.abuse.see.www.DNSreport.com.from.IP.72.240.199.64@DNSreport.com>: Relay access denied

smtp2.easydns.com OK: 554 <This.is.a.test.from.72.240.199.64@wwwDNSREPORTcom.example.com>: Relay access denied

smtp.easydns.com OK: 554 <This.is.a.test.from.72.240.199.64@wwwDNSREPORTcom.example.com>: Relay access denied

WARN 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).

WWW

INFO WWW Record Your http://www.12ozprophet.com A record is:

 

http://www.12ozprophet.com. CNAME 12ozprophet.com. [TTL=10800]

12ozprophet.com. A 204.215.12.10 [TTL=10800] [uS]

 

PASS All WWW IPs public OK. All of your WWW IPs appear to be public IPs. If there were any private IPs, they would not be reachable, causing problems reaching your web site.

PASS CNAME Lookup OK. You do have a CNAME record for http://www.12ozprophet.com, which can cause some confusion. However, this is legal. Your CNAME entry also returns the A record for the CNAME entry, which is good -- otherwise, it would require an extra DNS lookup, which slightly delays the initial access to the website and use extra bandwidth. Note that if the CNAME points to another CNAME, it will likely cause problems.

 

 

 

Fix Yer Shit 12oz you are one easy ass target for hacking

 

 

Happy Hacking

Link to comment
Share on other sites

I had a phone call from a high-level boss from around here asking why his screen was so black, dark, and blurry, and if there was any way he could increase the amount of color ink it used.

 

I directed him to his monitor's brightness and contrast controls.

 

* Him: "Brightness and contrast controls? What do they do?"

 

My smartass remark they make the computer screen brighter so you can see it to bad I cannot do the same for you.

 

*Click*

Link to comment
Share on other sites

I actually read that whole thing abouy 12oz above, kinda understood it the second time...

 

 

I trying to understand this whole security thing and people tracing you and shit and this week I read about that guy who posted the fake wikipedia article about Schlesinger. Anyway some guy tracked down the computer and the guy who made the article... how did that happen? and could it happen to me or you or anybody?

Link to comment
Share on other sites

CustName: Comcast Cable Communications

Address: 3 Executive Campus

Address: 5th Floor

City: Cherry Hill

StateProv: NJ

PostalCode: 08002

Country: US

RegDate: 2004-01-15

Updated: 2004-07-02

 

NetRange: 24.16.0.0 - 24.19.255.255

CIDR: 24.16.0.0/14

NetName: WASHINGTON-9

NetHandle: NET-24-16-0-0-2

Parent: NET-24-16-0-0-1

NetType: Reassigned

Comment:

RegDate: 2004-01-15

Updated: 2004-07-02

 

OrgAbuseHandle: NAPO-ARIN

OrgAbuseName: Network Abuse and Policy Observance

OrgAbusePhone: +1-856-317-7272

OrgAbuseEmail: abuse@comcast.net

 

OrgTechHandle: IC161-ARIN

OrgTechName: Comcast Cable Communications Inc

OrgTechPhone: +1-856-317-7200

OrgTechEmail: CNIPEO-Ip-registration@cable.comcast.com

 

 

 

if you are using a anonymous proxy or anything these results will change

Link to comment
Share on other sites

haha. sort of.

 

 

it\'s an ip range

 

24.16.0.0 - 24.19.255.255

 

 

birch falls into this one distinct

address 24.18.249.171

 

which is part of that range.

 

 

imagine an apartment complex.

each one is numbered. you know the

apartments belong to a realty company

and 24.18.249.171 is the apartment

you want to go to if you wanna leave

a flaming bag of poo on birch\'s doorstep.

Link to comment
Share on other sites

This is old but its pretty funny still

 

This is not by me

 

 

 

Dear Technical Support:

 

Last year I upgraded from Girlfriend 7.0 to Wife 1.0 and noticed that the new program began unexpected child processing that took up a lot of space and valuable resources. No mention of this phenomenon was included in the product brochure.

 

In addition, Wife 1.0 installs itself into all other programs and launches during system initialization, where it monitors all other system activity. Applications such as Poker Night 10.3, Drunken Boys Night 2.5 and Saturday Football 5.0 no longer run, crashing the system whenever selected.

 

I cannot seem to keep Wife 1.0 in the background while attempting to run some of my other favorite applications. I am thinking about going back to Girlfriend 7.0, but the uninstall does not work on this program. Can you help me, please!!!

 

Thanks,

A TROUBLED USER

 

 

 

--------------------------------------------------------------------------------

 

 

 

Dear TROUBLED USER:

 

This is a very common problem men complain about, but is mostly due to a primary misconception. Many people upgrade from Girlfriend 7.0 to Wife 1.0 with the idea that Wife 1.0 is merely a UTILITIES & ENTERTAINMENT program.

 

Wife 1.0 is an OPERATING SYSTEM and designed by its creator to run everything. It is unlikely you would be able to purge Wife 1.0 and still convert back to Girlfriend 7.0. Hidden operating files within your system would cause Girlfriend 7.0 to emulate Wife 1.0 so nothing is gained.

 

It is impossible to uninstall, delete, or purge the program files from the system once installed. You cannot go back to Girlfriend 7.0 because Wife 1.0 is not designed to do this. Some have tried to install Girlfriend 8.0 or Wife 2.0 but end up with more problems than with the original system. Look in your manual under "Warnings-Alimony/Child Support".

 

I recommend you keep Wife 1.0 and just deal with the situation. I suggest installing background application program C:\YES DEAR to alleviate software augmentation. Having Wife 1.0 installed myself, I might also suggest you read the entire section regarding General Partnership Faults (GPFs).

 

You must assume all responsibility for faults and problems that might occur, regardless of their cause. The best course of action will be to enter the command C:\APOLOGIZE. In any case avoid excessive use of YES DEAR because ultimately you will have to give the APOLOGIZE command before the operating system will return to normal.

 

The system will run smoothly as long as you take the blame for all the GPFs. Wife 1.0 is a great program, but very high maintenance. Consider buying additional software to improve the performance of Wife 1.0. I recommend Flowers 2.1 and Diamonds 5.0.

 

Do not, under any circumstances, install Secretary With Short Skirt 3.3. This is not a supported application for Wife 1.0 and is likely to cause irreversible damage to the operating system.

 

Best of luck,

Tech Support

 

 

 

--------------------------------------------------------------------------------

 

Sauce for the gander...author likewise unknown.

 

 

--------------------------------------------------------------------------------

 

Dear Tech Support:

 

Recently I upgraded from Boyfriend 5.0 to Husband 1.0 and noticed that the new program began making unexpected changes to the accounting software, severely limiting access to wardrobe, flower, and jewelry applications that operated flawlessly under Boyfriend 5.0. No mention of this phenomenon was included in the product brochure.

 

In addition, Husband 1.0 uninstalls many other valuable programs such as DinnerDancing 7.5, CruiseShip 2.3, and OperaNight 6.1 and installs new, undesirable programs such as PokerNight 1.3, SaturdayFootball 5.0, Golf 2.4, and ClutterEverywhere 4.5. Conversation 8.0 no longer runs and invariably crashes the system. Under no circumstances will it run DiaperChanging 14.1 or HouseCleaning 2.6. I've tried running Nagging 5.3 to fix Husband 1.0, but this all-purpose utility is of only limited effectiveness.

 

Can you help, please!!

Sincerely, XXX

 

 

 

--------------------------------------------------------------------------------

 

 

 

Dear XXX:

 

This is a very common problem women complain about, but is mostly due to a primary misconception. Many people upgrade from Boyfriend 5.0 to Husband 1.0 with the idea that Husband 1.0 is merely an ENTERTAINMENT package.

 

However, Husband 1.0 is an OPERATING SYSTEM and was designed by its creator to run as few applications as possible. Further, you cannot purge Husband 1.0 and return to Boyfriend 5.0, because Husband 1.0 is not designed to do this. Hidden operating files within your system would cause Boyfriend 5.0 to emulate Husband 1.0, so nothing is gained. It is impossible to uninstall, delete, or purge the program files from the system, once installed. Any new program files can only be installed once per year, as Husband 1.0 has severely limited memory. Error messages are common, and a normal part of Husband 1.0.

 

Having Husband 1.0 installed myself, I might also suggest you read the entire section regarding General Partnership Faults [GPFs]. This is a wonderful feature of Husband 1.0, secretly installed by the parent company as an integral part of the operating system. Husband 1.0 must assume ALL responsibility for ALL faults and problems, regardless of root cause. To activate this great feature enter the command "C:\I THOUGHT YOU LOVED ME". Sometimes Tears 6.2 must be run simultaneously while entering the command. Husband 1.0 should then run the applications Apologize 12.3 and Flowers/Chocolate 7.8.

 

TECH TIP!

 

Avoid excessive use of this feature. Overuse can create additional and more serious GPFs, and ultimately YOU may have to give a C:\I APOLOGIZE command before the system will return to normal operations. Overuse can also cause Husband 1.0 to default to GrumpySilence 2.5 or worse yet, to Beer 6.0. Beer 6.0 is a very bad program that causes Husband 1.0 to create FatBelly files and SnoringLoudly wave files that are very hard to delete. Save yourself some trouble by following this tech tip!

 

Just remember, the system will run smoothly, and take the blame for all GPFs, but because of this fine feature it can only intermittently run all the applications Boyfriend 5.0 ran. Husband 1.0 is a great program, but it does have limited memory and cannot learn new applications quickly. Consider buying additional software to improve performance. I personally recommend HotFood 3.0, Lingerie 5.3, and Patience 10.1. Used in conjunction, these utilities can really keep Husband 1.0 running smoothly.

 

After several years of use, Husband 1.0 will become familiar and you will find many valuable embedded features such as FixBrokenThings 2.1, Snuggling 4.2, and BestFriend 7.6. A final word of caution! DO NOT, under any circumstances, install MotherinLaw 1.0. This is not a supported application and will cause selective shutdown of the operating system. Husband will run only Fishing 9.4 and Hunting 5.2 until MotherinLaw 1.0 is uninstalled. I hope these notes have helped. Thank you for choosing to install Husband 1.0, and we here at Tech Support wish you luck.

Link to comment
Share on other sites

StopIE - Rid the web of Internet Explorer

 

Welcome to StopIE.com. We are dedicated to the removal of Internet Explorer as the most common browser on the web. There are many reasons for this.

Internet Explorer's Main Problems

 

There are countless bugs in Internet Explorer, but here are the main reasons to choose a free alternative.

 

* Prone to viruses and worms

* Renders pages incorrectly. Web designers then need to spend extra time working so that pages work in Internet Explorer. This puts costs up, and slows the web down.

* Doesn't let people resize certain text sizes. This means those with poor sight cannot read small text on many sites.

* Far slower program than other web browsers

* Far larger program than other web browsers

* Isn't as user-centric as other web browsers. It lacks many handy features such as tabbed browsing and integrated search

* Doesn't support PNG images properly

 

Alternatives to Internet Explorer

 

Internet Explorer is the worst major browser. There are a number of free alternatives available. These alternatives are standards compliant, i.e. they conform to international standards. Internet Explorer is not standards compliant, and thus renders pages wrongly.

 

On the alternatives to Internet Explorer page, we outline many superior competitors, all of which are free or have free versions. These are Mozilla Firefox, K-Meleon, Mozilla, Opera, Camino and Safari.

Microsoft responding?

 

Microsoft have announced 'IE7' will be available in the summer (Beta). Security fixes are expected, given MS' recent bad press in this area, but few expect Microsoft to fix web standards issues in Internet Explorer, or IE's accesibility problems.

 

Some only expect a similar update to Service Pack 2 (which fixed a number of very serious vulnerabilities).

 

Maybe some handy features will be adopted from alternative browsers, but no-one is holding their breath.

Play your part - StopIE

 

Change browser, encourage your friends and family to do the same. You may also consider helping to translate the site

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...