If the old AD Domain no longer exists then:
- Your administrators have probably migrated your account to the new AD domain. Whether that migration includes password history and state I couldn't say as it would depend on how exactly the migration is done.
127.0.0.1
represents your local machine. Mapping the name of the DC to your local machine would do nothing to assist you, because your local machine is not an AD domain controller for the old domain and so would not be able to process a login request.
- If the old AD is not online, it is probably inaccessible to clients, and even if it weren't it's unlikely that your account would have sufficient privileges to change password expiration policy.
Your domain administrators will likely have put a significant amount of planning into the migration of something as critical as Active Directory, if you have concerns regarding the migration, I would suggest contacting them since they will be far more able to tell you for certain if there will be downtime, and what you might be able to do to minimize the impact of downtime for yourself and your projects.
All of the above being said, Windows may1 maintain a credential cache which can be used for a limited time to login when a domain is unavailable. As long as your machine does not communicate with a domain, and your old credentials remain cached you might be able to login from your machine, until those cached credentials expire.
1 Whether credentials are cached can be controlled by Group Policy. If your administrators have disabled cached credentials. then this will not work for you.