Just wondering...

[MTDesigns]

Just wondering approximately how long it takes for NS to respond to the Service Agreement submitted by the purchaser of a domain name.[nbsp][nbsp]I'm still waiting for the NIC info that they need to email back to the buyer of a domain name.[nbsp][nbsp]It's been about 3 days now...I thought this was something that was almost immediate...how silly of me ;) .

Joi~

[pridetech]

Is he is paying the $199 for priority name change service? NS says standard processing time is 3-6 weeks.

[MTDesigns]

Nope...not paying the $199...he says he sent the service agreement to hostmaster@networksolutions.com, and he's supposed to get a number back so I can complete the transfer agreement.[nbsp][nbsp]But he still hasn't received that number from them - sooo I can't even begin the transfer yet...

Just want to get this over with already! ;)

Joi~

[pridetech]

Just a related note. CRYPT_PW protection is no longer safe!

NS used to blank out the plain text password in all email notifications to a change request. But from February this is not happening. This means if you use the form to make any changes the other contacts will see your plain text password when they receive the notification. This puts all other domains owned by you at risk.

Hopefully NS will rectify this soon!

[Deb]

Serious disapointment in the recent change by Network Solutions :([nbsp][nbsp]I agree that they need to change it back asap.[nbsp][nbsp]Thanks for the heads up pridetech

Deb
[nbsp]- If it's working break it?

[Dan Kaplan]

If it's not broken, you haven't looked hard enough, fix it anyway.[nbsp][nbsp]- Tom Peters (I believe)

...

If it's not broken, Network Solutions hasn't gotten their hands on it yet, break it anyway.[nbsp][nbsp]- ?

Dspicable

[MTDesigns]

This means if you use the form to make any changes the other contacts will see your plain text password when they receive the notification. This puts all other domains owned by you at risk.
Could you please explain further?[nbsp][nbsp]What password...and how would making changes to one domain (I am not the registered name on this particular domain that I am transferring) affect the others, if my name is not associated with this transfer? Just wondering.... ;)[nbsp][nbsp]
[This message has been edited by MTDesigns (edited 03-13-00@11:34 am)]

[Brian]

If you cannot get them to do this you might be better off switching registries to some one that has an automated system with voice support that can handle this quickly. This might cost $25 dollars but might save an uphill battle with NS.

Your best bet would be to contact register.com or dotster.com and see what they can do.

I hope this helps.

-Brian

[pridetech]

Hi,

Normally NSI performs the authentication for making changes on a domain record based on your email address. However you can change the authentication to CRYPT_PW or PGP. If you use the CRYPT_PW method NSI will do the changes as long as you mention the correct password in the 'Auth Info' (0c) field. This password is not specific to a domain, it is valid for all domains owned by the contact.

After completing the change (or before, depending on the settings) NSI sends notifications to all the listed contacts. These notifications contain the original form that was submitted. Before February 2000 these notifications had the password field blanked out.[nbsp][nbsp]So if I am the admin contact for a domain and some one else is the tech contact, the tech contact will receive a copy of my original submission but (s)he will not be able to see my password.

But now the password field is not blanked out by NSI and the tech contact will see my password. If the person decides to be nasty (s)he can go around making changes to all domains owned by me.

You are safe if your authentication is not CRYPT_PW based!