Forum Replies Created
-
Posts
-
Quote:quote:
Chat rooms are full of immature teenagers who don’t know how to use the English language anyway.Not all. There are rooms set aside for teenagers, and I don’t think they are all immature either.
As for English language, chat rooms pull people from around the world, not everyone speaks English, but more foreigners speak English than we speak foreign languages!
Chat Rooms have their use:
(1) You can talk to people with similar interests in real time, rather than wait all day for a response on a forum etc…
(2) Help and Assistance. Not just computing but anything. You can’t ask a book, or a website to clarify something or say it in an alternative way like you can a person.
(3) Language. Learning a language is good if you can talk to people who talk that language too. Again, a book or a tv program or a cassette cannot be asked to try and say something in a different way or to repear its self. Chat opens ability for this, and for voice too.
Everything can be abused.
If you’re one of those who thinks chat is all bad because of what happens, this stuff happens in normal Instant Messages, it happens on forums, in emails, in the street, in the park, at home, at school, at work etc…
Like everything else, children and other vulnerable people should be supervised. Like everything else, it can’t be monitored 24/7 perfectly.
I know exactly what you mean about Microsoft, but the content will not be posted here because of it’s nature (i.e. the abuse).
If you think that is a domain whois you’re not doing it right, that looks for nameservers with microsoft in them.
To do a proper domain whois, you need to type “domain microsoft.com” not just “microsoft.com”.
If you have archives enabled (login(messenger), preferences, archive) and IMs are ticked to be saved, you can view them from the contacts>>message archive option.
Otherwise no.
Quote:quote:
d00d, hve you ever done a whois on microsoft.com, it’s hillarious.I have posted at the end of this the microsoft.com whois information. I must not have a sense of humour, I don’t find it funny at all.
Quote:quote:
At any rate, you are right, it’s not relevant, and wasn’t to begin with, which is what the last statement of my last post was about.I Agree.
Quote:quote:
However, whois information can actually be several years old, it’s the DNS information that’s usually not more than 48 hours old, and whois and DNS aren’t related at all.I can agree and disagree.
Agree, that it can be out of date, as it’s the domain owners responsibility to keep this information upto date. Information such as address, telephone number can be left and it will just become old.
Disagree in sense that as long as user submits changes, the changes will be reflected within 48hours.
Quote:quote:
Whois just gives you general information about the site/domain, like the admin, abuse email address, the engineers/admin’s address, location, so on and so forth.Various contacts, technical, administrative etc…
Dates of registration, renewal, updatesQuote:quote:
The DNS information can actually be read by doing a dig on the site/domane (which is what I thinkyou meant by domane whois, however, it’s not techincally called that, it’s actually called…. a dig) and they can be as much as a week outdated, however, most are usually 600 seconds (6 min) to 24 hours outdated.This is actually called a DNS lookup. Via a recursive process, you want to find information regarding the IP that is retrieved from a domain. You do this via a DNS lookup. dig is a program that comes with BIND and allows you to do a DNS lookup, I’ve attached for you a dig output.
Can be upto 48hours out of date. The person who runs a domain, sets a value called TTL – Time To Live on a domain name, in seconds. This is how long a DNS server may cache the answer to a lookup, so that in future it avoids doing another full lookup.
Quote:quote:
The ISP’s domain info that I work at keeps it for 600 seconds.Good for them.
Quote:quote:
Also, an IP whois is the same as a domane/hostname/site whois, since, it’s all done by IP address anyways, the name is just easier to remember.No.
A domain name whois looks for who registered a domain name, and who are the contacts.
A DNS lookup, translates a domain into an IP address.
An IP lookup tells you who has been assigned a block of IP addresses, including contacts, the updates made, descriptions, and maybe use.
Quote:quote:
I could explain how DNS works, but I’m sure you know Freddy, at least I think you do , and if you don’t or anyone else wants to know, I can give an explanation, as long as it won’t piss off the admins of this site anyways .No need, I already wrote this http://www.helpbytes.co.uk/dns.php a long time ago.
MICROSOFT.COM WHOIS
Code:Registrant:
Microsoft Corporation (MICROSOFT-DOM)
1 microsoft way
One Microsoft Way
redmond, WA 98052
USDomain Name: MICROSOFT.COM
Administrative Contact:
MICROSOFT CORPORATION (EPMKOEAUSO) [email]msnhst@MICROSOFT.COM[/email]
One Microsoft Way
Redmond, WA 98052
US
425 882 8080 fax: 206 703 2641Technical Contact:
MICROSOFT CORPORATION (EJSEHEQUAO) [email]msnhst@MICROSOFT.COM[/email]
One Microsoft Way
Redmond, WA 98052
US
425-882-8080Record expires on 03-May-2014.
Record created on 02-May-1991.
Database last updated on 28-May-2004 12:43:51 EDT.Domain servers in listed order:
DNS1.CP.MSFT.NET 207.46.138.20
DNS1.TK.MSFT.NET 207.46.245.230
DNS3.UK.MSFT.NET 213.199.144.151
DNS1.DC.MSFT.NET 64.4.25.30
DNS1.SJ.MSFT.NET 64.4.25.30
DNS LOOKUP FOR MICROSOFT.COM
Code:; <> DiG 9.2.1 <> @localhost microsoft.com +trace
;; global options: printcmd
. 500963 IN NS M.ROOT-SERVERS.NET.
. 500963 IN NS A.ROOT-SERVERS.NET.
. 500963 IN NS B.ROOT-SERVERS.NET.
. 500963 IN NS C.ROOT-SERVERS.NET.
. 500963 IN NS D.ROOT-SERVERS.NET.
. 500963 IN NS E.ROOT-SERVERS.NET.
. 500963 IN NS F.ROOT-SERVERS.NET.
. 500963 IN NS G.ROOT-SERVERS.NET.
. 500963 IN NS H.ROOT-SERVERS.NET.
. 500963 IN NS I.ROOT-SERVERS.NET.
. 500963 IN NS J.ROOT-SERVERS.NET.
. 500963 IN NS K.ROOT-SERVERS.NET.
. 500963 IN NS L.ROOT-SERVERS.NET.
;; Received 244 bytes from 127.0.0.1#53(localhost) in 30 mscom. 172800 IN NS A.GTLD-SERVERS.NET.
com. 172800 IN NS G.GTLD-SERVERS.NET.
com. 172800 IN NS H.GTLD-SERVERS.NET.
com. 172800 IN NS C.GTLD-SERVERS.NET.
com. 172800 IN NS I.GTLD-SERVERS.NET.
com. 172800 IN NS B.GTLD-SERVERS.NET.
com. 172800 IN NS D.GTLD-SERVERS.NET.
com. 172800 IN NS L.GTLD-SERVERS.NET.
com. 172800 IN NS F.GTLD-SERVERS.NET.
com. 172800 IN NS J.GTLD-SERVERS.NET.
com. 172800 IN NS K.GTLD-SERVERS.NET.
com. 172800 IN NS E.GTLD-SERVERS.NET.
com. 172800 IN NS M.GTLD-SERVERS.NET.
;; Received 463 bytes from 202.12.27.33#53(M.ROOT-SERVERS.NET) in 281 msmicrosoft.com. 172800 IN NS dns1.cp.msft.net.
microsoft.com. 172800 IN NS dns1.dc.msft.net.
microsoft.com. 172800 IN NS dns1.sj.msft.net.
microsoft.com. 172800 IN NS dns1.tk.msft.net.
microsoft.com. 172800 IN NS dns3.uk.msft.net.
;; Received 229 bytes from 192.5.6.30#53(A.GTLD-SERVERS.NET) in 79 msmicrosoft.com. 3600 IN A 207.46.245.222
microsoft.com. 3600 IN A 207.46.245.214
;; Received 63 bytes from 207.46.138.20#53(dns1.cp.msft.net) in 161 ms—IP WHOIS OF 207.46.245.222—-
Code:OrgName: Microsoft Corp
OrgID: MSFT
Address: One Microsoft Way
City: Redmond
StateProv: WA
PostalCode: 98052
Country: USNetRange: 207.46.0.0 – 207.46.255.255
CIDR: 207.46.0.0/16
NetName: MICROSOFT-GLOBAL-NET
NetHandle: NET-207-46-0-0-1
Parent: NET-207-0-0-0-0
NetType: Direct Assignment
NameServer: DNS1.CP.MSFT.NET
NameServer: DNS2.CP.MSFT.NET
NameServer: DNS1.TK.MSFT.NET
NameServer: DNS1.DC.MSFT.NET
NameServer: DNS1.SJ.MSFT.NET
Comment:
RegDate: 1997-03-31
Updated: 2002-12-05TechHandle: ZM39-ARIN
TechName: Microsoft
TechPhone: +1-425-936-4200
TechEmail: [email]noc@microsoft.com[/email]OrgAbuseHandle: HOTMA-ARIN
OrgAbuseName: Hotmail Abuse
OrgAbusePhone: +1-425-882-8080
OrgAbuseEmail: [email]abuse@hotmail.com[/email]OrgAbuseHandle: MSNAB-ARIN
OrgAbuseName: MSN ABUSE
OrgAbusePhone: +1-425-882-8080
OrgAbuseEmail: [email]abuse@msn.com[/email]OrgAbuseHandle: ABUSE231-ARIN
OrgAbuseName: Abuse
OrgAbusePhone: +1-425-882-8080
OrgAbuseEmail: [email]abuse@microsoft.com[/email]OrgNOCHandle: ZM23-ARIN
OrgNOCName: Microsoft Corporation
OrgNOCPhone: +1-425-882-8080
OrgNOCEmail: [email]noc@microsoft.com[/email]OrgTechHandle: MSFTP-ARIN
OrgTechName: MSFT-POC
OrgTechPhone: +1-425-882-8080
OrgTechEmail: [email]iprrms@microsoft.com[/email]# ARIN WHOIS database, last updated 2004-05-27 19:15
# Enter ? for additional hints on searching ARIN’s WHOIS database.Anti Virus companies are not interested. They are not true viruses, because they don’t infect other files.
They are not worms, there is no automated infection.
Parts of the infection are Trojans which download the main infection, there are also ad clickers and downloaders in it, but again, no one is really interested in it, I sent samples to people, one replied saying it detected via heuristic scanning what was going on, and that it wasn’t a concern to their software because its more of a spyware issue.
No spyware companies replied.
Firstly, the whois information for microsoft.com looks fine.
Secondly, domain whois are usually no more than 48 hours (2 days) outdated.
Thirdly, IP whois is different, you are asking the big boys who they assigned the IP too, if they don’t know, the internet would be in a mess.
Fourthly(?), don’t think this is relevant to the forum.
I used the ActiveX installer, as any windows user with IE will be defaulted too, and I chose custom install over typical, because I can do without that evil toolbar known as Yahoo! Toolbar.
Anyway, it let me untick all options ( http://www.helpbytes.co.uk/images/mess6/installFull3.png ) but the Yahoo! Mail Control still installed, just didn’t make its self default.
I don’t remember the installers being part of the beta, as it obviously has issues too, this would have been a good idea, Yahoo! have a good idea, then they go release this, which to be honest, aint good is it!
I was thinking similiarly, there are still issues that let booters boot people at server for YMSG, but Yahoo! would say, well, it is free!
There are so many errors in this “release” that should have gone with the beta, but its been really rushed to release for the IM Live contest.
The contest will go well, if anyone can get Messenger to work long enough for them to compete!
HelpBytes is my website 😉
http://www.helpbytes.co.uk/messylinks.php has the ways of editing the link to set default text and IDs etc… and for other ways of linking into the messenger features.
I’ll attempt to keep this short 😉
Firstly, you may only obtain the IP (and isn’t this discussed in about 20 other threads?) when the IM goes into peer 2 peer mode, in which case messages are not handled by the server or routed through it. This only happens when two buddies talk usually, and it doesn’t happen all that often.
Secondly, it’s port 5101 http://www.helpbytes.co.uk/yconnect.php
Thirdly, Jimmy is indeed correct on most parts of his IP assignment.
RIPE is Europe, Middle East,Central Asia and parts of Africa (above equator), not Australia.
ARIN is indeed American plus sub-sahara Africa.
APNIC handles Australian too
There is a fourth, LACNIC, Latin Ammerica and Carribean.
As Jimmy said, they are responsible for IP assignments, an ISP must obtain the IP rights from these people first. It is from these 4 you get the whois information on which ISP the IP belongs too.
I explain 10 times an hour why Messenger is bootable, and if you searched this forum you’d find numerous explanations from me.
Y!Tunnel doesn’t work on heuristics, its dumb. It’s not got anything over a client in that department. Its worse off, and you’d know if you find and read my explanation.
Some boot happens at the server, no one has control over this.
I have just updated the instructions.
http://www.helpbytes.co.uk/removal.php
These have successfully helped a few people already, so good luck to you.
