DNS Propagation Issue . Plesk. Name Servers not being updated by Networksolutions

 I wonder if someone can point me to the right direction.

I look after 2 plesk servers.
We recently relocated them a new Datacentre and I went through changing the IP configuration etc on both of them and everything is working ok.

Recently I have found out that for some domains the .com ones, when I do a lookup, its
 >>>> Still pointing to the old stale IP addresses
 >>>> and it looks like the domain registrar who is our case is network solutions has not updated the records to push through the root servers on the internet and I can see when querying root servers,  a.gtld-servers.net returns info about Name Servers but then show the old records
>>>>> the problem I have is there are some customers who have odd email issues.
>>>>> upon doing MXtoolbox lookup, I get those stale records as well.
>>>>> i have exhausted speaking to networksolutions who are assuring me that it is just a visual issue and the records at the backend are up to date (they are not).

Any ideas etc.

Here is the output below:

Domain NS records       Nameserver records returned by the parent servers are:

ns01.netcom.uk.net.   ['xxx.xOLD IPxx.xxx.xxx']   [TTL=172800]  it returns OLD IP, it should be NEW one. Only doing it for .com domains
ns02.netcom.uk.net.   ['xxx.xxOLD IPx.xxx.xxx']   [TTL=172800]

a.gtld-servers.net was kind enough to give us that information.

and the warning as below:

Error       Mismatched NS records       WARNING: One or more of your nameservers did not return any of your NS records.
Error       DNS servers responded       ERROR: One or more of your nameservers did not respond:
The ones that did not respond are:
xxx.xxx.OLDIP.xxx.xx  ><<<<<< which makes sense it won't respond as its not their.
LVL 19
Kash2nd Line EngineerAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Unfortunately you are dealing with NS.

I have had issues in the past with ghost mx and ip records of which I was told to live with it and it will get fixed eventually.

Fuel for the fire:

Who controls the DNS servers for those domains? That's where the work has to be done, not at the registrar. Usually the registrar only records the DNS servers themselves and all other records come from the authoritative DNS servers.

If the registrar owns the DNS servers also then there is nothing you can do apart from
1. Talking to the correct party at Network Solutions and providing them with the info above, so that they can understand that the changes you require haven't been propagated. It should not take more than a few hours, or
2. Transfer the domains to a new and more responsive registrar, if that's permitted in the U.K.
Without disclosing the actual domain names and old/new addresses you're talking about, there's no way to help you.
Big Business Goals? Which KPIs Will Help You

The most successful MSPs rely on metrics – known as key performance indicators (KPIs) – for making informed decisions that help their businesses thrive, rather than just survive. This eBook provides an overview of the most important KPIs used by top MSPs.

David Johnson, CD, MVPOwnerCommented:
get am account (free) on Cloudflare (just a satisfied customer) and change your nameservers on Network Solutions to the name servers on cloudflare and use cloudflare to manage your DNS
robocat has a point. Although we normally try to keep things more anonymous on EE, DNS issues are more easily resolved when we can see actual names and IPs, since it's ultimately public information anyway. So the more real info you can provide, the more likely you can be assisted.
Kash2nd Line EngineerAuthor Commented:
thanks Guys for input.
@mike we control the DNS and the name servers are our plesk servers.

the domain in question for example is cwelimited.com which is pointing to old IPs.
there are many other .com(s) which are doing the same thing.

I think I will try David's suggestion to see if it helps.
David Johnson, CD, MVPOwnerCommented:
it will take whatever your TTL time is to fully propogate

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Kash2nd Line EngineerAuthor Commented:
I see, so you are trying to change NS records at ISP then. the MX records will change when the NS is changed of course, because the NS contains the MX records.
Kash2nd Line EngineerAuthor Commented:
Just wanted to add the final notes on to this.
I have been chasing networksolutions twice a day and they have finally pulled finger out of their arses and updated the Glue records.

This is now working like a charm. This means I won't have to faff around changing name servers for 500 domains.
Happy days.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.